Is Fastly down?

Between 10:02 UTC and 10:45 UTC on September 10, 2026, we experienced an issue with our delivery service at our Chicago (CHI) Point of Presence (POP). During this time, customers may have experienced intermittent 502 errors on requests routed through this POP. The issue has been resolved, and all services are operating normally.

This incident has been resolved.

We are investigating an issue causing elevated 5xx errors for some customers using our Compute services. Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the next hour. All other products and services are unaffected by this incident.

Our engineers believe they have identified the contributing factor causing the issue impacting our Compute services. Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.

Engineering has deployed a fix and have confirmed a gradual recovery to Compute services. We will continue to monitor until we’ve confirmed that customer experience has been fully restored. All other products and services remain unaffected by this incident.

Engineering has confirmed that Compute services has been fully restored. Customers may have experienced elevated 5xx errors from 18:28 to 21:52 UTC. This incident is resolved. 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-09-09 19:15:48 UTC

We are investigating an issue causing elevated 431 errors on requests for our customers. We will provide another update as more information becomes available or within the next hour.

Our engineers have identified the contributing factor causing the issue impacting our CDN service. Our engineers are now deploying a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.

A fix is being deployed for the issue impacting our CDN service. We are observing a gradual restoration of services, though some customers may continue to experience intermittent issues as the system stabilizes. Our team is actively monitoring the recovery and will post another update once services are fully restored.

A fix has been deployed for the issue impacting our Next-Gen WAF services running on Compute. We are observing a gradual restoration of services, though some customers may continue to experience intermittent issues as the system stabilizes. To clarify an earlier update: this issue affected Next-Gen WAF on Compute, not our CDN service, which was not impacted. Our team is actively monitoring the recovery and will post another update once services are fully restored.

Engineering has confirmed that our Compute services and NGWAF services that run on Compute have been fully restored. Customers may have experienced elevated 431 errors from September 9, at 11:40 UTC to September 11, at 20:00 UTC. This incident is resolved. 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-09-11 15:22:36 UTC

Between 17:49 and 18:45 UTC, we experienced an issue with our Fastly API service configuration endpoints. During this time, customers may have experienced elevated errors on service configuration API endpoints (VCL dictionary/ACL updates, version activations, and /service/:id/lint). The issue has been resolved, and all services are operating normally.

This incident has been resolved.

We're investigating possible performance impact affecting the Los Angeles (LAX), Los Angeles (HHR) Points of Presence (POPs). All other locations and services are unaffected.

Customers may also see possible degradation in our Los Angeles (BUR) POP.

Our engineers believe they have identified the contributing factor causing the issue impacting origin pull and shielding performance for customers with traffic routed through the affected region. Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.

We are currently monitoring a network issue caused by a third-party network provider serving the Los Angeles region. This is a third-party network event, not an issue with Fastly's platform. Our engineers have taken action to route traffic away from the affected paths and are coordinating directly with the third-party provider as they work to restore full service. For additional information about this network event, please see: https://ecogent.cogentco.com/network-status Customers with traffic paths through the affected region may see intermittent delays or errors for origin pull or shielding traffic. All other products and services are unaffected. Workaround & next steps: No action is needed on your part. We will share another update here as the third-party provider makes progress, or within the hour.

Our engineering teams have deployed traffic engineering changes that are successfully mitigating the network congestion affecting origin pull and shielding traffic in the Los Angeles region. Error rates and latency have returned to nominal levels for the majority of affected traffic. We continue to work closely with our third-party network provider while they resolve the underlying issue. Our team will continue to monitor the platform closely to ensure continued stability before we resolve this incident.

The fix has been successfully deployed, and we have observed a recovery of network performance for affected traffic paths. Error rates and latency have returned to nominal levels. Our team will continue to monitor the platform to ensure stability before we resolve this incident.

Engineering has confirmed that network performance for traffic routed through the Los Angeles (LAX), Los Angeles (HHR) and Los Angeles (BUR) POP's has been fully restored. Customers may have experienced intermittent delays or errors on origin pull and shielding traffic from September 2, 2026, 13:43 UTC to September 3, 2026, 09:11 UTC. This incident is resolved. 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-09-02 16:09:33 UTC