Sucuri driftsforstyrrelser

1. 21. oktober 2026 kl. 15.14 UTCmonitoring

   Sucuri har indsat yderligere Web Application Firewall (WAF) regler til at hjælpe med at afbøde angreb mønstre i forbindelse med de nyligt afslørede kritiske PHP sårbarheder, CVE- 2026- 109618 og CVE- 2026- 109619. Vi overvåger disse beskyttelsesforanstaltninger og den dermed forbundne trafik. Disse regler giver et ekstra lag af beskyttelse for trafik passerer gennem Sucuri hjemmeside firewall. WAF beskyttelse erstatter ikke patching PHP på din oprindelsesserver. Vi anbefaler stærkt at kontakte din hosting udbyder eller server administrator til at anvende den relevante PHP sikkerhedsopdatering så hurtigt som muligt. PHP Development Team har udgivet rettelser i PHP 8.5.12, 8.4.27, 8.3.36 og 8.2.35. Dit operativsystem eller hosting leverandør kan også levere lappede pakker. Du bedes gennemgå den officielle PHP sikkerhedsrådgivning for oprydning vejledning. http: / / www.php.net / archive / 2026.php # 2026-10-21-5

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. september 2026 kl. 15.00 UTCidentified

   Vi oplever i øjeblikket netværksnedbrydning, der påvirker forbindelse i dele af Asien på grund af flere samtidige undersøiske kabeludfald, der påvirker vores opstrømsudbyders rygrad kapacitet. En ny afbrydelse, der påvirker C2C-kabelsystemet, har fundet sted i dag og bidrager til det pakketab, der i øjeblikket konstateres i regionen. Da trafikken omdirigeres på tværs af de resterende tilgængelige netveje, kan kunderne opleve intermitterende pakketab, øget latenstid og potentiel kapacitetsforringelse, når de får adgang til tjenester via berørte ruter. Vores opstrømsleverandør er klar over problemet og arbejder aktivt på at genoprette den berørte netværkskapacitet. Vi følger nøje situationen og vil fortsat give opdateringer, efterhånden som yderligere oplysninger bliver tilgængelige. Bemærk: Eventuelle estimerede restaureringstider, som leveres af opstrømsleverandøren, er foreløbige og kan ændre sig, efterhånden som undersøgelsen og restaureringsindsatsen skrider frem. Vi undskylder for eventuelle forstyrrelser dette kan forårsage og værdsætter din tålmodighed, mens opstrøms netværk infrastruktur bliver genoprettet.

2. 28. september 2026 kl. 19.12 UTCresolved

   Denne hændelse er blevet løst, og forbindelsen er stabiliseret på tværs af den berørte region. Mens der stadig foregår retablering af skibe og undersøiske kabler i dele af Asien, er netværksforholdene vendt tilbage til en stabil tilstand. Besøgende adgang dine websteder fra berørte regioner kan stadig opleve mindre stigninger i latency eller lidt langsommere belastning gange, indtil alle restaurering arbejde er fuldt afsluttet. Vi har proaktivt drevet trafik gennem de sundeste og mest pålidelige tilgængelige netværksstier og vil fortsat nøje overvåge konnektivitet, ydeevne og trafikforhold for at sikre, at dine websteder forbliver tilgængelige, beskyttede og fungerer som forventet. Hvis du fortsætter med at opleve nogen forbindelse eller performance problemer, vores Support team er til rådighed til at hjælpe. Tak for Deres tålmodighed og forståelse, mens denne hændelse blev løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. september 2026 kl. 22.04 UTCinvestigating

   Vi oplever i øjeblikket forringet ydeevne i WAF Cluster 3. Vores team har identificeret netværk ustabilitet påvirker trafik dirigeret gennem denne placering, hvilket kan resultere i intermitterende forbindelse spørgsmål, øget latency, eller midlertidig manglende tilgængelighed for nogle kunder. Vi undersøger aktivt spørgsmålet og arbejder på at genoprette fuld stabilitet så hurtigt som muligt. Opdateringer vil blive leveret som mere information bliver tilgængelig.

2. 3. september 2026 kl. 22.11 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 3. september 2026 kl. 22.40 UTCmonitoring

   Den nedbrudte ydeevne er forbi, og vi overvåger resultaterne.

4. 4. september 2026 kl. 00.53 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 18.20 UTCresolved

   This incident is now resolved.

1. 3. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 01.05 UTCresolved

   This incident is now resolved.

1. 2. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 09.54 UTCresolved

   This incident has been resolved.

1. 18. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 16.48 UTCresolved

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

1. 28. februar 2026 kl. 18.29 UTCinvestigating

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

2. 28. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 18.42 UTCidentified

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

3. 7. januar 2026 kl. 18.47 UTCmonitoring

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

4. 7. januar 2026 kl. 19.19 UTCresolved

   This incident has been resolved.

1. 9. december 2025 kl. 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. december 2025 kl. 12.40 UTCinvestigating

   We are continuing to investigate this issue.

3. 10. december 2025 kl. 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. november 2025 kl. 15.20 UTCinvestigating

   We are currently investigating this issue.

2. 12. november 2025 kl. 16.18 UTCidentified

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

3. 12. november 2025 kl. 18.04 UTCmonitoring

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

4. 9. december 2025 kl. 18.59 UTCresolved

   This incident has been resolved.

1. 11. november 2025 kl. 03.37 UTCinvestigating

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

2. 11. november 2025 kl. 04.35 UTCresolved

   This incident has been resolved.

1. 2. september 2025 kl. 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. september 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. august 2025 kl. 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. juli 2025 kl. 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. juli 2025 kl. 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. juli 2025 kl. 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. juli 2025 kl. 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. juli 2025 kl. 15.58 UTCresolved

   This incident has been resolved.