Contentful incident

Errors across several services affecting Contentful APIs and the web app

Major Resolved View vendor source →

Contentful experienced a major incident on October 20, 2025 affecting Content Management API and Content Delivery API and 1 more component, lasting 14h 6m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 07:01 AM UTC
Resolved
Oct 20, 2025, 09:08 PM UTC
Duration
14h 6m
Detected by Pingoru
Oct 20, 2025, 07:01 AM UTC

Affected components

Content Management APIContent Delivery APIGraphQL Content APIAuthentication serviceWebhooksMarketplace AppsTaxonomy Delivery API

Update timeline

  1. investigating Oct 20, 2025, 07:01 AM UTC

    Some customers are experiencing errors using the GraphQL API.

  2. investigating Oct 20, 2025, 07:08 AM UTC

    Underlying issues affect multiple components, including the Contentful web app as well as delivery and management APIs.

  3. investigating Oct 20, 2025, 07:16 AM UTC

    Several of Contentful's components are affect by an outage at a 3rd party vendor, including the Contentful web app and the management and delivery APIs.

  4. investigating Oct 20, 2025, 07:38 AM UTC

    Several of Contentful's components remain affect by an outage at a 3rd party provider, including the Contentful web app and the management and delivery APIs. We are following the situation closely and are working with the provider to resolve issue.

  5. investigating Oct 20, 2025, 07:52 AM UTC

    Several of Contentful's components remain affect by an outage at a 3rd party provider, including the Contentful web app and the management and delivery APIs. We continue to follow the situation closely and are working with the provider to resolve issue.

  6. investigating Oct 20, 2025, 08:52 AM UTC

    Several of Contentful's components remain affect by an outage at a 3rd party provider, including the Contentful web app and the management and delivery APIs. We continue to follow the situation closely and are working with the provider to resolve issue. Authentication errors currently prevent customers to submit tickets.

  7. investigating Oct 20, 2025, 08:58 AM UTC

    Several of Contentful's components remain affect by an outage at a 3rd party provider, including the Contentful web app and the management and delivery APIs. We continue to follow the situation closely and are working with the provider to resolve issue. While the underlaying issue remains, we are providing temporary fixes for certain workloads. Authentication errors currently prevent customers from submitting tickets.

  8. identified Oct 20, 2025, 09:29 AM UTC

    Several components are still affected but we are seeing partial recovery and reduced error rates. We continue to work towards fully resolving the issue with our provider and will provide further updates. Authentication errors still prevent some customers from submitting tickets.

  9. identified Oct 20, 2025, 09:39 AM UTC

    We are mostly recovered but are still experiencing issues with webhooks. We are working towards a full recovery and will continue to provide updates.

  10. identified Oct 20, 2025, 10:20 AM UTC

    Webhooks remain to be affected with customers experiencing delays. Other components are operational. We are working towards a full recovery and will continue to provide updates.

  11. identified Oct 20, 2025, 10:54 AM UTC

    We are still working on the issue related to Webhooks not being process/triggered. All other Contentful services are operational.

  12. identified Oct 20, 2025, 11:20 AM UTC

    Due to the large failure with our 3rd party provider we have seen that publish events are not being processed at the moment. We have manually purged our cache (so recent changes should be reflected now). Until we are able to fully recover publishing events we will continue to manually purge cache periodically which will mean a delay for customers in seeing their published changes reflected.

  13. identified Oct 20, 2025, 11:59 AM UTC

    Publishing events and Webhooks are now being processed again. Customer may see some old events from the start of the outage (until the full backlog is cleared).

  14. identified Oct 20, 2025, 12:54 PM UTC

    While all systems are back operational again, we are still seeing some residual errors on GraphQL which we are investigating.

  15. monitoring Oct 20, 2025, 01:07 PM UTC

    All systems are back to normal operation. We will continue to monitor the situation.

  16. identified Oct 20, 2025, 03:35 PM UTC

    We are seeing issues again with the Contentful Webhook system which means that Webhooks are not being triggered. We are investigating the issue.

  17. identified Oct 20, 2025, 03:48 PM UTC

    Webhooks for customers is still experiencing an outage. Customers are also seeing delays in publishing of content being updated.

  18. identified Oct 20, 2025, 03:55 PM UTC

    We continue to investigate the issues related to Contentful services listed below: Webhooks: Webhooks system is still experiencing a major outage. Publishing: Some customer publishing may be delayed in being updated. Merge App: Merges are not completing using the Merge App.

  19. identified Oct 20, 2025, 04:42 PM UTC

    We are still investigating the issues related to publishing (delayed), Webhooks (outage) and Merge App (merges not completing).

  20. identified Oct 20, 2025, 05:39 PM UTC

    We continue to investigate the issues related to publishing (delayed), Webhooks (outage) and Merge App (merges not completing).

  21. identified Oct 20, 2025, 06:38 PM UTC

    Customers are continuing to see issues with publishing (delayed), Webhooks (outage) and Merge App (merges not completing).

  22. identified Oct 20, 2025, 08:07 PM UTC

    We have seen a recovery in publishing events and processed the backlog of outstanding events. We continue to see delays in Webhook events (as backlog is being processed)

  23. monitoring Oct 20, 2025, 08:48 PM UTC

    We are now seeing full recovery across all services. Webhooks and publishing are back operating as normal. We will continue to monitor the situation.

  24. resolved Oct 20, 2025, 09:08 PM UTC

    This issue is now resolved.