Kontent.ai incident

Problems With Fastly API Could Cause Stale Content to Be Served to Customers in Some Regions.

Major Resolved View vendor source →

Kontent.ai experienced a major incident on January 22, 2026 affecting Delivery REST API and Delivery REST API and 1 more component, lasting 2h 53m. The incident has been resolved; the full update timeline is below.

Started
Jan 22, 2026, 04:32 PM UTC
Resolved
Jan 22, 2026, 07:25 PM UTC
Duration
2h 53m
Detected by Pingoru
Jan 22, 2026, 04:32 PM UTC

Affected components

Delivery REST APIDelivery REST APIDelivery GraphQL APIDelivery GraphQL API

Update timeline

  1. investigating Jan 22, 2026, 04:32 PM UTC

    We are experiencing a problem in which the Fastly API isn't purging outdated content in the US and EU regions. We are currently investigating the issue and will provide updates as soon as possible.

  2. identified Jan 22, 2026, 05:16 PM UTC

    The problem has been identified as a bug in a recent update. We are working to fix this currently.

  3. resolved Jan 22, 2026, 07:25 PM UTC

    This incident has been resolved. Ultimately, the issue stemmed from an error that prevented entities from being deleted in a given database table. All of the failed deletions were manually cleared, and now cache purging works as intended. We will continue to investigate how this occurred, but the Delivery API shouldn't be returning stale content at this point.