Our engineers are currently investigating a bug affecting a subset of Purge services through our API. The bug is encountered when Purge services are requested using a batch method, when using JSON bodies or surrogate key vectors via Surrogate-Key.

Hash purges and simple surrogate key purges (using Fastly-Surrogate-Key header) are unaffected by this issue.

Our network availability and all other services are unaffected by this incident.

Status Post Update (Mar-8th):

We have retrospectively updated the start date and time to reflect the earliest onset of possible errors - as determined by our post-incident investigations. Customers may have experienced impact to varying degrees and to a shorter duration outline within this status post. 

Our engineers have confirmed the contributing factor for the bug, and are applying a fix for Purging services.

Engineering has deployed a bug fix for our Purging services. Our deployment will be deployed gradually across the fleet, and we will continue to monitor until we’ve confirmed that customer experience has been fully restored.

We do not anticipate any impact to our network availability or other services as a result of this deployment.

Engineering has confirmed that Purging  has been fully restored. Customers may have experienced issues when Purge services are requested using a batch method, when using JSON bodies or surrogate key vectors via Surrogate-Key from the 27th of February 2024 19:50 UTC to the 29th of February 12:55 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

Status Post Updated: 02/29/2024 at 02:39 UTC

Engineers confirmed in retrospective investigations, that the earliest possible onset for this bug was at 19:50 UTC on the 27th of February 2024. 

We're currently investigating performance issues with our URL, Surrogate Key, and Purge All services.

All other 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 URL and Surrogate Key services.

All other 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.

We're currently investigating performance issues with our URL and Surrogate Key purging services. All other services are unaffected.

The 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 URL and Surrogate Key purging services. All other services are unaffected.

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

A fix has been implemented, resulting in improved cloning and purging service performance. However, the service is working through a backlog of requests, and customers may continue to experience further delays. All other services remain unaffected.

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

This incident has been resolved.

We're currently investigating performance issues with our Surrogate Key purging services. All other services are unaffected.

The 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 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 currently investigating performance issues affecting the availability of manage.fastly.com, our API, and service propagation (CDN and Compute@Edge). CDN delivery, stats aggregation, and all other data plane services are unaffected.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

The 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 performance issues affecting the availability of purging. CDN delivery, stats aggregation, and all other data plane services are unaffected.

This incident has been resolved.

On January 5th, 2021 at 21:00 UTC, Fastly will be performing maintenance on the Fastly configuration application and API. During this scheduled maintenance, customers will not be able to access or modify service configurations through the Fastly App, and service API calls will return a 503 status code. Surrogate key and URL-based purging will not be affected, but purge_all will not be available during this maintenance window. Historical stats and WAF rule configuration will also be unavailable. Edge delivery, purging (except purge_all), stats aggregation, and all other content delivery services will be unaffected.

Maintenance will begin as scheduled in 60 minutes.

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

The scheduled maintenance has been completed.

We're currently investigating performance issues with our URL and Surrogate Key purging services. All other services are unaffected.

The 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.