Incident History for Fastly

Content delivery at Osaka (ITM) and Tokyo (NRT) POPs fully restored after increased errors and latency from 19:19 to 21:36 UTC.

Fix deployed and content delivery recovered at Osaka and Tokyo POPs; error rates and latency nominal, team monitoring before resolving.

Fastly engineers have identified the contributing factor and are developing a fix for degraded content delivery at the Osaka and Tokyo POPs.

Fastly is investigating increased errors and latency affecting content delivery at the Osaka (ITM) and Tokyo (NRT) points of presence.

The Controlled Support Access general availability event has been resolved as of 29 October 2026.

The Queretaro (QRO) rerouted traffic event has been resolved as of 29 October 2026 at 08:54 UTC.

Traffic to the Queretaro POP is being redirected to nearby POPs due to an upstream provider issue, with no customer impact expected.

The Queretaro (QRO) POP incident causing elevated errors and increased latency is resolved.

Scheduled maintenance for Varanasi, Delhi, Ranchi, and Sambalpur has been completed.

Scheduled maintenance for Hong Kong (HKG) data center capacity expansion has been completed.

Scheduled maintenance on Delhi, Ranchi, Sambalpur and Varanasi data centers from 27 October 2026, 20:00-22:00 UTC, with traffic redirected to neighboring POPs.

Scheduled maintenance on Delhi, Ranchi, Sambalpur and Varanasi data centers from 27 October 2026, 20:00-22:00 UTC, with traffic redirected to neighboring POPs.

Scheduled maintenance on Delhi, Ranchi, Sambalpur and Varanasi data centers from 27 October 2026, 20:00-22:00 UTC, with traffic redirected to neighboring POPs.

The scheduled maintenance at the New York (TSS) data center has been completed.

Fastly will perform scheduled maintenance on the New York (TSS) data center, redirecting traffic to neighboring POPs in the region.

Fastly will perform scheduled maintenance on the New York (TSS) data center, redirecting traffic to neighboring POPs in the region.

Fastly will perform scheduled maintenance on the New York (TSS) data center, redirecting traffic to neighboring POPs in the region.

Scheduled maintenance on the Sambalpur and Bhopal data centers has been completed.

Scheduled maintenance on the Sambalpur and Bhopal data centers will redirect traffic to neighboring POPs during the October 10 window.

Scheduled maintenance will redirect traffic to neighboring POPs during the October 10 window.

Scheduled maintenance for Toronto (YYZ) data center capacity expansion has been completed.

Scheduled maintenance for Toronto (YYZ) capacity expansion has been extended to 16 October 2026 at 18:00 UTC.

Scheduled maintenance for Toronto (YYZ) data center capacity expansion has been completed.

The Delhi (QAG) rerouted traffic incident has been resolved as of 15 October 2026 at 21:41 UTC.

Singapore (QPG) POP fully restored; elevated errors resolved after brief impact window.

Engineering confirmed the impact to the Singapore (QPG) POP has been mitigated and the incident is now being monitored.

Fastly is investigating elevated errors affecting its Singapore (QPG) Point of Presence; all other products and services remain unaffected.

The Cape Town (CPT) incident causing elevated errors from 03:12 to 03:57 UTC is resolved.

The Sambalpur (QAK) rerouted traffic event has been resolved; all services are normal.

Traffic in Sambalpur (QAK) has been temporarily rerouted; all other locations and services are unaffected.

Fastly is adding capacity at its Toronto (YYZ) POP, which may cause connection resets during traffic migration.

Scheduled maintenance on the Mexico City (AZP) new data center has been completed.

Fastly is adding a Mexico City (AZP) data center on 7 October 2026, with an estimated duration of 4 hours.

Fastly is adding a Mexico City (AZP) data center on 7 October 2026, with an estimated duration of 4 hours.

Fastly is adding a new Mexico City (AZP) data center on 7 October 2026, with an estimated 4-hour maintenance window.

Object Storage uploads in EU-Central have been fully restored after failures and elevated latency.

Engineers identified the cause of Object Storage upload failures and are developing a fix; no recovery yet.

Fastly is investigating intermittent upload failures to Object Storage in the EU-Central region.