Contentful incident

Customers experiencing issues on all APIs related to tags and taxonomy concepts

Major Resolved View vendor source →

Contentful experienced a major incident on August 21, 2025 affecting Content Management API and Content Management API and 1 more component, lasting 23h 45m. The incident has been resolved; the full update timeline is below.

Started
Aug 21, 2025, 09:13 AM UTC
Resolved
Aug 22, 2025, 08:59 AM UTC
Duration
23h 45m
Detected by Pingoru
Aug 21, 2025, 09:13 AM UTC

Affected components

Content Management APIContent Management APIContent Delivery APIContent Delivery APIGraphQL Content APIGraphQL Content API

Update timeline

  1. identified Aug 21, 2025, 09:13 AM UTC

    Free-tier customers are experiencing issues on all content APIs related to tags and taxonomy concepts that can lead to inconsistent responses or errors. We are working to resolve the issue.

  2. identified Aug 21, 2025, 10:00 AM UTC

    Customers are experiencing issues on all content APIs related to tags and taxonomy concepts that can lead to inconsistent responses or errors. We are working to resolve the issue.

  3. identified Aug 21, 2025, 10:05 AM UTC

    Customers are experiencing issues on all content APIs related to tags and taxonomy concepts that can lead to inconsistent responses or errors. We are working to resolve the issue.

  4. identified Aug 21, 2025, 10:57 AM UTC

    Customers are experiencing issues on all content APIs related to tags and taxonomy concepts that can lead to inconsistent responses or errors. We are actively working on resolving the issues and the situation is recovering progressively.

  5. identified Aug 21, 2025, 12:40 PM UTC

    We are still actively working on resolving the issues and the situation is recovering progressively.

  6. identified Aug 21, 2025, 03:17 PM UTC

    We continue to work on a fix for this issue and have already seen resolution for many customers affected by it.

  7. identified Aug 21, 2025, 04:56 PM UTC

    We continue to work on a fix for this issue and have already seen resolution for the majority of customers affected by it.

  8. monitoring Aug 22, 2025, 08:18 AM UTC

    We have resolved the issue for all customers and are monitoring the situation.

  9. resolved Aug 22, 2025, 08:59 AM UTC

    This issue has been resolved.