Web Delivery
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 have received reports of inaccurate or incomplete Geolocation Data from our customers. A fix has been identified and is being deployed to restore this service.
This fix is being deployed gradually throughout our fleet at a high priority, but our customers may continue to observe varying degrees of inaccurate or incomplete Geolocation data until this issue is resolved.
We will update and close this status post once the deploy is complete and the service has been confirmed by our engineers as having been fully restored.
Our network delivery and all other services remain unaffected by this issue.
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.