GraphCDN Outage History

GraphCDN is up right now

GraphCDN had 1 outage in the last 2 years totaling 1h 14m of downtime — averaging 0 incidents per month.

There was 1 GraphCDN outage since August 20, 2025 totaling 1h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://swl3fmh6tryh.statuspage.io

Major August 20, 2025

Domain resolution

Detected by Pingoru
Aug 20, 2025, 09:35 PM UTC
Resolved
Aug 20, 2025, 10:50 PM UTC
Duration
1h 14m
Affected: GraphQL Edge CachingGraphQL MetricsGraphQL Rate LimitingGraphQL Developer PortalsUser APIAdmin API
Timeline · 7 updates
  1. investigating Aug 20, 2025, 09:35 PM UTC

    We are currently investigating this issue.

  2. investigating Aug 20, 2025, 09:36 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 20, 2025, 09:57 PM UTC

    Noticing elevated error rates across our KV stores.

  4. monitoring Aug 20, 2025, 10:42 PM UTC

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

  5. monitoring Aug 20, 2025, 10:43 PM UTC

    Related https://www.fastlystatus.com/incident/377843

  6. resolved Aug 20, 2025, 10:50 PM UTC

    This incident has been resolved.

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

Read the full incident report →