Purging
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.
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.
Engineering has confirmed the impact to Purging functionality within our Hong Kong (HKG), Tokyo (NRT), Tokyo (TYO) POPs has been mitigated.
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.
We are investigating elevated errors to our Purging service.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to our Purging service.
All other locations and services are unaffected.
Engineering has confirmed the impact to Purging service has been mitigated.
All other locations and services are unaffected.
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.
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.
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.
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 and we are monitoring the results.
This incident has been resolved.