Simply Hosting undefined Servers outage history

On October 20, two critical PHP vulnerabilities were announced: CVE-2026-109618 and CVE-2026-109619. These vulnerabilities have a CVSS score of 9.2 and could potentially be exploited to execute code remotely on a server without requiring authentication. The vulnerabilities may affect all PHP versions starting from PHP 5. If you use PHP on your Bare Metal, Dedicated Server, VPS, we strongly recommend updating PHP with the patches that are available. If you are running cPanel/Plesk, patches are also available, and you should apply them. If you have a site/s running on these products from us, we recommend that you review your PHP usage and the version being used by you or your customers and take relevant actions. If you have managed server/vps with us, then these are/have been patched by our teams.

On October 20, two critical PHP vulnerabilities were announced: CVE-2026-109618 and CVE-2026-109619. These vulnerabilities have a CVSS score of 9.2 and could potentially be exploited to execute code remotely on a server without requiring authentication. The vulnerabilities may affect all PHP versions starting from PHP 5. If you use PHP on your Bare Metal, Dedicated Server, VPS, we strongly recommend updating PHP with the patches that are available. If you are running cPanel/Plesk, patches are also available, and you should apply them. If you have a site/s running on these products from us, we recommend that you review your PHP usage and the version being used by you or your customers and take relevant actions. If you have managed server/vps with us, then these are/have been patched by our teams.

On 20 October 2026, the Global PHP Security Team announced two critical security vulnerabilities. The official security updates were released the following day. Since millions of websites worldwide rely on PHP, the announcement understandably caused concern, and we received a large number of questions from our customers. Rightly so: the security of your website is extremely important. The good news? We took immediate action. Teams have been working non-stop to address the issue, taking mitigating measures where possible while waiting for the official software patches, and rolling out those patches as soon as they became available. All systems that could have been impacted on our hosting & company platforms have now been patched. Not every website runs on the latest PHP version. Some still use older versions, for example because certain plugins or applications are incompatible with a newer PHP release. Our teams went the extra mile and also adapted the security fixes for some older PHP versions. This process is called backporting: adapting a security patch so it also works with an older software version. It’s not simply a matter of copying a file. Our engineers have to manually implement, compile and test the necessary changes. The PHP project currently officially supports versions 8.2 through 8.5. Older versions no longer receive regular security updates. It goes without saying though, if you are on an older version of PHP, please update this.

One of our UK to Ireland links is currently down. The Redundant paths are functioning as expect so no impact is expected but the network should be considered at risk at this time. We have a case open with the carrier and are awaiting updates.

One of our UK to Ireland links is currently down. The Redundant paths are functioning as expect so no impact is expected but the network should be considered at risk at this time. We have a case open with the carrier and are awaiting updates. The Carrier has confirmed the issue is resolved, we have monitored and are happy to now end the at risk period.

We are currently dealing with a issue on one of our fibre connections. Any services using it have failed over to redundant resources but the network should be considered "At Risk" while this fault is ongoing.

We are currently dealing with a issue on one of our fibre connections. Any services using it have failed over to redundant resources but the network should be considered "At Risk" while this fault is ongoing. The carrier has now identified the issue and is working to carry out the necessary repairs.

The carrier has repaired the service and the normal levels of resilience of the network have resumed. We consider the event cleared, but will continue a period of monitoring.

The carrier has repaired the service and the normal levels of resilience of the network have resumed. We consider the event cleared and are no longer in an at risk state.

Our monitoring has identified a failed network switch in our Reading datacentre rack L20 affecting a small number of dedicated server customers in that rack. The switch is currently under investigation and we expect servers to return online soon. We will post a further update once complete.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Our monitoring has identified a failed network switch in our Reading datacentre rack N17 affecting a small number of dedicated server customers in that rack. The switch is currently under replacement and we expect servers to return online soon. We will post a further update once complete.

The switch has now been replaced, and the rack is back online

We will continue to monitor over the next couple of hours

This incident has been resolved.

We are investigating an issue on one link between our Reading Datacentre and London, this link is currently down and therefore the network should be considered at-risk. We are engaging with our upstream supplier to determine a root cause and implement a fix.

Our supplier has identified the root cause and is undertaking remedial work to address the underlying issue. The network remains at risk at this time.

Our supplier has completed the remedial work and confirmed the fix is in place. The network is no longer at risk. We will continue to monitor the link overnight as a precaution.

This incident has been resolved.

We currently have an issue with one of our switches causing some servers to be offline, we are working on getting the issue resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

Our monitoring has detected 2 independent issues on circuits to our other European locations. Whilst we still have upstream connectivtiy from that location and resilient connectivity to another core pop datacenter we as such rely on this site at the current time and would consider this an at-risk situation for Network. We are progressing fault tickets with both carriers with the highest priority to restore normal resilience levels.

Both suppliers of different international circuits are mobilising engineers and replacement equipment to their affected locations in the EU with priority.

Both suppliers of different international circuits have repaired their services overnight in the EU. The Network is now operating with normally expected levels of resilience.

Our network teams have identified multiple independent fibre cuts across multiple suppliers that are impacting usual resilience to our IP transit network that feeds our UK hosting services. The network is still available and at full capacity, however we consider this an at-risk situation until these links are recovered by the suppliers and are closely tracking their progress.

All fibres and links are now available as normal and full network resilience has been restored. We will keep under monitoring overnight but are not anticipating any further unplanned works.

All fibres and links are now available as normal and full network resilience has been restored. We will keep under monitoring overnight but are not anticipating any further unplanned works.

At around 1:23am BST we were alerted to an instance of network instability. This was found to be due to a flapping link caused by a hardware failure. We isolated the link in question at approximately 1:57am BST and removed it from service while we arrange hardware replacement. This has reduced the capacity along one of our backbone links however overall resiliency has not been affected. We believe the impact to customers to be minimal however we will continue to monitor the situation and provide updates once we initiate the replacement process.

Faulty hardware has been identified and replaced, and the affected link will be returned to service between 2300 and 0100 tonight.

Faulty hardware has been identified and replaced, and the affected link will be returned to service between 2300 and 0100 tonight.

We have reports from a small numbers of customers with intermittent traffic issues communicating from some Amazon AWS instances to our network. This does not affect all source or destination IP addresses but a small subset of traffic that is not predictable. We are currently investigating and communicating with the supply chain to resolve the problem as quickly as possible.

Update: A solution has been found and we now believe that this has been resolved. We will monitor feedback and the network before fully closing this status. We have reports from a small numbers of customers with intermittent traffic issues communicating from some Amazon AWS instances to our network. This does not affect all source or destination IP addresses but a small subset of traffic that is not predictable. We are currently investigating and communicating with the supply chain to resolve the problem as quickly as possible.

Update: A solution has been found and we now believe that this has been resolved. We will monitor feedback and the network before fully closing this status. We have reports from a small numbers of customers with intermittent traffic issues communicating from some Amazon AWS instances to our network. This does not affect all source or destination IP addresses but a small subset of traffic that is not predictable. We are currently investigating and communicating with the supply chain to resolve the problem as quickly as possible.

We are currently investigating reports of Network packet loss or slow network access to some Simply Hosting services.

An issue was identified with a network device which has now been resolved and normal levels of network service has resumed.

This incident has been resolved.

We are investigating a network issue on a core device that may be affecting traffic from some destinations to some Simply Dedicated Servers.

Mitigating actions have been implemented and appear to have resolved the fault conditions in the affected hardware. We will now closely monitor before marking this issue as resolved.

This incident has been resolved.

We are currently investigating an issue with a linecard in one of our PoP routers. We do not expect this to cause any outages however this should be considered an at risk period as due to the nature of this issue we will need to run at reduced resiliency at times during fault finding and resolution.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are aware of a service issue affecting one of our backbone links between two of our PoP sites. We do not expect any service interruption however this should be considered an at-risk period due to reduced resiliency.

This issue was observed as fixed at around 2:30am, after monitoring for a while and checking for errors, we believe this incident to be resolved.

We are aware of a service issue affecting one of our backbone links that connects our Reading DC to one of our PoP sites. We do not expect any service interruption however this should be considered an at-risk period due to reduced resiliency.

This incident has been resolved.

We are aware of a service issue affecting one of our backbone links that connects our Reading DC to one of our PoP sites. We do not expect any service interruption however this should be considered an at-risk period due to reduced resiliency.

This incident has been resolved.

We are currently experiencing an issue with our phone lines, for any support issues, please raise a ticket on your customer portal or email [email protected]

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Due to a software error causing forwarding issues, we will be rebooting one of our aggregation routers imminently. The reboot is expected to cause two blips as the secondary router as part of the resilient pair takes over, and then the primary router comes back online and takes back control.

The router in question is now back online and we can confirm the issue is resolved.