История сбоев Sucuri

1. 21 октября 2026 г. в 15:14 UTCmonitoring

   Sucuri внедрила дополнительные правила брандмауэра веб-приложений (WAF), чтобы помочь смягчить шаблоны атак, связанные с недавно раскрытыми критическими уязвимостями PHP, CVE-2026-109618 и CVE-2026-109619. Мы отслеживаем эту защиту и связанный с ней трафик. Эти правила обеспечивают дополнительный уровень защиты трафика, проходящего через брандмауэр сайта Sucuri. Защита WAF не заменяет исправление PHP на исходном сервере. Мы настоятельно рекомендуем связаться с вашим хостинг-провайдером или администратором сервера, чтобы как можно скорее применить соответствующее обновление безопасности PHP. Команда разработчиков PHP выпустила исправления в PHP 8.5.12, 8.4.27, 8.3.36 и 8.2.35. Ваша операционная система или поставщик хостинга также могут предоставлять исправленные пакеты. Пожалуйста, ознакомьтесь с официальными рекомендациями по безопасности PHP для руководства по исправлению. https://www.php.net/archive/2026.php#2026-10-21-5

Автоматический перевод официального обновления инцидента.

1. 22 сентября 2026 г. в 15:00 UTCidentified

   В настоящее время мы испытываем деградацию сети, влияющую на связь в некоторых частях Азии из-за многочисленных одновременных отключений подводных кабелей, влияющих на магистральную пропускную способность нашего провайдера. Сегодня произошел новый сбой, влияющий на кабельную систему C2C, и это способствует потере пакетов, наблюдаемой в регионе. Поскольку трафик перенаправляется по остальным доступным сетевым путям, клиенты могут испытывать периодическую потерю пакетов, повышенную задержку и потенциальную деградацию подключения при доступе к услугам через затронутые маршруты. Наш провайдер в курсе проблемы и активно работает над восстановлением затронутой сети. Мы внимательно следим за ситуацией и будем продолжать предоставлять обновления по мере поступления дополнительной информации. Обратите внимание: любое предполагаемое время восстановления, предоставленное поставщиком услуг, является предварительным и может измениться по мере продвижения исследований и восстановительных работ. Мы приносим извинения за любые сбои, которые это может вызвать, и ценим ваше терпение, пока восстанавливается инфраструктура сети.

2. 28 сентября 2026 г. в 19:12 UTCresolved

   Этот инцидент был урегулирован, и связь в пострадавшем регионе стабилизировалась. В то время как в некоторых частях Азии продолжаются работы по восстановлению морских и подводных кабелей, сетевые условия вернулись в стабильное состояние. Посетители, посещающие ваши сайты из пострадавших регионов, могут по-прежнему испытывать незначительное увеличение задержки или немного более медленное время загрузки, пока все восстановительные работы не будут полностью завершены. Мы активно направляем трафик по самым здоровым и надежным доступным сетевым маршрутам и будем продолжать внимательно следить за подключением, производительностью и условиями трафика, чтобы ваши сайты оставались доступными, защищенными и работали так, как ожидалось. Если вы продолжаете испытывать какие-либо проблемы с подключением или производительностью, наша команда поддержки готова помочь. Спасибо за ваше терпение и понимание, пока этот инцидент решался.

Автоматический перевод официального обновления инцидента.

1. 3 сентября 2026 г. в 22:04 UTCinvestigating

   В настоящее время мы испытываем ухудшение производительности в кластере WAF 3. Наша команда определила нестабильность сети, влияющую на трафик, направляемый через это место, что может привести к периодическим проблемам с подключением, увеличению задержки или временной недоступности для некоторых клиентов. Мы активно изучаем этот вопрос и работаем над тем, чтобы как можно быстрее восстановить полную стабильность. Обновления будут предоставляться по мере поступления дополнительной информации.

2. 3 сентября 2026 г. в 22:11 UTCinvestigating

   Мы продолжаем расследование этого вопроса.

3. 3 сентября 2026 г. в 22:40 UTCmonitoring

   Пониженная производительность закончилась, и мы отслеживаем результаты.

4. 4 сентября 2026 г. в 00:53 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 23 апреля 2026 г. в 16:55 UTCidentified

   We have identified an SSL-related issue associated with maintenance work that was recently completed in Paris. Our team is actively working on it, and we will post another update shortly.

2. 23 апреля 2026 г. в 17:47 UTCmonitoring

   We have implemented a fix for the SSL certificate issue in Paris. Our teams are actively monitoring to validate recovery. Further updates will follow as we confirm full resolution.

3. 23 апреля 2026 г. в 18:20 UTCresolved

   This incident is now resolved.

1. 3 апреля 2026 г. в 00:22 UTCinvestigating

   We’re investigating delays in when changes made in the dashboard are applied. Saves may take longer than normal to take effect. We’ll update this incident as we learn more or when behavior is back to normal.

2. 3 апреля 2026 г. в 00:44 UTCmonitoring

   We’ve resolved the delay in when dashboard changes take effect. You should see normal apply times now. We’re continuing to monitor and will post shortly that the issue is resolved.

3. 3 апреля 2026 г. в 01:05 UTCresolved

   This incident is now resolved.

1. 2 апреля 2026 г. в 08:19 UTCinvestigating

   We are currently working on mitigating the impact of the DDoS attack in the Paris region. Will inform about updates

2. 2 апреля 2026 г. в 09:03 UTCidentified

   Mitigation has been applied to the IP address that was targeted by a high volume of traffic in the Paris region. The region is currently stable. We will provide further updates shortly.

3. 2 апреля 2026 г. в 10:12 UTCidentified

   The attack is still ongoing, and the affected IP is still under mitigation. The Paris region is currently stable. We’ll provide further updates shortly.

4. 2 апреля 2026 г. в 11:23 UTCidentified

   The attack is still ongoing, and the affected IP is still under mitigation. The Paris region is currently stable. We will keep you informed

5. 2 апреля 2026 г. в 12:32 UTCidentified

   We are continuing to mitigate an ongoing attack targeting an IP in the Paris region. The region is currently stable. We will share further updates as more information becomes available.

6. 2 апреля 2026 г. в 17:57 UTCidentified

   We’re still mitigating an ongoing attack aimed at infrastructure in the Paris and Frankfurt regions. Cluster 28 is impacted in these regions at this time. We’ll post another update when we have more to share.

7. 2 апреля 2026 г. в 19:23 UTCidentified

   We continue to respond to sustained malicious traffic targeting our footprint in Paris, Frankfurt, and London. Cluster 28 remains affected in those locations. We’ll follow up as soon as we have further information on this incident.

8. 3 апреля 2026 г. в 00:26 UTCidentified

   We remain engaged countering sustained malicious traffic affecting our Paris, Frankfurt, and London footprint. Cluster 28 is still impacted in those locations. We will post again when we have additional information on this incident.

9. 3 апреля 2026 г. в 07:41 UTCidentified

   We are continuing to respond to ongoing malicious traffic affecting our infrastructure in Paris, Frankfurt, and London. Cluster 28 remains impacted in these locations. We will provide an update as soon as more information about this incident becomes available.

10. 3 апреля 2026 г. в 10:38 UTCidentified

    We are still actively responding to ongoing malicious traffic impacting our infrastructure in Paris, Frankfurt, and London. Cluster 28 continues to be affected in these locations. We will share another update as soon as additional information on this incident is available.

11. 3 апреля 2026 г. в 18:48 UTCidentified

    We are continuing to work with our network team to mitigate the source of incoming attack traffic. At the moment, we still see packet loss and cluster 28 is still affected. We will provide further updates shortly.

12. 3 апреля 2026 г. в 20:49 UTCmonitoring

    We have completed a series of mitigations addressing elevated load on our network. These measures required more time than we initially expected to implement safely. We appreciate your patience and understand the impact this has had. We are now observing improved latency and overall performance, consistent with a substantial reduction in the traffic that was contributing to the issue. Engineering teams remain engaged and are actively monitoring systems and external checks to confirm stability. We will provide a further update if conditions change or once we are confident the incident is fully resolved. If you continue to see problems with a specific site or region, please contact support with details so we can investigate.

13. 5 апреля 2026 г. в 15:48 UTCmonitoring

    We are still monitoring closely after the applied mitigations. No new issues observed in our checks; we will update if that changes.

14. 6 апреля 2026 г. в 16:51 UTCmonitoring

    Increased traffic levels persist and are causing higher latency in certain regions. We are coordinating with our networking team and continuing to monitor. We will update again as conditions change.

15. 6 апреля 2026 г. в 21:06 UTCresolved

    Additional mitigations have restored traffic and latency to normal levels in the affected regions. We will continue routine monitoring. This incident is resolved.

1. 31 марта 2026 г. в 09:23 UTCmonitoring

   We are currently working on mitigating the impact of the DDoS attack in the Paris and London regions. The attack has been stopped now, and we continue to monitor the situation.

2. 31 марта 2026 г. в 09:54 UTCresolved

   This incident has been resolved.

1. 18 марта 2026 г. в 15:39 UTCresolved

   Users whose traffic was served from our Dallas, Chicago, and San Jose Points of Presence (POPs) experienced redirect loops. Only a subset of customers who have the option to redirect would be affected. This was caused by cache configuration changes at those locations. We reverted those changes, redirect behavior returned to normal, and the issue is resolved.

1. 4 марта 2026 г. в 13:27 UTCinvestigating

   We are currently experiencing degraded performance in the London region. Our team has identified network instability affecting traffic routed through this location, which may result in intermittent connectivity issues, increased latency, or temporary unavailability for some customers. We are actively investigating the issue and working to restore full stability as quickly as possible. Updates will be provided as more information becomes available.

2. 4 марта 2026 г. в 13:35 UTCidentified

   The issue impacting the London region has been identified. Mitigation steps are underway, and we are closely monitoring the recovery process.

3. 4 марта 2026 г. в 15:29 UTCmonitoring

   The corrective actions have been applied, and routing in the London region has been stabilized. All services are currently operating as expected. We are actively monitoring performance metrics to confirm full recovery.

4. 4 марта 2026 г. в 16:48 UTCresolved

   The London region has remained stable without any further issues. This incident is now resolved.

1. 28 февраля 2026 г. в 18:29 UTCinvestigating

   We are currently mitigating a network-related issue affecting traffic originating from the Paris and London (EU) regions.

2. 28 февраля 2026 г. в 18:49 UTCidentified

   Mitigations have been applied to an IP address that was targeted with the high amount of traffic within the Paris and London regions. Both regions are currently stable, however sites on cluster 35 are still affected and we will provide further updates shortly.

3. 28 февраля 2026 г. в 19:06 UTCmonitoring

   The implemented mitigations have demonstrated stability across both regions currently. Sites on cluster 35 remain affected by these measures, and we continue monitoring traffic to ultimately remove them.

4. 28 февраля 2026 г. в 22:05 UTCmonitoring

   We are continuing to monitor the impacted cluster, cluster 35, on the Paris and London regions. We will provide another status update within the next few hours unless we see any significant changes.

5. 1 марта 2026 г. в 03:07 UTCmonitoring

   We're still tracking the situation with cluster 35 in Paris and London. Any significant developments will be communicated promptly.

6. 1 марта 2026 г. в 14:41 UTCmonitoring

   Our deployed mitigations continue to show stable performance in both regions. Sites on cluster 35 are still affected by these safeguards while we monitor conditions to eventually lift them.

7. 1 марта 2026 г. в 15:16 UTCresolved

   The issue affecting cluster 35 in the Paris and London regions has been resolved. All services have been restored to normal operation. This incident is now resolved.

1. 26 февраля 2026 г. в 16:36 UTCinvestigating

   Our network monitoring tools have detected some intermittent network issues impacting Asia region that has resulted in degraded performance. Our network engineering team are continuing to investigate the issue and we will post further updates once we have more detailed information. We hope to have the issue resolved shortly and we apologize for any trouble experienced.

2. 26 февраля 2026 г. в 21:44 UTCresolved

   Our network monitoring tools have detected some intermittent network issues impacting one of our Asia POPs, in Singapore region that has resulted in degraded performance. The issue was localized only in that specific region and was related to some upstream network's issues outside our infra It is already normalized, but our network engineering team are continuing to investigate the issue and monitoring everything. We apologize for any trouble experienced.

1. 24 февраля 2026 г. в 16:54 UTCresolved

   Yesterday, February 23rd, around 2:00pm EST - our network monitoring tools have detected some intermittent network issues impacting one of our North America POPs, in west coast region that has resulted in degraded performance. The issue was localized only in that specific region and was related to some upstream network's issues outside our infra It is already normalized, but our network engineering team are continuing to investigate the issue and monitoring everything. We apologize for any trouble experienced.

1. 6 февраля 2026 г. в 23:50 UTCinvestigating

   We are currently mitigating a network-related issue affecting a subset of traffic originating from the Paris (EU) region. As part of this mitigation, a specific IP associated with Cluster 39 has been temporarily blackholed in the Paris PoP to protect overall platform stability. Impact: Some customers accessing their websites from Paris and parts of the EU may experience connectivity issues. Traffic from other regions remains unaffected. No data loss has been observed. Mitigation Actions: Cluster 39 has been temporarily blackholed in the Paris PoP as a containment measure. Impacted customers may experience service disruption in that region until the issue is fully resolved. Support: If you are experiencing issues accessing your site from the Paris/EU region, please contact Support so we can promptly move your site to an alternate cluster.

2. 7 февраля 2026 г. в 08:02 UTCresolved

   The network related issue that was affecting Cluster 39 in the Paris (EU) region has been resolved and the IP is no longer blackholed.

1. 7 января 2026 г. в 18:40 UTCinvestigating

   We are currently experiencing an issue affecting the WAF 1.0 Captcha feature. Our engineering team is currently deploying a fix and we should have everything normalized in less than 1 hour.

2. 7 января 2026 г. в 18:42 UTCidentified

   Our engineering team is currently deploying a fix and we should have everything normalized in about 30 minutes

3. 7 января 2026 г. в 18:47 UTCmonitoring

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

4. 7 января 2026 г. в 19:19 UTCresolved

   This incident has been resolved.

1. 9 декабря 2025 г. в 12:11 UTCinvestigating

   We are currently experiencing an issue affecting the WAF Dashboard at waf.sucuri.net in EU. Customers may be unable to log in or access dashboard functionality at this time. Our engineering team is actively investigating and working to resolve the issue. We will continue to provide updates as soon as more information becomes available.

2. 9 декабря 2025 г. в 12:40 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 декабря 2025 г. в 15:34 UTCresolved

   This incident has been resolved. Thank you for your patience and understanding, if you are still having issues, please open a support ticket.

1. 11 ноября 2025 г. в 15:20 UTCinvestigating

   We are currently investigating this issue.

2. 12 ноября 2025 г. в 16:18 UTCidentified

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

3. 12 ноября 2025 г. в 18:04 UTCmonitoring

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

4. 9 декабря 2025 г. в 18:59 UTCresolved

   This incident has been resolved.

1. 11 ноября 2025 г. в 03:37 UTCinvestigating

   We're currently investigating the potential where allowlisted IP's may continue to experience firewall blocks.

2. 11 ноября 2025 г. в 04:35 UTCresolved

   This incident has been resolved.

1. 2 сентября 2025 г. в 16:56 UTCinvestigating

   We are currently experiencing an issue with paypal on checkout due to changes in paypal policy we are working diligently to get an update from paypal and will release more information soon. For now we request you use a valid credit card.

2. 3 сентября 2025 г. в 20:02 UTCresolved

   The PayPal checkout issue has been addressed. Normal functionality has been restored, and users can once again complete purchases using PayPal. We apologize for any inconvenience caused and appreciate your patience.

1. 27 августа 2025 г. в 08:48 UTCidentified

   Our monitoring systems have identified intermittent network disruptions affecting the North America West region, resulting in periods of degraded performance. At this time, the issue appears to be localized to this region. The root cause has been traced to one of our upstream providers currently experiencing technical difficulties, which in turn has impacted our WAF service. The provider is actively working on remediation, and our network engineering team is closely monitoring the situation to ensure service stability. We will continue to provide updates as more information becomes available and will confirm once services have been fully restored. We sincerely apologize for any inconvenience this may cause and appreciate your patience as we work to resolve the matter promptly.

2. 27 августа 2025 г. в 14:31 UTCmonitoring

   The issue affecting the North America West region has been successfully isolated. Service performance has stabilized, and our network engineering team is actively monitoring the service to ensure continued stability. We will provide a final update once we have confirmed full resolution.

3. 28 августа 2025 г. в 14:35 UTCresolved

   This incident has been resolved. Thank you for your patience and understanding, if you are still having issues, please open a support ticket.

1. 27 июля 2025 г. в 11:14 UTCinvestigating

   We are currently experiencing an issue affecting the WAF Dashboard at waf.sucuri.net. Customers may be unable to log in or access dashboard functionality at this time. Our engineering team is actively investigating and working to resolve the issue. We will continue to provide updates as soon as more information becomes available. Please note that Firewall protection, Monitoring, and Backup services remain fully operational and are not impacted. This incident affects only the dashboard interface used to configure WAF settings.

2. 27 июля 2025 г. в 11:48 UTCinvestigating

   We are aware of an issue that is also affecting customers' ability to log in to their support dashboard. We are investigating this issue and will provide updates as more information becomes available.

3. 27 июля 2025 г. в 15:36 UTCidentified

   The issue has been identified, we are working quickly to implement a fix, and we will provide an update as soon as the solution is in place

4. 28 июля 2025 г. в 17:13 UTCmonitoring

   We’ve applied a fix to address the underlying issue and are currently observing system performance and stability. Our team continues to monitor all affected services closely to ensure full recovery. Further updates will be shared as needed.

5. 29 июля 2025 г. в 15:58 UTCresolved

   This incident has been resolved.