Fastly Outage History

We are investigating an issue causing elevated 503 errors and slowness affecting api.fastly.com and manage.fastly.com. Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available.

We are investigating an issue causing connection failures and elevated errors for some customers connecting through our Santa Clara (RHV) Point of Presence (POP). We have rerouted traffic away from this location while our engineers work on mitigation. Customers may experience slightly elevated latency while traffic is served from neighboring POPs. 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.

Traffic remains rerouted away from our Santa Clara (RHV) Point of Presence (POP) while our engineers continue to work on mitigation. Customers may experience slightly elevated latency while traffic is served from neighboring POPs. This POP will remain offline until further notice. We will provide another update once traffic has been restored to this location. All other products and services are unaffected by this incident.

Fastly Engineers detected a performance impacting event affecting our API & Configuration Management. All data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Traffic in St. Louis (STL) has been temporarily rerouted. All other locations and services are unaffected.

Traffic in Srinagar-Nahota (QBG) has been temporarily rerouted. All other locations and services are unaffected.

We're currently investigating performance issues with our Image Optimization service in Europe. All other services are unaffected.

Our engineers believe they have identified the contributing factor causing the issue impacting our Image Optimizer service. 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 confirmed the impact to Image Optimization service has been mitigated.

Between 00:32 and 00:44 UTC on July 16, 2026, we experienced an issue with our Historical Stats API and Origin Inspector API. During this time, customers may have experienced failed requests to the Historical Stats API and Origin Inspector API, errors when loading observability dashboards, and alerts that evaluate these metrics may have been delayed or may not have triggered. The issue has been resolved, and all services are operating normally.

We are investigating an issue causing elevated latency (high Time To First Byte (TTFB)) for our Singapore (SIN) Point of Presence (POP). Our engineers have taken steps to reduce the impact and are observing improvement while they continue to investigate 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 contributing factor causing the issue impacting the Singapore (SIN) status page component. 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.

Traffic in Kolkata (CCU) has been temporarily rerouted. All other locations and services are unaffected.

We are investigating reports of intermittent latency and errors impacting customers served through the Kolkata (CCU) Point of Presence. Traffic has been rerouted to nearby regions while our engineers investigate. Customers may experience intermittent impact during this time as traffic stabilizes on alternate paths. Our ability to deliver network services on all other locations, and our ability to security services are not affected by this incident. We will provide another update as more information becomes available.

Our engineers believe they have identified contributing factor causing the issue impacting the Kolkata (CCU) status page component. 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.

We are investigating elevated errors with Compute at our Palo Alto (PAO) Point of Presence (POP). All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting our Palo Alto (PAO) POP. 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.

Between 13:00 UTC and 19:12 UTC on June 25, 2026, customers routing traffic through our London City (LCY) and London Heathrow (LHR) Points of Presence (POPs) may have experienced elevated Time to First Byte (TTFB), request timeouts, and HTTP 503 errors. Customers using LHR as a shield origin — including those routing through LCY — were most affected. The highest concentration of errors occurred between approximately 16:00 and 16:40 UTC. Service degradation began to improve at approximately 16:40 UTC and was fully resolved by 19:12 UTC. Customer impact: Customers in the affected traffic paths may have observed increased latency, elevated error rates, and in some cases failed requests during this window. Current status: This incident is fully resolved. All services at LCY and LHR are operating normally. If you have questions about how this incident affected your services, please contact our support team by emailing us at [email protected].

Fastly Engineers detected a performance impacting event affecting our API Services. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Traffic in Mumbai (QAI) has been temporarily rerouted. All other locations and services are unaffected.

We're investigating possible performance impact affecting the Buenos Aires (EZE) data center. All other locations and services are unaffected.

Our engineers believe they have identified contributing factor causing the issue impacting the Buenos Aires (EZE) status page component. 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.

Fastly Engineers detected a performance impacting event affecting the Santiago (SCL) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

We're currently investigating an issue with our Next-Gen WAF (NGWAF) service that is causing audit log events to not appear in the logs. This does not affect functionality of NGWAF services. All other services are unaffected.

Our engineers believe they have identified contributing factor causing the issue impacting the Next-Gen WAF (NGWAF) status page component. 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.

Fastly Engineers detected a performance impacting event affecting the Lima (LIM) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Fastly Engineers detected a performance impacting event affecting the availability of manage.fastly.com and API. CDN delivery, stats aggregation, and all other data plane services were unaffected. The issue has been resolved and we are monitoring performance closely.

We are investigating elevated errors with product enablements in our Fastly Application. All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the Fastly Application status page component. 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.

Traffic in London (QQP) has been temporarily rerouted. All other locations and services are unaffected.

Our engineers have been informed that our Customer Relationship Management (CRM) provider is currently experiencing an incident. As a result, you may experience slightly delayed responses from our Support team while we implement an internal workaround and monitor this provider's incident updates. All other Fastly services remain fully operational. Our network and security products continue to deliver without disruption. We will provide an update if the situation changes.

We have an update regarding the ongoing Informational affecting Support Ticketing System. Our provider has reported that a contributing factor has been identified and they are working on a fix. As a reminder, Fastly's core edge network and security services remain unaffected. Please continue to email [email protected] for any assistance while our standard support and CRM channels remain impacted. Updated on 18 June 2026 at 18:49 UTC

We are investigating elevated errors to our Bogota (BOG) Point of Presence (POP). All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the Bogota (BOG) status page component. 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.

We are investigating elevated errors to our Lima (LIM) Point of Presence (POP). All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the Lima (LIM) status page component. 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.

Traffic in Hong Kong (HKG) has been temporarily rerouted. All other locations and services are unaffected.

Fastly Engineers detected a performance impacting event affecting the Hong Kong (HKG) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.