Simply Hosting undefined Servers driftsforstyrrelser

1. 28. oktober 2026 kl. 09.21 UTCinvestigating

   En af vores britiske forbindelser til Irland er i øjeblikket nede. De Redundant stier fungerer som forventet, så ingen indvirkning forventes, men netværket bør betragtes som udsat for risiko på dette tidspunkt. Vi har en sag åben med luftfartsselskabet og afventer opdateringer.

2. 28. oktober 2026 kl. 10.38 UTCidentified

   Vores luftfartsselskab har bekræftet problemet og arbejder på at løse det.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. oktober 2026 kl. 15.41 UTCmonitoring

   Den 20. oktober blev to kritiske PHP sårbarheder annonceret: CVE- 2026- 109618 og CVE- 2026- 109619. Disse sårbarheder har en CVSS score på 9.2 og kunne potentielt udnyttes til at udføre kode eksternt på en server uden at kræve godkendelse. Sårbarhederne kan påvirke alle PHP-versioner startende fra PHP 5. Hvis du bruger PHP på din Bare Metal, Dedikeret Server, VPS, anbefaler vi stærkt opdatering PHP med de patches, der er tilgængelige. Hvis du kører cPanel / Plesk, patches er også tilgængelige, og du bør anvende dem. Hvis du har et websted / s kører på disse produkter fra os, anbefaler vi, at du gennemgår din PHP-brug og den version, der bliver brugt af dig eller dine kunder og tage relevante handlinger. Hvis du har forvaltet server / vps med os, så disse er / er blevet lappet af vores hold.

2. 28. oktober 2026 kl. 10.08 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. oktober 2026 kl. 13.16 UTCmonitoring

   Den 20. oktober blev to kritiske PHP sårbarheder annonceret: CVE- 2026- 109618 og CVE- 2026- 109619. Disse sårbarheder har en CVSS score på 9.2 og kunne potentielt udnyttes til at udføre kode eksternt på en server uden at kræve godkendelse. Sårbarhederne kan påvirke alle PHP-versioner startende fra PHP 5. Hvis du bruger PHP på din Bare Metal, Dedikeret Server, VPS, anbefaler vi stærkt opdatering PHP med de patches, der er tilgængelige. Hvis du kører cPanel / Plesk, patches er også tilgængelige, og du bør anvende dem. Hvis du har et websted / s kører på disse produkter fra os, anbefaler vi, at du gennemgår din PHP-brug og den version, der bliver brugt af dig eller dine kunder og tage relevante handlinger. Hvis du har forvaltet server / vps med os, så disse er / er blevet lappet af vores hold.

2. 22. oktober 2026 kl. 15.31 UTCmonitoring

   Den 20. oktober 2026 annoncerede Global PHP Security Team to kritiske sikkerhedssårbarheder. De officielle sikkerhedsopdateringer blev udgivet dagen efter. Da millioner af hjemmesider i hele verden er afhængige af PHP, gav meddelelsen forståeligt nok anledning til bekymring, og vi modtog en lang række spørgsmål fra vores kunder. Ret så: sikkerheden på din hjemmeside er yderst vigtig. Den gode nyhed? Vi greb straks ind. Holdene har arbejdet nonstop for at løse problemet, tage formildende foranstaltninger, hvor det er muligt, mens de venter på de officielle software-patches, og rulle ud disse patches, så snart de blev tilgængelige. Alle systemer, der kunne have været påvirket på vores hosting & selskab platforme er nu blevet lappet. Ikke hver hjemmeside kører på den nyeste PHP version. Nogle bruger stadig ældre versioner, for eksempel fordi visse plugins eller programmer er uforenelige med en nyere PHP udgivelse. Vores hold gik den ekstra mil og også tilpasset sikkerhedsrettelser for nogle ældre PHP versioner. Denne proces kaldes backporting: tilpasning af en sikkerhedspatch, så det også fungerer med en ældre softwareversion. Det handler ikke kun om at kopiere en fil. Vores ingeniører skal manuelt implementere, kompilere og teste de nødvendige ændringer. PHP-projektet understøtter i øjeblikket officielt versioner 8.2 til 8.5. Ældre versioner modtager ikke længere regelmæssige sikkerhedsopdateringer. Det siger sig selv, hvis du er på en ældre version af PHP, bedes du opdatere dette.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 28. september 2026 kl. 08.45 UTCinvestigating

   En af vores britiske forbindelser til Irland er i øjeblikket nede. De Redundant stier fungerer som forventet, så ingen indvirkning forventes, men netværket bør betragtes som udsat for risiko på dette tidspunkt. Vi har en sag åben med luftfartsselskabet og afventer opdateringer.

2. 28. september 2026 kl. 19.32 UTCresolved

   En af vores britiske forbindelser til Irland er i øjeblikket nede. De Redundant stier fungerer som forventet, så ingen indvirkning forventes, men netværket bør betragtes som udsat for risiko på dette tidspunkt. Vi har en sag åben med luftfartsselskabet og afventer opdateringer. Carrier har bekræftet, at problemet er løst, at vi har overvåget og er glade for nu at afslutte den risikoperiode.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juli 2026 kl. 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 kl. 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 kl. 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 kl. 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. maj 2026 kl. 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. maj 2026 kl. 13.12 UTCmonitoring

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

3. 15. maj 2026 kl. 13.28 UTCresolved

   This incident has been resolved.

1. 27. marts 2026 kl. 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. marts 2026 kl. 13.08 UTCidentified

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

3. 27. marts 2026 kl. 13.10 UTCmonitoring

   We will continue to monitor over the next couple of hours

4. 27. marts 2026 kl. 17.10 UTCresolved

   This incident has been resolved.

1. 3. februar 2026 kl. 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 kl. 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 kl. 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 kl. 16.59 UTCresolved

   This incident has been resolved.

1. 24. oktober 2025 kl. 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 kl. 13.11 UTCidentified

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

3. 24. oktober 2025 kl. 15.54 UTCresolved

   This incident has been resolved.

1. 2. oktober 2025 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 10.40 UTCresolved

   This incident has been resolved.

1. 10. november 2023 kl. 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 kl. 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 kl. 17.26 UTCresolved

   This incident has been resolved.

1. 20. august 2023 kl. 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 kl. 23.19 UTCmonitoring

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

3. 21. august 2023 kl. 08.31 UTCresolved

   This incident has been resolved.

1. 26. juli 2023 kl. 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 kl. 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 kl. 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 kl. 13.43 UTCresolved

   This incident has been resolved.

1. 10. maj 2023 kl. 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 kl. 08.58 UTCresolved

   This incident has been resolved.

1. 29. december 2022 kl. 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. december 2022 kl. 12.25 UTCidentified

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

3. 29. december 2022 kl. 16.16 UTCmonitoring

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

4. 30. december 2022 kl. 10.03 UTCresolved

   This incident has been resolved.