Engineers are carrying out container reboots after a recent update which requires a restart to take full effect. Containers will normally be offline for a matter of seconds during the reboot.
External monitoring scripts may pick up the reboot and report as an outage.
11th March 2017, at 8:56PM
11th March 2017, at 9:36PM
Prohost33 is being rebooted to apply new security modules. Websites will be unavailable for a few minutes.
7th March 2017, at 9:14AM
7th March 2017, at 9:56AM
We're currently reviewing a possible fault on our core network affecting multiple services. More information to follow.
28th February 2017, at 10:50PM
1st March 2017, at 2:51AM
Prohost33 is undergoing a quick reboot to apply some new security patches. Websites will be down for a few minutes on this server. Emails will not be affected.
23rd February 2017, at 4:14PM
23rd February 2017, at 4:56PM
As part of the PHP7 migration process, we are restarting all WordPress hosting containers. Expected downtime for each container will be negligible. We will be monitoring all sites during this period.
21st February 2017, at 2:21PM
21st February 2017, at 3:43PM
We are currently removing the staging Chroots, put in place to test PHP7. This may mean both your staging and main site will for a second be unresponsive as PHP-FPM is reloaded with PHP7 on the main site.
This process is being monitored by engineers to make sure it goes smoothly.
20th February 2017, at 3:15PM
20th February 2017, at 5:11PM
This server is being rebooted in order for the memory to be upgraded.
Estimated downtime is 15 minutes.
16th February 2017, at 8:38AM
16th February 2017, at 8:45AM
This server is being rebooted in order for the memory to be upgraded. Estimated downtime is 15 minutes.
16th February 2017, at 8:25AM
16th February 2017, at 8:37AM
This server is being rebooted in order for the memory to be upgraded.
Estimated downtime is 30 minutes.
16th February 2017, at 8:09AM
16th February 2017, at 8:24AM
Prohost28 is currently being rebooted to apply a new network configuration as part of scheduled maintenance.
Estimated downtime is 10 minutes.
15th February 2017, at 7:48AM
15th February 2017, at 8:01AM