Sucuri の障害履歴

1. 2026年10月21日 15:14 UTCmonitoring

   Sucuriは、最近公開された重要なPHP脆弱性、CVE-2026-109618およびCVE-2026-109619に関連する攻撃パターンを緩和するために、追加のWebアプリケーションファイアウォール(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日 15:00 UTCidentified

   現在、当社は、上流プロバイダーの背骨容量に影響を及ぼす複数の同時海底ケーブルによるアジアの部分における接続に影響を及ぼすネットワークの劣化を経験しています。 現在、C2Cケーブルシステムに影響を及ぼす新しい停電が発生し、現在、地域に観察されているパケット損失に貢献しています。 トラフィックは、利用可能なネットワークパス全体で再ルートされているため、顧客は、影響を受けたルートを介してサービスにアクセスする際に、断続的なパケット損失、レイテンシの増加、および潜在的な接続劣化が発生する可能性があります。 当社の上流プロバイダは、問題を認識し、影響を受けるネットワーク容量を回復するために積極的に取り組んでいます。 状況を密接に監視し、追加情報として更新を引き続き提供してまいります。 注意: 上流プロバイダーが提供する推定回復時間は暫定的であり、調査および修復の努力の進捗状況として変更することがあります。 上流ネットワークインフラが復元されている間、この問題が起き、忍耐を認める可能性があることをお詫び申し上げます.

2. 2026年9月28日 19:12 UTCresolved

   このインシデントは、影響を受けた地域を横断して解決され、接続が安定しています。 一部のキャリアおよび海底ケーブル復元活動は、アジアの部分で継続的を維持していますが、ネットワークの状態は安定した状態に戻りました。 影響を受けた地域からサイトにアクセスする訪問者は、すべての復元作業が完全に完了するまで、レイテンシーまたはわずかに遅い負荷時間でマイナーな増加が発生することがあります。 私たちは、健康と最も信頼性の高い利用可能なネットワークパスを介して積極的にトラフィックをルーティングし、あなたのサイトが利用可能であることを保証するために、接続、パフォーマンス、およびトラフィック条件を密接に監視し、保護され、期待どおりに実行します。 今後も、コネクティビティやパフォーマンスに関する問題が発生した場合は、当社のサポートチームがお手伝いいたします。 この事件が解決された間、あなたの忍耐と理解をありがとう.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月3日 22:04 UTCinvestigating

   現在、WAFクラスター3で劣化性能を発揮しています。 当社のチームは、この場所を介してルートされたトラフィックに影響を与えるネットワークの不安定性を特定しました。これにより、断続的な接続の問題、レイテンシの増加、または一部の顧客の一時的な利用不能が発生する可能性があります。 問題を積極的に調査し、可能な限り迅速に全安定性を回復させます。 詳細は、更新情報として提供いたします.

2. 2026年9月3日 22:11 UTCinvestigating

   今後もこの問題について調査を続けてまいります.

3. 2026年9月3日 22:40 UTCmonitoring

   劣化した性能は上回っており、その結果を監視しています.

4. 2026年9月4日 0:53 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年4月23日 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. 2026年4月23日 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. 2026年4月23日 18:20 UTCresolved

   This incident is now resolved.

1. 2026年4月3日 0: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日 0: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日 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. 2026年4月2日 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. 2026年4月3日 0: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日 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. 2026年4月3日 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. 2026年4月5日 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. 2026年4月6日 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. 2026年4月6日 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. 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日 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. 2026年3月4日 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. 2026年3月4日 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. 2026年3月4日 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. 2026年3月4日 16:48 UTCresolved

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

1. 2026年2月28日 18:29 UTCinvestigating

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

2. 2026年2月28日 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. 2026年2月28日 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. 2026年2月28日 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. 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日 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. 2026年3月1日 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. 2026年2月26日 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. 2026年2月26日 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. 2026年2月24日 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. 2026年2月6日 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. 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日 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. 2026年1月7日 18:42 UTCidentified

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

3. 2026年1月7日 18:47 UTCmonitoring

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

4. 2026年1月7日 19: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日 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. 2025年11月11日 15:20 UTCinvestigating

   We are currently investigating this issue.

2. 2025年11月12日 16:18 UTCidentified

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

3. 2025年11月12日 18:04 UTCmonitoring

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

4. 2025年12月9日 18: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日 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. 2025年9月3日 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. 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日 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. 2025年8月28日 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. 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日 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. 2025年7月28日 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. 2025年7月29日 15:58 UTCresolved

   This incident has been resolved.