Fastly outage history and live incidents

Our engineers have confirmed that our content delivery service in the ITM and NRT POPs has been fully restored.

Customers may have experienced increased errors and latency from 19:19 to 21:36 UTC. Service has been fully restored.

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.

This event has been resolved.

This event has been resolved.

During this incident, customers may have experienced elevated errors and increased latency for requests served through our Queretaro (QRO) POP from 23:21 to 03:29 UTC.

This incident is resolved.

For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.

This event has been resolved.

Engineering has confirmed that Compute, Next-Gen WAF (NGWAF) Services has been fully restored. Customers may have experienced intermittent 5xx errors from 23:05 UTC on October 27 to 00:23 UTC on October 28. Service has been fully restored.

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.

Our engineers have confirmed that our network services in the Johannesburg (JNB) Point of Presence (POP) have been fully restored.

Customers may have experienced errors and increased latency from 13:55 to 17:31 UTC on October 27, 2026. Customers in the Cape Town (CPT) POP were temporarily impacted between 14:35 and 14:54 UTC. Service has been fully restored.

Affected customers may have experienced impact to varying degrees and for a shorter duration than stated 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.

Our engineers have taken steps to recover the affected systems in the Johannesburg (JNB) Point of Presence (POP) and are gradually returning traffic to the site.

Customers in the Cape Town (CPT) POP were temporarily impacted between 14:35 and 14:54 UTC. Services in CPT have since fully recovered.

Our team is actively monitoring the recovery and will post another update once services are fully restored.