North America with Possible Impact

Incident
18 November 2026, 04:07 UTC

North America with Possible Impact

Status: closed
Start: 18 November 2026, 01:50 UTC
End: 18 November 2026, 04:07 UTC
Duration: 2 hours 17 minutes
Affected Components:
Platform North America Ashburn (IAD) Atlanta (PDK) Boston (BOS) Calgary (YYC) Chicago (CHI) Chicago (ORD) Columbus (CMH) Dallas (DFW) Denver (DEN) Detroit (DTW) Honolulu (HNL) Houston (IAH) Jacksonville (JAX) Kansas City (MCI) Los Angeles (HHR) Los Angeles (BUR) Los Angeles (LAX) McAllen (MFE) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) New York (TSS) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
Investigating

18 November 2026, 01:50 UTC

18 November 2026, 01:50 UTC

We're investigating possible performance impact affecting the North America data centers.

All other locations and services are unaffected.

Identified

18 November 2026, 03:51 UTC

18 November 2026, 03:51 UTC

Our engineers have identified the contributing factor causing the issue impacting our services in North America.

Mitigation actions are in progress, and we are seeing early signs of improvement. We will post a new update once recovery is confirmed.

All other products and services remain unaffected by this incident.

Monitoring

18 November 2026, 03:57 UTC

18 November 2026, 03:57 UTC

Engineering has deployed a fix and have confirmed a gradual recovery to North America POPs. We will continue to monitor until we’ve confirmed that customer and end user experience has been fully restored.

All other networks and services were unaffected by this incident.

Resolved

18 November 2026, 04:07 UTC

18 November 2026, 04:07 UTC

Engineering has confirmed that North America POPs have been fully restored. Customers may have experienced elevated errors and latency from 1:50 to 3:34 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.


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.

Status Post, Created Date/Time:   2026-11-18 02:57:01 UTC