Possible CDN Performance Impact in our Amsterdam (RTM), London (LON), and the Paris (PAR) Point of Presence
Possible CDN Performance Impact in our Amsterdam (RTM), London (LON), and the Paris (PAR) Point of Presence
12 November 2025, 17:50 UTC
12 November 2025, 17:50 UTC
We're currently investigating potential impact to performance with our CDN services.
12 November 2025, 18:42 UTC
12 November 2025, 18:42 UTC
Our engineers are continuing to investigate a performance impact to Europe, Global POP Network (SEV1/0) service.
All other locations and services are unaffected.
12 November 2025, 19:18 UTC
12 November 2025, 19:18 UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Europe, Global POP Network (SEV1/0) status page component.
We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.
All other products and services are unaffected by this incident.
12 November 2025, 19:19 UTC
12 November 2025, 19:19 UTC
Engineering has confirmed the impact to Europe, Global POP Network (SEV1/0) service has been mitigated.
To provide further clarity on this incident: we initially posted to global components out of an abundance of caution while we investigated. Following further investigation, we can confirm the performance impact was isolated to our Amsterdam (RTM), London (LON), Marseille (MRS), Paris (PAR) and Vienna (VIE) POPs.
We've updated both the status post title and listed components to reflect these findings. This incident remains mitigated.
12 November 2025, 21:41 UTC
12 November 2025, 21:41 UTC
Engineering has confirmed that London (LON), Marseille (MRS), Vienna (VIE), Paris (PAR), Amsterdam (RTM) POPs has been fully restored. Customers may have experienced elevated errors and/or latency from 17:50 to 18:15 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-11-12 18:17:01 UTC
Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.