Fastly Outage History

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

We are investigating an issue caused by a third-party service provider, which is affecting availability of the Support Portal, including the ability to view or create support tickets. Our engineers are actively monitoring the situation and working with the provider to diagnose and resolve the issue. We will provide another update as more information becomes available or within the next hour.

Our engineers are continuing to investigate the issue impacting the Support Portal, including the ability to view or create support tickets. This has been caused by a third-party service provider outage. We have not yet confirmed the contributing factor has been fully resolved. We'll provide another update as soon as we have more information.

A fix has been validated by our third-party service provider and is currently being rolled out across all impacted systems. 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.

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.

Fastly Engineers detected a performance impacting event affecting the Johannesburg (JNB) 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 our Real-time Log Streaming and Log Explorer & Insights data. 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 for traffic routed through our Los Angeles (BUR), Los Angeles (LAX), Los Angeles (HHR) data centers. 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 restored service performance. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

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.

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.

Fastly is updating how a subset of client disconnects are reported for Delivery (Varnish) Services. Previously, these disconnects returned a 503 (Service Unavailable) response code. As part of a fix for an issue affecting our ERROR-WAIT handling, we changed this behavior so a subset of these disconnects now return a 499 (Client Closed Request) and will have an ERROR-DISCONNECT state. This change will be rolling out gradually over the next few weeks. What you may notice: You may see an increase in 499 response codes and a corresponding decrease in 503 response codes for waitlist disconnects in your logs and dashboards. This is expected and does not indicate a new issue with your service. What you need to do: If you have monitoring, alerting, or automation that treats 503s and 499s differently, review your configuration to confirm it accounts for this change. If you have questions, contact your Fastly support team.

We recently identified an issue affecting the plan usage page for all customers. This is related to the Month to Date API Services Maintenance announced on August 20, 2026. Due to that planned downtime in a downstream system, we did not save daily usage receipts that power the plan usage page visualizations. As a result, the page shows zero usage for August 21 through August 25. This does not affect your bill in any way. The only impact is a temporary loss of visibility into usage for those five days, and unfortunately, we are not able to recover the daily historical data required to visualize the usage. Customers with any questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated account management team members.

We are investigating an issue affecting network connectivity in our McAllen (MFE) point of presence. Our engineers are actively working to diagnose and mitigate the contributing factor. As a precaution, traffic in McAllen (MFE) has been temporarily rerouted. All other locations and services are unaffected.

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

We are investigating an issue causing Next-Gen Waf (NGWAF) dashboard to display blank or missing performance data for some customers. This is a visible issue only - NGWAF protection and services are no impacted. Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the hour All other products and services are unaffected by this incident

Between 14:00 UTC and 19:30 UTC on August 24, 2026, the "Forgot your password" functionality on manage.fastly.com was temporarily unavailable for all Fastly account users while our team performed maintenance. During this window, customers attempting to reset their password via the Fastly Control Panel may have been unable to complete the request. No other account functionality was affected. Our engineering team completed the maintenance and confirmed the password reset flow was fully restored as of 19:30 UTC. No further action is needed from customers. We apologize for any inconvenience this may have caused.

We are investigating an issue causing Next-Gen WAF (NGWAF) dashboard to display blank or missing performance data for some customers. This is a visible issue only - NGWAF protection and services are no impacted. Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the hour All other products and services are unaffected by this incident

Our engineers believe we have identified contributing factor causing missing dashboard data in NGWAF. NGWAF protection and service are not impacted — this affects dashboard visibility only. All other products and services are unaffected by this incident.

Between 01:06 UTC and 01:51 UTC on August 23, 2026, Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT), Chicago (CHI), Columbus (CMH), Los Angeles (BUR), Phoenix (PHX), Toronto (YYZ), Los Angeles (LAX), Los Angeles (HHR) Points of Presence (POPs). During this time, customers with traffic routed through these locations may have experienced elevated error rates or latency. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

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

We have identified the cause of elevated latency affecting a subset of edge POPs served by our Chicago (CHI) shield. Engineers are actively working on a mitigation. We understand how critical this service is to your operations and apologize for the disruption. All other products and services are unaffected by this incident.

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

Between approximately 16:59 and 17:12 UTC on August 20, 2026, some customers experienced difficulty accessing the manage.fastly.com dashboard, including blank pages and login issues. This incident did not impact API endpoints on api.fastly.com. This issue has been fully resolved and all customers should now have normal access to manage.fastly.com. We apologize for any disruption this may have caused. Our engineering team has identified the contributing factor and is implementing measures to prevent recurrence.

Our engineers have identified a contributing factor causing reduced cache-hit performance for a subset of cache infrastructure serving Compute customers. Affected customers may see temporarily elevated origin load. A fix is being deployed to the affected nodes. Due to the scope of the change, full deployment will take some time. We will post updates as the rollout progresses. All other products and services remain unaffected by this incident.

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

We are investigating a small number of requests receiving an empty response body where content is expected. Impact is limited to requests that use Streaming Miss and are eligible for HTTP response revalidation. All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the Content Delivery (CDN) 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.

Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to our Content Delivery (CDN) service. All other locations and services are unaffected.