Fastly outage history

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

Engineering have confirmed a gradual recovery to API & Configuration Management . We will continue to monitor until we’ve confirmed that customer and end user experience has been fully restored.

Our engineers believe they have identified contributing factor causing the issue impacting the API & Configuration Management 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 and latency to our API & Configuration Management All other products and services are unaffected by this incident.

Engineering has confirmed the impact to Object Storage (EU-Central) has been mitigated. Our team will continue to monitor the platform to ensure stability before we resolve this incident.

Our engineers believe they have identified the contributing factor causing the issue impacting Fastly Object Storage. 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 investigating an issue causing intermittent failures when uploading objects to Fastly Object Storage in the EU-Central region. 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.

Fastly is announcing General Availability on September 29, 2026 of Controlled Support Access (CSA). CSA gives customers more control and visibility over Fastly employee access by requiring customer approval for Fastly write/enforcing access. Approved access is time-bound, auditable, and customer-revocable. Read-only troubleshooting remains available so Fastly can continue diagnosing issues efficiently. CSA is default OFF at General Availability (GA). Customers who want to enable CSA can opt in directly from the Fastly Control Panel. What’s Changing? To learn more, see the Controlled support access documentation. The documentation explains standard CSA requests/grants, customer approval and revocation, audit visibility, and Breakglass emergency access. What’s next? What do I have to do? CSA is disabled by default at GA, meaning no action is required unless you wish to use it. Superusers can enable the feature directly within the Fastly Control Panel. 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.

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.

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.

On October 13, 2026, at 00:00 UTC, Fastly will publish additional public IP address ranges to our Public IP List API endpoint. To prepare for future use, we recommend updating your IP prefix lists as soon as possible. The following IP block(s) will be added to our range list: IPv4: 90.98.0.0/17 , 90.98.128.0/18 IPv6: 2a04:4e42::/31 (expanded from 2a04:4e42::/32 ), 2a04:4e44::/32 The deployment of these new prefixes for active use is scheduled for January 11, 2027, at 00:00 UTC, and all currently published IP prefixes will remain unchanged. Customers with any questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated Customer Success team members.

During this incident, customers using logging globally may have experienced delayed or dropped log data, along with elevated errors and increased latency concentrated in our US-West region, from 20:52 to 21:23 UTC and again from 22:16 to 22:29 UTC. The vast majority of logs were delivered successfully throughout this period. For more information about this retrospective stat us post, please reach out to Support through https://support.fastly.com .

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.

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.

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.

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.

Fastly will perform maintenance on the Fastly Support Portal and artificial intelligence (AI) chatbot on September 10, 2026 from 12:00 AM to 4:00 AM UTC (240 minutes). What’s changing? Fastly is updating the infrastructure behind the Fastly Support Portal and AI chatbot by migrating from our ticketing provider's default content delivery network (CDN) to our own in-house Fastly CDN and Fastly Next-Gen WAF (NGWAF) layer. This change improves system resilience and adds protection against automated bot traffic and distributed denial of service (DDoS) threats. What’s next? What do I have to do? Nothing. Fastly is handling every action for this planned maintenance. During the 240-minute window, the AI chatbot and the Fastly Support Portal will be temporarily unavailable. Case submission via [email protected] and all dedicated enterprise Slack channels will remain unaffected and fully operational during this maintenance.

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.

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.

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.