Histórico de interrupções do Simply Hosting undefined Servers

1. 22 Here 2026 da 15:41 UTCmonitoring

   Em 20 de outubro, duas vulnerabilidades críticas do PHP foram anunciadas: CVE-2026-109618 e CVE-2026-109619. Essas vulnerabilidades têm uma pontuação CVSS de 9.2 e poderiam potencialmente ser exploradas para executar código remotamente em um servidor sem precisar de autenticação. As vulnerabilidades podem afetar todas as versões PHP a partir do PHP 5. Se você usar PHP em seu Bare Metal, Dedicated Server, VPS, recomendamos fortemente atualizar PHP com os patches que estão disponíveis. Se você estiver executando cPanel/Plesk, patches também estão disponíveis, e você deve aplicá-los. Se você tem um site/s rodando nesses produtos de nós, recomendamos que você reveja seu uso do PHP e a versão que está sendo usada por você ou seus clientes e tome medidas relevantes. Se você tiver gerenciado servidor/vps conosco, então estes são/foram corrigidos por nossas equipes.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Here 2026 da 13:16 UTCmonitoring

   Em 20 de outubro, duas vulnerabilidades críticas do PHP foram anunciadas: CVE-2026-109618 e CVE-2026-109619. Essas vulnerabilidades têm uma pontuação CVSS de 9.2 e poderiam potencialmente ser exploradas para executar código remotamente em um servidor sem precisar de autenticação. As vulnerabilidades podem afetar todas as versões PHP a partir do PHP 5. Se você usar PHP em seu Bare Metal, Dedicated Server, VPS, recomendamos fortemente atualizar PHP com os patches que estão disponíveis. Se você estiver executando cPanel/Plesk, patches também estão disponíveis, e você deve aplicá-los. Se você tem um site/s rodando nesses produtos de nós, recomendamos que você reveja seu uso do PHP e a versão que está sendo usada por você ou seus clientes e tome medidas relevantes. Se você tiver gerenciado servidor/vps conosco, então estes são/foram corrigidos por nossas equipes.

2. 22 Here 2026 da 15:31 UTCmonitoring

   Em 20 de outubro de 2026, a Global PHP Security Team anunciou duas vulnerabilidades críticas de segurança. As atualizações oficiais de segurança foram lançadas no dia seguinte. Uma vez que milhões de sites em todo o mundo dependem do PHP, o anúncio causou preocupação, e recebemos um grande número de perguntas de nossos clientes. Com razão: a segurança do seu site é extremamente importante. As boas notícias? Tomamos medidas imediatas. As equipes têm trabalhado sem parar para resolver o problema, tomando medidas atenuantes, sempre que possível, enquanto aguardam os patches de software oficiais, e lançando esses patches assim que estiverem disponíveis. Todos os sistemas que poderiam ter sido impactados em nossas plataformas de hospedagem e empresa foram agora corrigidos. Nem todo site é executado na versão mais recente do PHP. Alguns ainda usam versões mais antigas, por exemplo, porque certos plugins ou aplicativos são incompatíveis com uma versão PHP mais recente. Nossas equipes foram a milha extra e também adaptaram as correções de segurança para algumas versões PHP mais antigas. Este processo é chamado backporting: adaptando um patch de segurança para que ele também funcione com uma versão de software mais antiga. Não é simplesmente uma questão de copiar um arquivo. Nossos engenheiros têm que implementar, compilar e testar manualmente as mudanças necessárias. O projeto PHP atualmente suporta oficialmente versões 8.2 a 8.5. Versões mais antigas já não recebem atualizações de segurança regulares. É evidente que, se você estiver em uma versão mais antiga do PHP, por favor, atualize isso.

Traduzido automaticamente da atualização oficial do incidente.

1. 28 Gwengolo 2026 da 08:45 UTCinvestigating

   Uma das nossas ligações do Reino Unido à Irlanda está actualmente em baixo. Os caminhos Redundant estão funcionando como esperado, por isso não é esperado nenhum impacto, mas a rede deve ser considerada em risco neste momento. Temos um caso aberto com a transportadora e estamos aguardando atualizações.

2. 28 Gwengolo 2026 da 19:32 UTCresolved

   Uma das nossas ligações do Reino Unido à Irlanda está actualmente em baixo. Os caminhos Redundant estão funcionando como esperado, por isso não é esperado nenhum impacto, mas a rede deve ser considerada em risco neste momento. Temos um caso aberto com a transportadora e estamos aguardando atualizações. O Transportador confirmou que a questão está resolvida, nós monitoramos e estamos felizes por agora terminar o período de risco.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gouere 2026 da 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 Gouere 2026 da 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 Gouere 2026 da 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 Gouere 2026 da 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 Mae 2026 da 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 Mae 2026 da 13:12 UTCmonitoring

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

3. 15 Mae 2026 da 13:28 UTCresolved

   This incident has been resolved.

1. 27 Meurzh 2026 da 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 Meurzh 2026 da 13:08 UTCidentified

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

3. 27 Meurzh 2026 da 13:10 UTCmonitoring

   We will continue to monitor over the next couple of hours

4. 27 Meurzh 2026 da 17:10 UTCresolved

   This incident has been resolved.

1. 3 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 16:59 UTCresolved

   This incident has been resolved.

1. 24 Here 2025 da 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 Here 2025 da 13:11 UTCidentified

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

3. 24 Here 2025 da 15:54 UTCresolved

   This incident has been resolved.

1. 2 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Mezheven 2025 da 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 Mezheven 2025 da 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 Mezheven 2025 da 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 Ebrel 2025 da 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 Ebrel 2025 da 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 Ebrel 2025 da 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 Eost 2024 da 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 Eost 2024 da 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 Eost 2024 da 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 Ebrel 2024 da 17:29 UTCinvestigating

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

2. 19 Ebrel 2024 da 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 Ebrel 2024 da 10:40 UTCresolved

   This incident has been resolved.

1. 10 Du 2023 da 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 Du 2023 da 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 Du 2023 da 17:26 UTCresolved

   This incident has been resolved.

1. 20 Eost 2023 da 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 Eost 2023 da 23:19 UTCmonitoring

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

3. 21 Eost 2023 da 08:31 UTCresolved

   This incident has been resolved.

1. 26 Gouere 2023 da 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 Gouere 2023 da 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 Gouere 2023 da 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 Gouere 2023 da 13:43 UTCresolved

   This incident has been resolved.

1. 10 Mae 2023 da 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 Mezheven 2023 da 08:58 UTCresolved

   This incident has been resolved.

1. 29 Kerzu 2022 da 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 Kerzu 2022 da 12:25 UTCidentified

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

3. 29 Kerzu 2022 da 16:16 UTCmonitoring

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

4. 30 Kerzu 2022 da 10:03 UTCresolved

   This incident has been resolved.

1. 13 Kerzu 2022 da 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 Kerzu 2022 da 18:27 UTCresolved

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