We’re investigating elevated errors and issues affecting timely propagation of Compute@Edge KV Store writes.

All other locations and services are unaffected.

This issue has been identified and a fix is being implemented. 

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Fastly will be performing maintenance on Log Tailing for Compute@Edge from the 8th of August 2023 at 01:00 to 01:15 UTC.

• Expected duration, 15 minutes

During this time, the ability to tail Compute@Edge services, via the UI and CLI, may be unavailable.

All other Real Time Logging and other services will be unaffected.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The scheduled maintenance has been completed.

Fastly Engineers detected a performance impacting event affecting the Compute@Edge services in IAD data center.

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

We're investigating issues affecting purging for Compute@Edge services.

This issue has been identified and a fix is being implemented. 

Engineering has applied a fix to Compute@Edge Purging. After further investigation we are deploying additional mitigation strategy.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We're investigating issues affecting timely propagation of Compute@Edge KV Store writes.

All other locations and services are unaffected.

This issue has been identified and a fix is being implemented. 

Engineering has applied a fix to KV Store Writes in Compute@Edge. After further investigation we are deploying additional mitigation strategy.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We're investigating elevated errors in Compute@Edge services in our London (LCY), Dublin (DUB), Ashland (IAD), Seattle (BFI) and Columbus (CMH) Points of Presence (POPs).

All other locations and services are unaffected

This issue has been identified and a fix is being implemented. 

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Fastly Engineers detected a performance impacting event affecting some data centers.

During this time, customers may have experienced 502 Bad Gateway errors.

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

This incident has been resolved.

We are currently investigating performance issues affecting the VCL configuration and Compute@Edge module updates. CDN delivery, stats aggregation, and all other data plane services are unaffected.

This issue has been identified and a fix is being implemented. 

Fastly engineers have detected performance issues with VCL configuration propagation from 16:20 - 16:26 UTC and 17:44 - 17:55 UTC. During these time frames, customers may have experienced an increase in 5xx errors for API requests and slow VCL propagation. All other services were unaffected. 

This incident has been resolved.

We’re currently investigating performance issues with Compute@Edge configuration propagation. All other services are unaffected.

This issue has been identified and a fix is being implemented. 

Our investigations have identified common network provider issues related to the performance impact for our Compute@Edge services and NGWAF@Edge updates and decision making. Existing rules are operational, but new data is parsed at a slower pace. Fastly Engineering is in the process of performing standard traffic engineering to restore Compute@Edge and NGWAF@Edge services to pre-incident levels. 

A fix has been implemented and we are monitoring the results.

Fastly has performed traffic engineering to route around the global network provider currently experiencing impact. Our Compute@Edge and NGWAF@Edge services are performing at pre-incident levels. 

This incident is resolved.