Sucuri Outage History

Started Sep 22, 2026, 03:00 PM UTC· resolved Sep 28, 2026, 07:12 PM UTC

1. identified Sep 22, 2026, 03:00 PM UTC

   We are currently experiencing network degradation affecting connectivity in parts of Asia due to multiple concurrent subsea cable outages impacting our upstream provider's backbone capacity. A new outage affecting the C2C cable system has occurred today and is contributing to the packet loss currently observed in the region. As traffic is being rerouted across the remaining available network paths, customers may experience intermittent packet loss, increased latency, and potential connectivity degradation when accessing services through affected routes. Our upstream provider is aware of the issue and is actively working to restore the affected network capacity. We are closely monitoring the situation and will continue to provide updates as additional information becomes available. Please note: Any estimated restoration times provided by the upstream provider are tentative and may change as the investigation and restoration efforts progress. We apologize for any disruption this may cause and appreciate your patience while the upstream network infrastructure is being restored.

2. resolved Sep 28, 2026, 07:12 PM UTC

   This incident has been resolved, and connectivity has stabilized across the affected region. While some carrier and subsea cable restoration activities remain ongoing across parts of Asia, network conditions have returned to a stable state. Visitors accessing your sites from affected regions may still experience minor increases in latency or slightly slower load times until all restoration work is fully completed. We have proactively routed traffic through the healthiest and most reliable available network paths and will continue to closely monitor connectivity, performance, and traffic conditions to ensure your sites remain available, protected, and performing as expected. If you continue to experience any connectivity or performance issues, our Support team is available to assist. Thank you for your patience and understanding while this incident was being resolved.

Read the full incident report →

Started Sep 03, 2026, 10:04 PM UTC· resolved Sep 04, 2026, 12:53 AM UTC

1. investigating Sep 03, 2026, 10:04 PM UTC

   We are currently experiencing degraded performance in WAF Cluster 3. 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. investigating Sep 03, 2026, 10:11 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 03, 2026, 10:40 PM UTC

   The degraded performance is over and we are monitoring the results.

4. resolved Sep 04, 2026, 12:53 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 23, 2026, 04:55 PM UTC· resolved Apr 23, 2026, 06:20 PM UTC

1. identified Apr 23, 2026, 04:55 PM UTC

   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. monitoring Apr 23, 2026, 05:47 PM UTC

   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. resolved Apr 23, 2026, 06:20 PM UTC

   This incident is now resolved.

Read the full incident report →

Started Apr 03, 2026, 12:22 AM UTC· resolved Apr 03, 2026, 01:05 AM UTC

1. investigating Apr 03, 2026, 12:22 AM UTC

   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. monitoring Apr 03, 2026, 12:44 AM UTC

   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. resolved Apr 03, 2026, 01:05 AM UTC

   This incident is now resolved.

Read the full incident report →

Started Apr 02, 2026, 08:19 AM UTC· resolved Apr 06, 2026, 09:06 PM UTC

1. investigating Apr 02, 2026, 08:19 AM UTC

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

2. identified Apr 02, 2026, 09:03 AM UTC

   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. identified Apr 02, 2026, 10:12 AM UTC

   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. identified Apr 02, 2026, 11:23 AM UTC

   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. identified Apr 02, 2026, 12:32 PM UTC

   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. identified Apr 02, 2026, 05:57 PM UTC

   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. identified Apr 02, 2026, 07:23 PM UTC

   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. identified Apr 03, 2026, 12:26 AM UTC

   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. identified Apr 03, 2026, 07:41 AM UTC

   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. identified Apr 03, 2026, 10:38 AM UTC

    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. identified Apr 03, 2026, 06:48 PM UTC

    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. monitoring Apr 03, 2026, 08:49 PM UTC

    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. monitoring Apr 05, 2026, 03:48 PM UTC

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

14. monitoring Apr 06, 2026, 04:51 PM UTC

    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. resolved Apr 06, 2026, 09:06 PM UTC

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

Read the full incident report →

Started Mar 31, 2026, 09:23 AM UTC· resolved Mar 31, 2026, 09:54 AM UTC

1. monitoring Mar 31, 2026, 09:23 AM UTC

   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. resolved Mar 31, 2026, 09:54 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 18, 2026, 03:39 PM UTC· resolved Mar 18, 2026, 03:39 PM UTC

1. resolved Mar 18, 2026, 03:39 PM UTC

   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.

Read the full incident report →

Started Mar 04, 2026, 01:27 PM UTC· resolved Mar 04, 2026, 04:48 PM UTC

1. investigating Mar 04, 2026, 01:27 PM UTC

   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. identified Mar 04, 2026, 01:35 PM UTC

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

3. monitoring Mar 04, 2026, 03:29 PM UTC

   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. resolved Mar 04, 2026, 04:48 PM UTC

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

Read the full incident report →

Started Feb 26, 2026, 04:36 PM UTC· resolved Feb 26, 2026, 09:44 PM UTC

1. investigating Feb 26, 2026, 04:36 PM UTC

   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. resolved Feb 26, 2026, 09:44 PM UTC

   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.

Read the full incident report →

Started Feb 24, 2026, 04:54 PM UTC· resolved Feb 24, 2026, 04:54 PM UTC

1. resolved Feb 24, 2026, 04:54 PM UTC

   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.

Read the full incident report →

Started Feb 06, 2026, 11:50 PM UTC· resolved Feb 07, 2026, 08:02 AM UTC

1. investigating Feb 06, 2026, 11:50 PM UTC

   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. resolved Feb 07, 2026, 08:02 AM UTC

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

Read the full incident report →

Started Jan 07, 2026, 06:40 PM UTC· resolved Jan 07, 2026, 07:19 PM UTC

1. investigating Jan 07, 2026, 06:40 PM UTC

   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. identified Jan 07, 2026, 06:42 PM UTC

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

3. monitoring Jan 07, 2026, 06:47 PM UTC

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

4. resolved Jan 07, 2026, 07:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 09, 2025, 12:11 PM UTC· resolved Dec 10, 2025, 03:34 PM UTC

1. investigating Dec 09, 2025, 12:11 PM UTC

   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. investigating Dec 09, 2025, 12:40 PM UTC

   We are continuing to investigate this issue.

3. resolved Dec 10, 2025, 03:34 PM UTC

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

Read the full incident report →

Started Nov 11, 2025, 03:20 PM UTC· resolved Dec 09, 2025, 06:59 PM UTC

1. investigating Nov 11, 2025, 03:20 PM UTC

   We are currently investigating this issue.

2. identified Nov 12, 2025, 04:18 PM UTC

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

3. monitoring Nov 12, 2025, 06:04 PM UTC

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

4. resolved Dec 09, 2025, 06:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 11, 2025, 03:37 AM UTC· resolved Nov 11, 2025, 04:35 AM UTC

1. investigating Nov 11, 2025, 03:37 AM UTC

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

2. resolved Nov 11, 2025, 04:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2025, 04:56 PM UTC· resolved Sep 03, 2025, 08:02 PM UTC

1. investigating Sep 02, 2025, 04:56 PM UTC

   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. resolved Sep 03, 2025, 08:02 PM UTC

   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.

Read the full incident report →

Started Aug 27, 2025, 08:48 AM UTC· resolved Aug 28, 2025, 02:35 PM UTC

1. identified Aug 27, 2025, 08:48 AM UTC

   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. monitoring Aug 27, 2025, 02:31 PM UTC

   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. resolved Aug 28, 2025, 02:35 PM UTC

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

Read the full incident report →

Started Mar 27, 2025, 05:45 PM UTC· resolved Mar 27, 2025, 11:31 PM UTC

1. investigating Mar 27, 2025, 05:45 PM UTC

   Our network monitoring tools have detected some intermittent network issues impacting Cluster 7 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. monitoring Mar 27, 2025, 07:58 PM UTC

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

3. resolved Mar 27, 2025, 11:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 15, 2025, 07:18 PM UTC· resolved Mar 15, 2025, 08:31 PM UTC

1. investigating Mar 15, 2025, 07:18 PM UTC

   We are currently investigating an issue preventing users from submitting support requests.

2. monitoring Mar 15, 2025, 07:51 PM UTC

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

3. resolved Mar 15, 2025, 08:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 15, 2025, 01:09 AM UTC· resolved Jan 15, 2025, 01:27 PM UTC

1. investigating Jan 15, 2025, 01:09 AM UTC

   We are currently experiencing intermittent service issues. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible.

2. monitoring Jan 15, 2025, 02:09 AM UTC

   The intermittent service issue at our North America West location is no longer occurring. We are closely monitoring the situation to ensure continued stability.

3. resolved Jan 15, 2025, 01:27 PM UTC

   This incident has been resolved.

Read the full incident report →