Elevated Errors for Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR)

Incident
29 November 2025, 21:52 UTC

Elevated Errors for Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR)

Status: closed
Start: 29 November 2025, 20:13 UTC
End: 29 November 2025, 21:52 UTC
Duration: 1 hour 39 minutes
Affected Components:
Platform North America Europe Frankfurt (FRA) London (LCY) Chicago (CHI) London (LHR) Lisbon (LIS) Detroit (DTW) Paris (PAR) Rome (FCO)
Investigating

29 November 2025, 20:13 UTC

29 November 2025, 20:13 UTC

We are investigating elevated errors to our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) Points of Presence (POPs)

All other products and services are unaffected by this incident.

Identified

29 November 2025, 20:52 UTC

29 November 2025, 20:52 UTC

Our engineers believe they have identified contributing factor causing the issue impacting our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) 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.

Monitoring

29 November 2025, 21:27 UTC

29 November 2025, 21:27 UTC

Engineering has confirmed the impact to our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) POPs has been mitigated.

Resolved

29 November 2025, 21:52 UTC

29 November 2025, 21:52 UTC

Engineering has confirmed that our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) POPs  have been fully restored. Customers may have experienced elevated errors and increased latency  from 20:13  to 21:20  UTC.

This incident is resolved.

12/12 A retrospective into this incident identified that London (LHR) had also experienced elevated errors and increased periods of latency as a result of this incident. Component has been added to reflect accurate data.

To offer feedback on our status page, click " Give Feedback

Status Post, Created Date/Time: 2025-11-29 20:35:29 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.