Historial de interrupciones de Simply Hosting undefined Servers

1. 22 de octubre de 2026 a las 15:41 UTCmonitoring

   El 20 de octubre se anunciaron dos vulnerabilidades de PHP críticas: CVE-2026-109618 y CVE-2026-109619. Estas vulnerabilidades tienen una puntuación CVSS de 9.2 y podrían potencialmente ser explotadas para ejecutar código remotamente en un servidor sin requerir autenticación. Las vulnerabilidades pueden afectar todas las versiones de PHP desde PHP 5. Si utiliza PHP en su Bare Metal, Dedicated Server, VPS, recomendamos encarecidamente actualizar PHP con los parches disponibles. Si está ejecutando cPanel/Plesk, también hay parches disponibles, y debe aplicarlos. Si usted tiene un sitio/s que se ejecuta en estos productos de nosotros, le recomendamos que revise su uso de PHP y la versión que está siendo utilizada por usted o sus clientes y tome acciones relevantes. Si usted ha gestionado servidor/vps con nosotros, entonces estos son / han sido parcheados por nuestros equipos.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de octubre de 2026 a las 13:16 UTCmonitoring

   El 20 de octubre se anunciaron dos vulnerabilidades de PHP críticas: CVE-2026-109618 y CVE-2026-109619. Estas vulnerabilidades tienen una puntuación CVSS de 9.2 y podrían potencialmente ser explotadas para ejecutar código remotamente en un servidor sin requerir autenticación. Las vulnerabilidades pueden afectar todas las versiones de PHP desde PHP 5. Si utiliza PHP en su Bare Metal, Dedicated Server, VPS, recomendamos encarecidamente actualizar PHP con los parches disponibles. Si está ejecutando cPanel/Plesk, también hay parches disponibles, y debe aplicarlos. Si usted tiene un sitio/s que se ejecuta en estos productos de nosotros, le recomendamos que revise su uso de PHP y la versión que está siendo utilizada por usted o sus clientes y tome acciones relevantes. Si usted ha gestionado servidor/vps con nosotros, entonces estos son / han sido parcheados por nuestros equipos.

2. 22 de octubre de 2026 a las 15:31 UTCmonitoring

   El 20 de octubre de 2026, el Equipo Mundial de Seguridad de PHP anunció dos vulnerabilidades de seguridad críticas. The official security updates were released the following day. Dado que millones de sitios web de todo el mundo dependen de PHP, el anuncio causó comprensiblemente preocupación, y recibimos un gran número de preguntas de nuestros clientes. Por cierto: la seguridad de su sitio web es extremadamente importante. ¿Las buenas noticias? Tomamos acción inmediata. Los equipos han estado trabajando sin parar para abordar el problema, tomando medidas de mitigación cuando sea posible mientras esperan los parches oficiales de software, y desplegando esos parches tan pronto como se pusieron a disposición. Todos los sistemas que podrían haber sido impactados en nuestras plataformas de hosting " se han reparado ahora. No todos los sitios web se ejecutan en la última versión PHP. Algunos todavía usan versiones anteriores, por ejemplo porque ciertos plugins o aplicaciones son incompatibles con una versión PHP más reciente. Nuestros equipos fueron la milla extra y también adaptaron las soluciones de seguridad para algunas versiones PHP antiguas. Este proceso se llama backporting: adaptación de un parche de seguridad por lo que también funciona con una versión anterior del software. No es simplemente una cuestión de copiar un archivo. Nuestros ingenieros tienen que implementar, compilar y probar manualmente los cambios necesarios. El proyecto PHP actualmente soporta las versiones 8.2 a 8.5. Las versiones más antiguas ya no reciben actualizaciones regulares de seguridad. Sin embargo, sin decir, si usted está en una versión anterior de PHP, por favor actualice esto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 28 de septiembre de 2026 a las 8:45 UTCinvestigating

   Uno de nuestros enlaces de Reino Unido a Irlanda está actualmente baja. Las rutas de Redundant funcionan como se espera para que no se espere ningún impacto, pero la red debe considerarse en riesgo en este momento. Tenemos un caso abierto con el transportista y estamos esperando actualizaciones.

2. 28 de septiembre de 2026 a las 19:32 UTCresolved

   Uno de nuestros enlaces de Reino Unido a Irlanda está actualmente baja. Las rutas de Redundant funcionan como se espera para que no se espere ningún impacto, pero la red debe considerarse en riesgo en este momento. Tenemos un caso abierto con el transportista y estamos esperando actualizaciones. El Transportista ha confirmado que la cuestión se resuelve, hemos monitoreado y estamos contentos de terminar el período de riesgo.

Traducido automáticamente desde la actualización oficial del incidente.

1. 10 de julio de 2026 a las 9: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 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 8: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 de mayo de 2026 a las 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 de mayo de 2026 a las 13:12 UTCmonitoring

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

3. 15 de mayo de 2026 a las 13:28 UTCresolved

   This incident has been resolved.

1. 27 de marzo de 2026 a las 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 de marzo de 2026 a las 13:08 UTCidentified

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

3. 27 de marzo de 2026 a las 13:10 UTCmonitoring

   We will continue to monitor over the next couple of hours

4. 27 de marzo de 2026 a las 17:10 UTCresolved

   This incident has been resolved.

1. 3 de febrero de 2026 a las 9: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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 16:59 UTCresolved

   This incident has been resolved.

1. 24 de octubre de 2025 a las 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 de octubre de 2025 a las 13:11 UTCidentified

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

3. 24 de octubre de 2025 a las 15:54 UTCresolved

   This incident has been resolved.

1. 2 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 7: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 de junio de 2025 a las 8: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 de junio de 2025 a las 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 de junio de 2025 a las 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 de abril de 2025 a las 1: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 de abril de 2025 a las 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 de abril de 2025 a las 9: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 de agosto de 2024 a las 8: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 de agosto de 2024 a las 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 de agosto de 2024 a las 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 de abril de 2024 a las 17:29 UTCinvestigating

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

2. 19 de abril de 2024 a las 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 de abril de 2024 a las 10:40 UTCresolved

   This incident has been resolved.

1. 10 de noviembre de 2023 a las 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 de noviembre de 2023 a las 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 de noviembre de 2023 a las 17:26 UTCresolved

   This incident has been resolved.

1. 20 de agosto de 2023 a las 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 de agosto de 2023 a las 23:19 UTCmonitoring

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

3. 21 de agosto de 2023 a las 8:31 UTCresolved

   This incident has been resolved.

1. 26 de julio de 2023 a las 8: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 de julio de 2023 a las 7: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 de julio de 2023 a las 8: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 de julio de 2023 a las 13:43 UTCresolved

   This incident has been resolved.

1. 10 de mayo de 2023 a las 9: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 de junio de 2023 a las 8:58 UTCresolved

   This incident has been resolved.

1. 29 de diciembre de 2022 a las 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 de diciembre de 2022 a las 12:25 UTCidentified

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

3. 29 de diciembre de 2022 a las 16:16 UTCmonitoring

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

4. 30 de diciembre de 2022 a las 10:03 UTCresolved

   This incident has been resolved.

1. 13 de diciembre de 2022 a las 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 de diciembre de 2022 a las 18:27 UTCresolved

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