Sucuri 장애 기록

1. 2026년 10월 21일 오후 3:14 UTCmonitoring

   Sucuri는 최근 공개 된 중요한 PHP 취약점, CVE-2026-109618 및 CVE-2026-109619와 관련된 공격 패턴을 완화하는 데 도움이 추가 웹 응용 방화벽 (WAF) 규칙을 배포했습니다. 우리는 이러한 보호 및 관련 트래픽을 모니터링하고 있습니다. 이 규칙은 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. 2026년 9월 22일 오후 3:00 UTCidentified

   우리는 현재 많은 동시 잠수함 공급자의 backbone 수용량에 영향을 미치는 다수 concurrent subsea 케이블 부족 때문에 아시아의 부속에 있는 연결에 영향을 미치는 네트워크 degradation를 경험하고 있습니다. C2C 케이블 시스템에 영향을 미치는 새로운 결과는 오늘 발생했으며 현재 지역에서 관찰 된 패킷 손실에 기여하고 있습니다. 트래픽은 나머지 사용 가능한 네트워크 경로를 통해 다시 시작되고, 고객은 영향을받는 루트를 통해 서비스에 액세스 할 때 간헐적 인 패킷 손실, 증가 지연 및 잠재적 인 연결 향상을 경험할 수 있습니다. 우리의 상류 공급자는 문제점의 aware이고 영향을 받는 네트워크 수용량을 복원하기 위하여 활발합니다. 우리는 상황을 모니터링하고 추가 정보를 사용할 때 업데이트를 계속 제공 할 것입니다. 주의: 상류 공급자에 의해 제공된 어떤 추정된 회복 시간은 Tentative이고 조사와 회복 노력 진도로 변화할지도 모릅니다. 우리는이 모든 혼란에 대해 사과하고 업스트림 네트워크 인프라가 복원 된 동안 당신의 인내력을 평가 할 수 있습니다.

2. 2026년 9월 28일 오후 7:12 UTCresolved

   이 사건은 해결되고, 연결성은 영향을받는 지역에 걸쳐 안정화되었습니다. 몇몇 운반대 및 subsea 케이블 restoration 활동은 아시아의 부속의 맞은편에 남아 있는 동안, 네트워크 상태는 안정되어 있는 국가에 돌려보냅니다. 영향을받는 지역에서 사이트의 방문자는 여전히 모든 복원 작업이 완전히 완료 될 때까지 지연 또는 약간 느리게로드 시간에 미성년자 증가를 경험할 수 있습니다. 우리는 가장 건강하고 믿을 수 있는 유효한 네트워크 경로를 통해 proactively routed 소통량이 있고, 당신의 위치를 지키기 위하여 연결, 성과 및 교통 조건을, 보호하고, 예상대로 실행할 것입니다. 연결이나 성능 문제가 계속되는 경우 지원팀이 도움을 받을 수 있습니다. 이 사건이 해결 된 동안 당신의 인내와 이해에 감사드립니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 3일 오후 10:04 UTCinvestigating

   우리는 현재 WAF 클러스터 3의 성능 향상 우리의 팀은 네트워크 불안정성 트래픽이이 위치를 통해 분기에 영향을 미치는 것으로, 이는 간헐적인 연결 문제, 증가한 대기 시간, 또는 일부 고객에 대한 임시 불연성에 발생할 수 있습니다. 우리는 적극적으로 가능한 한 빨리 전체 안정성을 복원하는 문제 및 작업에 투자하고 있습니다. 업데이트는 더 많은 정보로 제공됩니다.

2. 2026년 9월 3일 오후 10:11 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 9월 3일 오후 10:40 UTCmonitoring

   Degraded 성과는 위에 이고 우리는 결과를 감시하고 있습니다.

4. 2026년 9월 4일 오전 12:53 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 4월 23일 오후 4: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. 2026년 4월 23일 오후 5: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. 2026년 4월 23일 오후 6:20 UTCresolved

   This incident is now resolved.

1. 2026년 4월 3일 오전 12: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. 2026년 4월 3일 오전 12: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. 2026년 4월 3일 오전 1:05 UTCresolved

   This incident is now resolved.

1. 2026년 4월 2일 오전 8:19 UTCinvestigating

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

2. 2026년 4월 2일 오전 9: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. 2026년 4월 2일 오전 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. 2026년 4월 2일 오전 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. 2026년 4월 2일 오후 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. 2026년 4월 2일 오후 5: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. 2026년 4월 2일 오후 7: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. 2026년 4월 3일 오전 12: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. 2026년 4월 3일 오전 7: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. 2026년 4월 3일 오전 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. 2026년 4월 3일 오후 6: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. 2026년 4월 3일 오후 8: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. 2026년 4월 5일 오후 3: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. 2026년 4월 6일 오후 4: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. 2026년 4월 6일 오후 9: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. 2026년 3월 31일 오전 9: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. 2026년 3월 31일 오전 9:54 UTCresolved

   This incident has been resolved.

1. 2026년 3월 18일 오후 3: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. 2026년 3월 4일 오후 1: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. 2026년 3월 4일 오후 1:35 UTCidentified

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

3. 2026년 3월 4일 오후 3: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. 2026년 3월 4일 오후 4:48 UTCresolved

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

1. 2026년 2월 28일 오후 6:29 UTCinvestigating

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

2. 2026년 2월 28일 오후 6: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. 2026년 2월 28일 오후 7: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. 2026년 2월 28일 오후 10: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. 2026년 3월 1일 오전 3:07 UTCmonitoring

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

6. 2026년 3월 1일 오후 2: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. 2026년 3월 1일 오후 3: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. 2026년 2월 26일 오후 4: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. 2026년 2월 26일 오후 9: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. 2026년 2월 24일 오후 4: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. 2026년 2월 6일 오후 11: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. 2026년 2월 7일 오전 8: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. 2026년 1월 7일 오후 6: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. 2026년 1월 7일 오후 6:42 UTCidentified

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

3. 2026년 1월 7일 오후 6:47 UTCmonitoring

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

4. 2026년 1월 7일 오후 7:19 UTCresolved

   This incident has been resolved.

1. 2025년 12월 9일 오후 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. 2025년 12월 9일 오후 12:40 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 12월 10일 오후 3: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. 2025년 11월 11일 오후 3:20 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 11월 12일 오후 4:18 UTCidentified

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

3. 2025년 11월 12일 오후 6:04 UTCmonitoring

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

4. 2025년 12월 9일 오후 6:59 UTCresolved

   This incident has been resolved.

1. 2025년 11월 11일 오전 3:37 UTCinvestigating

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

2. 2025년 11월 11일 오전 4:35 UTCresolved

   This incident has been resolved.

1. 2025년 9월 2일 오후 4: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. 2025년 9월 3일 오후 8: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. 2025년 8월 27일 오전 8: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. 2025년 8월 27일 오후 2: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. 2025년 8월 28일 오후 2: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. 2025년 7월 27일 오전 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. 2025년 7월 27일 오전 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. 2025년 7월 27일 오후 3: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. 2025년 7월 28일 오후 5: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. 2025년 7월 29일 오후 3:58 UTCresolved

   This incident has been resolved.