Resilimap

Multi-cloud reliability monitoring

Site generated: 2026-06-05 20:04:21 UTC 6/5/2026, 8:04:21 PM local
Back to all providers

Fastly

Last updated: 6/5/2026, 3:03:11 PM

⚠ 18 Active Incidents
Active Incidents
18
Resolved
22
Scheduled Maint.
0
Total Incidents
40
Total Maint.
3
Critical
0

Active Incidents

Traffic in Houston (IAH) has been temporarily rerouted.

All other locations and services are unaffected.

Started: 6/4/2026, 8:00:00 AM Updated: 6/4/2026, 8:00:00 AM Duration: 36h 5m

Fastly will be adding capacity at our Chicago (CHI) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 04 June 2026 at 05:00 UTC.

Our estimated duration is 4h. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team at https://support.fastly.com.

Started: 6/4/2026, 5:00:00 AM Updated: 6/4/2026, 5:00:00 AM Duration: 39h 5m

Traffic in Fortaleza (FOR) has been temporarily rerouted.

All other locations and services are unaffected.

Started: 6/2/2026, 3:03:00 PM Updated: 6/2/2026, 3:03:00 PM Duration: 77h 2m

As part of Fastly’s global network expansion, we will be adding Dusseldorf (DUS) data center to Fastly's Europe network. 

Traffic served by our  Dusseldorf (DUS)  data center will be aggregated into our Europe region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to  Dusseldorf (DUS) . As such, some customers may see a change in their bills.

Fastly’s standard billing rates are located at https://www.fastly.com/pricing.

Started: 5/29/2026, 12:00:00 AM Updated: 5/29/2026, 12:00:00 AM Duration: 188h 5m

We are investigating elevated errors to our Fortaleza (FOR) Point of Presence (POP).

All other products and services are unaffected by this incident.

Started: 5/28/2026, 1:38:00 AM Updated: 5/28/2026, 1:38:00 AM Duration: 210h 27m

Fastly will be adding capacity at our London (LHR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 26 May 2026 at 00:30 UTC.

Our estimated duration is 4h. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team at https://support.fastly.com.

Started: 5/26/2026, 12:30:00 AM Updated: 5/26/2026, 12:30:00 AM Duration: 259h 35m

Our engineers believe they have identified contributing factor causing the issue impacting the Image Optimization 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.

Started: 5/22/2026, 10:20:00 AM Updated: 5/22/2026, 10:20:00 AM Duration: 345h 45m

We're currently investigating performance issues with our Image Optimization service in Europe.

All other services are unaffected.

Started: 5/22/2026, 6:50:00 AM Updated: 5/22/2026, 6:50:00 AM Duration: 349h 15m

Fastly Engineers detected a performance impacting event affecting the Ashburn (IAD) data center.

Started: 5/21/2026, 9:29:00 PM Updated: 5/21/2026, 9:29:00 PM Duration: 358h 36m

Our engineers believe they have identified contributing factor causing the issue impacting the  API Services 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.

Started: 5/20/2026, 8:02:00 PM Updated: 5/20/2026, 8:02:00 PM Duration: 384h 3m

We are investigating an issue causing errors and timeouts for customers using the Fastly API (api.fastly.com).

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.

Started: 5/20/2026, 6:35:00 PM Updated: 5/20/2026, 6:35:00 PM Duration: 385h 30m

Update: The responding escalation manager erroneously marked the incorrect status page component in their original post which caused the wrong title to appear within customer support chat and email threads. This was corrected to display the proper component (Ambala (QAA)). 

All other components, locations and services were unaffected by this event. 

Started: 5/17/2026, 2:59:00 AM Updated: 5/17/2026, 2:59:00 AM Duration: 473h 6m

Traffic in Ambala (QAA) has been temporarily rerouted.

All other locations and services are unaffected.

Started: 5/17/2026, 1:27:00 AM Updated: 5/17/2026, 1:27:00 AM Duration: 474h 38m

Our engineers believe they have identified contributing factor causing the issue impacting the TLS Provisioning features via API and Web application.

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

Started: 5/13/2026, 7:01:00 AM Updated: 5/13/2026, 7:01:00 AM Duration: 565h 4m

We are investigating elevated errors to our TLS Provisioning feature.

Started: 5/13/2026, 6:06:00 AM Updated: 5/13/2026, 6:06:00 AM Duration: 565h 59m

Traffic in New York (TSS) has been temporarily rerouted.

All other locations and services are unaffected.

Started: 5/6/2026, 6:38:00 PM Updated: 5/6/2026, 6:38:00 PM Duration: 721h 27m

Our engineers believe they have identified contributing factor causing the issue impacting the Next-Gen WAF (NGWAF) rule propagation.

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.

Started: 5/6/2026, 5:38:00 AM Updated: 5/6/2026, 5:38:00 AM Duration: 734h 27m

Next-Gen WAF (NGWAF) services are currently experiencing a delay in new rule propagation. Existing rules and functionality are unaffected.

Started: 5/6/2026, 4:42:00 AM Updated: 5/6/2026, 4:42:00 AM Duration: 735h 23m

Recently Resolved Incidents

This incident has been resolved.


AI Analysis
Impact: major
Categories: network, cdn
Users: specific-region
Root Cause: Root cause not yet disclosed
Started: 6/5/2026, 12:52:00 PM Resolved: N/A Duration: 7h 13m

Fastly Engineers detected a performance impacting event affecting the Singapore (SIN) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

AI Analysis
Impact: major
Categories: network, cdn
Users: specific-region
Root Cause: Performance impacting event affecting the Singapore (SIN) data center
Started: 6/5/2026, 12:00:00 PM Resolved: N/A Duration: 8h 5m

This event has been resolved.



Started: 6/4/2026, 9:25:00 AM Resolved: N/A Duration: 34h 40m

This event has been resolved.



Started: 6/2/2026, 4:36:00 PM Resolved: N/A Duration: 75h 29m

This event has been resolved.



Started: 5/28/2026, 2:29:00 AM Resolved: N/A Duration: 209h 36m

This incident has been resolved. Image Optimization services in Europe are fully restored and operating normally.

Customers may have experienced intermittent errors and elevated latency between 06:50 UTC and 10:02 UTC on May 22, 2026.

We apologize for any disruption this may have caused and thank you for your patience.




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-05-22 09:55:16 UTC  

Started: 5/22/2026, 12:10:00 PM Resolved: N/A Duration: 343h 55m

Engineering has confirmed the impact to Image Optimization service has been mitigated.

Started: 5/22/2026, 10:24:00 AM Resolved: N/A Duration: 345h 41m

The issue causing temporary unhealthy cache nodes was resolved, and services were fully restored.

Our engineers confirmed that all cache nodes returned to a healthy state. Customers may have experienced impact between 21:29 UTC and 21:35 UTC (approximately 6 minutes).

All other services and locations were unaffected by this event.

Started: 5/21/2026, 9:35:00 PM Resolved: N/A Duration: 358h 30m

Our engineers have confirmed that the Fastly API (api.fastly.com) has been fully restored. Customers may have experienced elevated 503 errors, increased timeouts, or failures on API calls and Terraform builds from approximately 18:35 to 19:37 UTC.

As a side effect of the API degradation, the following areas were also impacted during this period:

  • Next-Gen WAF (NGWAF) rule and configuration updates may have been delayed in taking effect
  • Fastly account sign-up may have experienced disruptions
  • Fastly Support Portal functionality may have been affected

Service has been fully restored. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

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-05-20 19:31:03 UTC    

Started: 5/20/2026, 8:19:00 PM Resolved: N/A Duration: 383h 46m

Engineering has confirmed the impact to API Services has been mitigated.

Started: 5/20/2026, 8:18:00 PM Resolved: N/A Duration: 383h 47m

Showing 10 of 22 resolved incidents

Scheduled Maintenance

This scheduled maintenance has been completed.
Started: 6/4/2026, 9:00:00 AM Completed: N/A Duration: 35h 5m

The scheduled maintenance has been completed.


Started: 5/29/2026, 5:00:00 AM Completed: N/A Duration: 183h 5m

The scheduled maintenance has been completed.


Started: 5/26/2026, 4:30:00 AM Completed: N/A Duration: 255h 35m