Störungsverlauf von Simply Hosting undefined Servers

1. 22. Oktober 2026 um 15:41 UTCmonitoring

   Am 20. Oktober wurden zwei kritische PHP-Schwachstellen angekündigt: CVE-2026-109618 und CVE-2026-109619. Diese Sicherheitslücken haben einen CVSS-Score von 9,2 und könnten möglicherweise genutzt werden, um Code aus der Ferne auf einem Server auszuführen, ohne dass eine Authentifizierung erforderlich ist. Die Sicherheitslücken können sich auf alle PHP-Versionen ab PHP 5 auswirken. Wenn Sie PHP auf Ihrem Bare Metal, Dedicated Server, VPS verwenden, empfehlen wir dringend, PHP mit den verfügbaren Patches zu aktualisieren. Wenn Sie cPanel/Plesk ausführen, sind auch Patches verfügbar, die Sie anwenden sollten. Wenn Sie eine Website/s mit diesen Produkten von uns haben, empfehlen wir Ihnen, Ihre PHP-Nutzung und die von Ihnen oder Ihren Kunden verwendete Version zu überprüfen und entsprechende Maßnahmen zu ergreifen. Wenn Sie Server/vps mit uns verwaltet haben, werden diese von unseren Teams gepatcht.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Oktober 2026 um 13:16 UTCmonitoring

   Am 20. Oktober wurden zwei kritische PHP-Schwachstellen angekündigt: CVE-2026-109618 und CVE-2026-109619. Diese Sicherheitslücken haben einen CVSS-Score von 9,2 und könnten möglicherweise genutzt werden, um Code aus der Ferne auf einem Server auszuführen, ohne dass eine Authentifizierung erforderlich ist. Die Sicherheitslücken können sich auf alle PHP-Versionen ab PHP 5 auswirken. Wenn Sie PHP auf Ihrem Bare Metal, Dedicated Server, VPS verwenden, empfehlen wir dringend, PHP mit den verfügbaren Patches zu aktualisieren. Wenn Sie cPanel/Plesk ausführen, sind auch Patches verfügbar, die Sie anwenden sollten. Wenn Sie eine Website/s mit diesen Produkten von uns haben, empfehlen wir Ihnen, Ihre PHP-Nutzung und die von Ihnen oder Ihren Kunden verwendete Version zu überprüfen und entsprechende Maßnahmen zu ergreifen. Wenn Sie Server/vps mit uns verwaltet haben, werden diese von unseren Teams gepatcht.

2. 22. Oktober 2026 um 15:31 UTCmonitoring

   Am 20. Oktober 2026 kündigte das Global PHP Security Team zwei kritische Sicherheitslücken an. Die offiziellen Sicherheitsupdates wurden am nächsten Tag veröffentlicht. Da Millionen von Websites weltweit auf PHP setzen, hat die Ankündigung verständlicherweise Bedenken ausgelöst und wir haben eine große Anzahl von Fragen von unseren Kunden erhalten. Zu Recht: Die Sicherheit Ihrer Website ist extrem wichtig. Die guten Nachrichten? Wir haben sofort gehandelt. Die Teams haben ununterbrochen daran gearbeitet, das Problem anzugehen, indem sie nach Möglichkeit Maßnahmen ergriffen haben, um auf die offiziellen Software-Patches zu warten, und diese Patches eingeführt haben, sobald sie verfügbar sind. Alle Systeme, die auf unseren Hosting- und Unternehmensplattformen hätten betroffen sein können, wurden jetzt gepatcht. Nicht jede Website läuft mit der neuesten PHP-Version. Einige verwenden noch ältere Versionen, zum Beispiel, weil bestimmte Plugins oder Anwendungen mit einem neueren PHP-Release nicht kompatibel sind. Unsere Teams gingen die extra Meile und passten auch die Sicherheitskorrekturen für einige ältere PHP-Versionen an. Dieser Prozess wird als Backporting bezeichnet: Anpassen eines Sicherheitspatches, so dass es auch mit einer älteren Softwareversion funktioniert. Es geht nicht nur darum, eine Datei zu kopieren. Unsere Ingenieure müssen die notwendigen Änderungen manuell implementieren, kompilieren und testen. Das PHP-Projekt unterstützt derzeit offiziell die Versionen 8.2 bis 8.5. Ältere Versionen erhalten keine regelmäßigen Sicherheitsupdates mehr. Es versteht sich von selbst, wenn Sie auf einer älteren Version von PHP sind, aktualisieren Sie dies bitte.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 28. September 2026 um 08:45 UTCinvestigating

   Eine unserer Verbindungen zwischen Großbritannien und Irland ist derzeit unten. Die Redundanten Pfade funktionieren wie erwartet, so dass keine Auswirkungen erwartet werden, aber das Netzwerk sollte zu diesem Zeitpunkt als gefährdet betrachtet werden. Wir haben einen Fall mit dem Carrier offen und warten auf Updates.

2. 28. September 2026 um 19:32 UTCresolved

   Eine unserer Verbindungen zwischen Großbritannien und Irland ist derzeit unten. Die Redundanten Pfade funktionieren wie erwartet, so dass keine Auswirkungen erwartet werden, aber das Netzwerk sollte zu diesem Zeitpunkt als gefährdet betrachtet werden. Wir haben einen Fall mit dem Carrier offen und warten auf Updates. Die Fluggesellschaft hat bestätigt, dass das Problem gelöst ist, wir haben es überwacht und freuen uns, die Risikoperiode jetzt zu beenden.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. Juli 2026 um 09:21 UTCinvestigating

   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.

2. 10. Juli 2026 um 15:55 UTCinvestigating

   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.

3. 10. Juli 2026 um 23:04 UTCmonitoring

   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.

4. 13. Juli 2026 um 08:08 UTCresolved

   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.

1. 15. Mai 2026 um 12:23 UTCinvestigating

   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.

2. 15. Mai 2026 um 13:12 UTCmonitoring

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

3. 15. Mai 2026 um 13:28 UTCresolved

   This incident has been resolved.

1. 27. März 2026 um 12:41 UTCidentified

   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.

2. 27. März 2026 um 13:08 UTCidentified

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

3. 27. März 2026 um 13:10 UTCmonitoring

   We will continue to monitor over the next couple of hours

4. 27. März 2026 um 17:10 UTCresolved

   This incident has been resolved.

1. 3. Februar 2026 um 09:27 UTCinvestigating

   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.

2. 3. Februar 2026 um 15:53 UTCinvestigating

   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.

3. 3. Februar 2026 um 16:52 UTCinvestigating

   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.

4. 3. Februar 2026 um 16:59 UTCresolved

   This incident has been resolved.

1. 24. Oktober 2025 um 13:10 UTCinvestigating

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

2. 24. Oktober 2025 um 13:11 UTCidentified

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

3. 24. Oktober 2025 um 15:54 UTCresolved

   This incident has been resolved.

1. 2. Oktober 2025 um 13:36 UTCinvestigating

   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.

2. 2. Oktober 2025 um 18:23 UTCinvestigating

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

3. 3. Oktober 2025 um 07:37 UTCresolved

   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.

1. 17. Juni 2025 um 08:04 UTCinvestigating

   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.

2. 17. Juni 2025 um 18:52 UTCmonitoring

   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.

3. 19. Juni 2025 um 10:11 UTCresolved

   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.

1. 8. April 2025 um 01:22 UTCidentified

   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.

2. 15. April 2025 um 13:40 UTCidentified

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

3. 16. April 2025 um 09:15 UTCresolved

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

1. 28. August 2024 um 08:10 UTCinvestigating

   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.

2. 28. August 2024 um 12:16 UTCmonitoring

   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.

3. 28. August 2024 um 14:34 UTCresolved

   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.

1. 19. April 2024 um 17:29 UTCinvestigating

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

2. 19. April 2024 um 18:16 UTCmonitoring

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

3. 20. April 2024 um 10:40 UTCresolved

   This incident has been resolved.

1. 10. November 2023 um 10:54 UTCinvestigating

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

2. 10. November 2023 um 11:20 UTCmonitoring

   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.

3. 11. November 2023 um 17:26 UTCresolved

   This incident has been resolved.

1. 20. August 2023 um 18:54 UTCinvestigating

   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.

2. 20. August 2023 um 23:19 UTCmonitoring

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

3. 21. August 2023 um 08:31 UTCresolved

   This incident has been resolved.

1. 26. Juli 2023 um 08:00 UTCidentified

   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.

2. 27. Juli 2023 um 07:46 UTCresolved

   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.

1. 3. Juli 2023 um 08:52 UTCinvestigating

   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.

2. 18. Juli 2023 um 13:43 UTCresolved

   This incident has been resolved.

1. 10. Mai 2023 um 09:05 UTCidentified

   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.

2. 12. Juni 2023 um 08:58 UTCresolved

   This incident has been resolved.

1. 29. Dezember 2022 um 12:01 UTCinvestigating

   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]

2. 29. Dezember 2022 um 12:25 UTCidentified

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

3. 29. Dezember 2022 um 16:16 UTCmonitoring

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

4. 30. Dezember 2022 um 10:03 UTCresolved

   This incident has been resolved.

1. 13. Dezember 2022 um 18:19 UTCinvestigating

   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.

2. 13. Dezember 2022 um 18:27 UTCresolved

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