GraphCDN experienced a major incident on August 20, 2025 affecting GraphQL Edge Caching and GraphQL Metrics and 1 more component, lasting 1h 14m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 20, 2025, 09:35 PM UTC
We are currently investigating this issue.
- investigating Aug 20, 2025, 09:36 PM UTC
We are continuing to investigate this issue.
- investigating Aug 20, 2025, 09:57 PM UTC
Noticing elevated error rates across our KV stores.
- monitoring Aug 20, 2025, 10:42 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 20, 2025, 10:43 PM UTC
Related https://www.fastlystatus.com/incident/377843
- resolved Aug 20, 2025, 10:50 PM UTC
This incident has been resolved.
- postmortem Aug 21, 2025, 04:32 PM UTC
## Summary On August 20, 2025, our services experienced elevated errors on our KV stores due to a third-party vendor issue. The incident was caused by a faulty enhancement deployment on the vendor's platform, which was subsequently rolled back to restore service. ## Root Cause Third-party vendor deployed a faulty enhancement that caused backend errors for a subset of customers, primarily in Singapore and California regions. ## Resolution Vendor engineering team rolled back the problematic deployment and confirmed service restoration. ## Lessons Learned * Vendor responded quickly with clear communication * Need better early detection of vendor-side issues * Consider additional monitoring for vendor dependencies Related: [https://www.fastlystatus.com/incident/377843](https://www.fastlystatus.com/incident/377843).