Fastly Outage History

Fastly's Next-Gen WAF service experienced delays in propagating new security rules for 1.3 hours, while existing rules continued to function normally. Engineers identified the contributing factor and deployed a fix, with services gradually restoring though some customers experienced intermittent issues during recovery.

Fastly experienced performance impacts with their Object Storage service in US-East, US-West, and EU-Central regions for 6 hours on May 1st, 2026. Engineering identified multiple contributing factors and deployed fixes with gradual recovery confirmed by 16:50 UTC, followed by full mitigation at 22:16 UTC. All other Fastly locations and services remained unaffected throughout the incident.

Fastly experienced performance issues affecting their API services for 3.4 hours, impacting the Fastly Application, API & Configuration Management, and API Services components. CDN delivery, stats aggregation, and other data plane services remained unaffected throughout the incident. Engineering identified the contributing factor, developed a fix, and successfully mitigated the API performance impact.

Fastly experienced performance issues affecting KV Store and Object Storage services in the Asia Pacific (APAC) and South Asia regions for 17.2 hours. The incident impacted Object Storage, Fastly Compute, and KV Store components in these specific geographic areas while all other locations and services remained unaffected. Engineering successfully mitigated the performance impact and restored normal service operations.

Fastly experienced elevated errors affecting Dashboard Data in their Next Generation Web Application Firewall (NGWAF) Dashboard, along with impacts to the Security Console & API. The incident lasted 49 minutes while engineers identified the contributing factor and implemented a fix. All other Fastly products and services remained unaffected during this minor incident.

Fastly experienced elevated errors that prevented users from logging into the Fastly Application user interface and sub-services, affecting API & Configuration Management, API Services, Configuration Management Services, and the main Fastly Application. Engineering identified the contributing factor and implemented a mitigation strategy, with gradual recovery observed and the impact fully resolved after 2.3 hours. All other Fastly products and network/security services remained unaffected throughout the incident.

Fastly experienced elevated errors at their Ashburn (IAD) point of presence, affecting services in the North America region. The incident lasted 2.1 hours and was classified as minor, with all other Fastly products and services remaining unaffected. Engineering successfully mitigated the impact to the Ashburn PoP.

Fastly experienced elevated errors across all Points of Presence (POPs) in India for 1.6 hours, affecting major cities including Mumbai, Delhi, Bangalore, Chennai, Kolkata, Hyderabad, and dozens of other locations. Engineers identified the contributing factor and developed a fix to mitigate the issue. The incident was resolved with continued monitoring, while all other Fastly products and services remained unaffected.

Fastly experienced elevated errors with their Image Optimization service affecting traffic shielding at Points of Presence in the west North American region, with Web Delivery also impacted. Engineering identified the contributing factor and developed a fix, with the impact mitigated after 1.2 hours. All other Fastly products and services remained unaffected during the incident.

Fastly experienced elevated errors across multiple Points of Presence (POPs) globally, affecting CDN performance in regions including India, Europe, Asia-Pacific, North America, and South America for 1.4 hours. Engineering identified the contributing factor and developed a fix to mitigate the impact. The incident was resolved after engineers implemented the fix and confirmed recovery across all affected POPs.