Purging

Network Services Web Delivery Purging
 
15 November 2024, 01:00 UTC

We are investigating elevated errors to Purging functionality within our Hong Kong (HKG), Tokyo (NRT), Tokyo (TYO) Points of Presence (POPs).

All other products and services are unaffected by this incident.


 
15 November 2024, 03:56 UTC

Our engineers have identified the contributing factor and are applying a fix to Purging functionality within our Hong Kong (HKG), Tokyo (NRT), Tokyo (TYO) POPs.

All other locations and services are unaffected.

 
15 November 2024, 04:11 UTC

Engineering has confirmed the impact to Purging functionality within our Hong Kong (HKG), Tokyo (NRT), Tokyo (TYO) POPs has been mitigated.

 
15 November 2024, 04:25 UTC

Engineering has confirmed that Purging functionality within our Hong Kong (HKG), Tokyo (NRT), Tokyo (TYO) POPs has been fully restored. Customers may have experienced elevated errors when purging from 01:00 UTC to 04:13 UTC.

This incident is resolved.

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

To offer feedback on our status page, click "Give Feedback

Status Post, Created Date/Time: 2024-11-15 03:52:11 UTC 



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.


05 October 2024, 11:32 UTC
Network Services Web Delivery Purging
 
05 October 2024, 11:32 UTC

We are investigating elevated errors to our Purging service.

All other products and services are unaffected by this incident.


 
05 October 2024, 12:18 UTC

Our engineers have identified the contributing factor and are applying a fix to our Purging service.

All other locations and services are unaffected.

 
05 October 2024, 12:41 UTC

Engineering has confirmed the impact to Purging service has been mitigated.

All other locations and services are unaffected.

 
05 October 2024, 13:15 UTC

Engineering has deployed a fix and have confirmed a gradual recovery to Purging service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

All other products and services were unaffected by this incident.


 
05 October 2024, 13:54 UTC

Engineering has confirmed that Purging service has been fully restored. Customers may have experienced elevated errors when purging or may have observed stale content served after a successful purge from 11:32 to 13:45 UTC.

This incident is resolved.

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

To offer feedback on our status page, click "Give Feedback

Status Post, Created Date/Time: 2024-10-05 12:15:17 UTC 



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.


Compute Purging
 
27 February 2024, 19:50 UTC

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. 

 
28 February 2024, 23:40 UTC

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


 
29 February 2024, 00:55 UTC

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.



 
29 February 2024, 14:04 UTC

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. 

07 February 2023, 23:09 UTC
Compute Purging
 
07 February 2023, 23:09 UTC

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

All other services are unaffected.

 
07 February 2023, 23:58 UTC

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

 
08 February 2023, 00:14 UTC

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

 
08 February 2023, 00:59 UTC

This incident has been resolved.

11 January 2023, 19:42 UTC
Network Services Web Delivery Purging
 
11 January 2023, 19:42 UTC

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

All other services are unaffected.

 
11 January 2023, 19:46 UTC

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

 
11 January 2023, 21:55 UTC

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

 
11 January 2023, 22:09 UTC

This incident has been resolved.

09 November 2022, 23:49 UTC
Platform Compute North America Europe Amsterdam (AMS) Purging Ashburn (IAD) Boston (BOS)
 
09 November 2022, 23:49 UTC

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

 
10 November 2022, 00:11 UTC

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

 
10 November 2022, 00:25 UTC

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

 
10 November 2022, 00:35 UTC

This incident has been resolved.

03 June 2022, 15:59 UTC
Purging
 
03 June 2022, 15:59 UTC
We're currently investigating performance issues with our URL and Surrogate Key purging services. All other services are unaffected.
 
03 June 2022, 17:35 UTC
The issue has been identified and a fix is being implemented.
 
03 June 2022, 18:38 UTC
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.
 
03 June 2022, 19:13 UTC
A fix has been implemented and we are monitoring the results.
 
03 June 2022, 19:25 UTC
This incident has been resolved.
15 April 2022, 17:06 UTC
Purging
 
15 April 2022, 17:06 UTC
We're currently investigating performance issues with our Surrogate Key purging services. All other services are unaffected.
 
15 April 2022, 17:39 UTC
The issue has been identified and a fix is being implemented.
 
15 April 2022, 18:25 UTC
A fix has been implemented and we are monitoring the results.
 
15 April 2022, 18:40 UTC
This incident has been resolved.
Fastly Application Purging API Services
 
08 December 2021, 18:24 UTC
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.
 
08 December 2021, 18:34 UTC
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.
 
08 December 2021, 18:56 UTC
We are continuing to investigate this issue.
 
08 December 2021, 18:58 UTC
We are continuing to investigate this issue.
 
08 December 2021, 19:13 UTC
The issue has been identified and a fix is being implemented.
 
08 December 2021, 19:15 UTC
A fix has been implemented and we are monitoring the results.
 
08 December 2021, 19:25 UTC
This incident has been resolved.
16 November 2021, 23:56 UTC
Purging
 
16 November 2021, 23:56 UTC
We are currently investigating performance issues affecting the availability of purging. CDN delivery, stats aggregation, and all other data plane services are unaffected.
 
17 November 2021, 01:05 UTC
This incident has been resolved.