We are investigating elevated errors in Configuration Deployment services. Customers with newly provisioned services and some configuration updates may not deploy to the CDN.

Network availability and all other services are unaffected.

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

Fastly has begun to see recovery in response to our fix. 

Customers will not have to take any action, their deployed configuration updates and newly provisioned services will become available as our fix reaches the impacted hosts.

Network availability and all other services were unaffected by this incident. We will continue to monitor until our fix is fully deployed and all services have been effectively updated.

This incident has been resolved.

We are currently investigating performance issues affecting the availability of manage.fastly.com and our API. CDN delivery, stats aggregation, and all other data plane 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.

We are currently investigating into elevated errors when attempting to access our Control Plane (manage.fastly.com) Configuration Management and API services.

We have observed a reduction in errors since the start of this incident, but are continuing to investigate the cause of the errors observed in order to identify a solution that would prevent a repeat of this incident for our partner and customer services.

The customer impact associated with this status post is a direct result of the third party service provider issue that is covered in this status post link: https://www.fastlystatus.com/incident/376079 

All remaining status post updates will be consolidated into the link provided above. We are effectively closing this post in order to reduce dual notifications for our subscribers.

We’re currently investigating performance issues with our VCL websockets.

All other services are unaffected.

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

This incident has been resolved.

On the 8th of September 2023, Fastly Support and dedicated Technical Account teams received reports of intermittent WebSocket error messages from a subset of Fastly customers. Fastly Engineering identified one of our recent configuration deployments had resulted in the customer experience reported. To limit the impact we immediately identified a workaround, and distributed the instructions to all of our impacted customers.

As of the 15th September 2023 a corrected configuration has been effectively deployed throughout our infrastructure.

Those customers previously impacted by this incident, will be provided with a Fastly Service Advisory (FSA) outlining the details of this incident and the corrective measures that we have taken.

All other customer services and Point of Presence (POP) locations were unaffected by this incident.

We're investigating elevated errors in API & Configuration Management .

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 is resolved. Customers would have experienced elevated errors when attempting to access our Control Plane (manage.fastly.com) and API services during this incident may experience delays or have failed.

A Fastly Service Advisory (FSA) will be made available after a retrospective of this incident.

We're investigating elevated errors in API & Configuration Management .

All other locations and services are unaffected

This issue has been caused by a disruption with a common cloud provider. Customers may experience elevated errors while accessing our Control Plane (manage.fastly.com), managing their service configurations, performing purge-all, and other API services.

A fix has been implemented and we are monitoring the gradual recovery of our Control Plane services (manage.fastly.com). 

Our Control Plane services (manage.fastly.com) have been restored and we are monitoring the results.

This incident has been resolved.

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.

We're currently investigating performance issues with our Historical Stats service.

All other services are unaffected.

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

Fastly Engineering is applying additional mitigation strategies to fix our historical stats API. Customers may continue to experience 5xx errors in their Historical Stats API as we deploy these measures.

Upon further investigation, Fastly Engineering has also identified impact with our Fastly Application that may be affecting customers.  

Customers may experience degraded service with the Historical Stats API and Fastly Application when attempting to collect data.

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.

We are currently investigating performance issues affecting the availability of manage.fastly.com and our API. CDN delivery, stats aggregation, and all other data plane services are unaffected.

We are continuing to investigate performance issues affecting the availability of manage.fastly.com and our API. CDN delivery, stats aggregation, and all other data plane 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.