Degraded Performance on Paris, Frankfurt, and London Regions

Update timeline

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.