Elevated Errors for Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), Amsterdam (RTM)
Elevated Errors for Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), Amsterdam (RTM)
10 October 2025, 11:30 UTC
10 October 2025, 11:30 UTC
We are investigating elevated errors to our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) Points of Presence (POPs).
All other products and services are unaffected by this incident.
10 October 2025, 21:11 UTC
10 October 2025, 21:11 UTC
Our engineers believe they have identified contributing factor causing the issue impacting our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs .
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.
10 October 2025, 23:08 UTC
10 October 2025, 23:08 UTC
Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs.
All other locations and services are unaffected.
11 October 2025, 00:18 UTC
11 October 2025, 00:18 UTC
Engineering has deployed a fix and have confirmed a gradual recovery to our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs. We will continue to monitor until we’ve confirmed that the customer experience has been fully restored.
All other locations and services are unaffected.
11 October 2025, 01:26 UTC
11 October 2025, 01:26 UTC
Engineering has confirmed that our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs have been fully restored. Customers may have experienced increased latency or elevated timeout errors from 11:30
on the 10th of October 2025 to 00:30 on the 11th of October 2025 UTC.
This incident is resolved.
To offer feedback on our status page, click " Give Feedback "
Status Post, Created Date/Time: 2025-10-10 21:10:07 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.