Historial de interrupciones de Sucuri

1. September 3, 2026 at 10:04 PM UTCinvestigating

   Actualmente estamos experimentando un rendimiento degradado en WAF Cluster 3. Nuestro equipo ha identificado la inestabilidad de la red que afecta al tráfico a través de esta ubicación, lo que puede resultar en problemas de conectividad intermitente, mayor latencia o falta de disponibilidad temporal para algunos clientes. Estamos investigando activamente la cuestión y trabajando para restaurar la plena estabilidad lo antes posible. Se proporcionarán actualizaciones a medida que se disponga de más información.

2. September 3, 2026 at 10:11 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. September 3, 2026 at 10:40 PM UTCmonitoring

   El rendimiento degradado ha terminado y estamos monitoreando los resultados.

4. September 4, 2026 at 12:53 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. April 23, 2026 at 4:55 PM 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. April 23, 2026 at 5:47 PM 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. April 23, 2026 at 6:20 PM UTCresolved

   This incident is now resolved.

1. April 3, 2026 at 12:22 AM 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. April 3, 2026 at 12:44 AM 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. April 3, 2026 at 1:05 AM UTCresolved

   This incident is now resolved.

1. April 2, 2026 at 8:19 AM UTCinvestigating

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

2. April 2, 2026 at 9:03 AM 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. April 2, 2026 at 10:12 AM 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. April 2, 2026 at 11:23 AM 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. April 2, 2026 at 12:32 PM 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. April 2, 2026 at 5:57 PM 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. April 2, 2026 at 7:23 PM 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. April 3, 2026 at 12:26 AM 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. April 3, 2026 at 7:41 AM 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. April 3, 2026 at 10:38 AM 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. April 3, 2026 at 6:48 PM 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. April 3, 2026 at 8:49 PM 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. April 5, 2026 at 3:48 PM UTCmonitoring

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

14. April 6, 2026 at 4:51 PM 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. April 6, 2026 at 9:06 PM 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. March 31, 2026 at 9:23 AM 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. March 31, 2026 at 9:54 AM UTCresolved

   This incident has been resolved.

1. March 18, 2026 at 3:39 PM 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. March 4, 2026 at 1:27 PM 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. March 4, 2026 at 1:35 PM UTCidentified

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

3. March 4, 2026 at 3:29 PM 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. March 4, 2026 at 4:48 PM UTCresolved

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

1. February 28, 2026 at 6:29 PM UTCinvestigating

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

2. February 28, 2026 at 6:49 PM 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. February 28, 2026 at 7:06 PM 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. February 28, 2026 at 10:05 PM 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. March 1, 2026 at 3:07 AM UTCmonitoring

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

6. March 1, 2026 at 2:41 PM 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. March 1, 2026 at 3:16 PM 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. February 26, 2026 at 4:36 PM 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. February 26, 2026 at 9:44 PM 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. February 24, 2026 at 4:54 PM 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. February 6, 2026 at 11:50 PM 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. February 7, 2026 at 8:02 AM 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. January 7, 2026 at 6:40 PM 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. January 7, 2026 at 6:42 PM UTCidentified

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

3. January 7, 2026 at 6:47 PM UTCmonitoring

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

4. January 7, 2026 at 7:19 PM UTCresolved

   This incident has been resolved.

1. December 9, 2025 at 12:11 PM 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. December 9, 2025 at 12:40 PM UTCinvestigating

   We are continuing to investigate this issue.

3. December 10, 2025 at 3:34 PM 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. November 11, 2025 at 3:20 PM UTCinvestigating

   We are currently investigating this issue.

2. November 12, 2025 at 4:18 PM UTCidentified

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

3. November 12, 2025 at 6:04 PM UTCmonitoring

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

4. December 9, 2025 at 6:59 PM UTCresolved

   This incident has been resolved.

1. November 11, 2025 at 3:37 AM UTCinvestigating

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

2. November 11, 2025 at 4:35 AM UTCresolved

   This incident has been resolved.

1. September 2, 2025 at 4:56 PM 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. September 3, 2025 at 8:02 PM 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. August 27, 2025 at 8:48 AM 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. August 27, 2025 at 2:31 PM 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. August 28, 2025 at 2:35 PM 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. July 27, 2025 at 11:14 AM 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. July 27, 2025 at 11:48 AM 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. July 27, 2025 at 3:36 PM 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. July 28, 2025 at 5:13 PM 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. July 29, 2025 at 3:58 PM UTCresolved

   This incident has been resolved.

1. March 27, 2025 at 5:45 PM UTCinvestigating

   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. March 27, 2025 at 7:58 PM UTCmonitoring

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

3. March 27, 2025 at 11:31 PM UTCresolved

   This incident has been resolved.

1. March 15, 2025 at 7:18 PM UTCinvestigating

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

2. March 15, 2025 at 7:51 PM UTCmonitoring

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

3. March 15, 2025 at 8:31 PM UTCresolved

   This incident has been resolved.