Contentful Outage History

Started Dec 10, 2025, 01:12 PM UTC· resolved Dec 10, 2025, 02:01 PM UTC

1. identified Dec 10, 2025, 01:12 PM UTC

   We've noticed an issue with the captcha service returning "Invalid Captcha" errors for user registrations and email confirmations and are now working on resolving it

2. resolved Dec 10, 2025, 02:01 PM UTC

   The issue is resolved now

Read the full incident report →

Started Dec 04, 2025, 10:33 AM UTC· resolved Dec 04, 2025, 11:40 AM UTC

1. investigating Dec 04, 2025, 10:33 AM UTC

   We are investigating spikes of increased latency on our Content Management API (CMA).

2. identified Dec 04, 2025, 10:54 AM UTC

   We have identified the cause of the issue and are working on a fix.

3. monitoring Dec 04, 2025, 11:23 AM UTC

   This issue has been mitigated and we are monitoring the result.

4. resolved Dec 04, 2025, 11:40 AM UTC

   This issue is now resolved.

Read the full incident report →

Started Dec 02, 2025, 03:12 PM UTC· resolved Dec 03, 2025, 09:03 AM UTC

1. investigating Dec 02, 2025, 03:12 PM UTC

   We've identified an issue affecting CMA API call usage reporting and Audit Logs since Nov 14, where certain fields are missing and data may be incomplete. As a result, some Audit Log events may be absent, and the CMA usage reports displayed in the web app may not accurately reflect actual usage. We are currently investigating and will provide updates as soon as we understand the full impact.

2. investigating Dec 02, 2025, 03:45 PM UTC

   The root cause has been identified, and a fix is in progress. At this stage, it appears that usage reporting is unaffected.

3. monitoring Dec 02, 2025, 05:04 PM UTC

   We've fixed the missing fields for Audit Logs and are now monitoring to ensure normal functionality is restored.

4. resolved Dec 03, 2025, 09:03 AM UTC

   Audit Logs have returned to their normal state and are fully operational again.

Read the full incident report →

Started Dec 02, 2025, 01:06 PM UTC· resolved Dec 02, 2025, 02:16 PM UTC

1. investigating Dec 02, 2025, 01:06 PM UTC

   Some customers are experiencing errors for cross-space references. We are investigating the situation.

2. investigating Dec 02, 2025, 01:23 PM UTC

   We've identified the issue. It is only affecting cross-space references for customers who are using fallback locales. We are working on a resolution.

3. monitoring Dec 02, 2025, 01:35 PM UTC

   We've resolved the issue and are monitoring the situation.

4. resolved Dec 02, 2025, 02:16 PM UTC

   The issue is resolved.

Read the full incident report →

Started Nov 21, 2025, 12:04 PM UTC· resolved Nov 21, 2025, 01:18 PM UTC

1. investigating Nov 21, 2025, 12:04 PM UTC

   Our Web App is currently operating in degraded mode with presence indicator not receiving data on users working with the entry. We are investigating the issue.

2. identified Nov 21, 2025, 12:22 PM UTC

   We have identified the issue and are working to deploy a fix.

3. monitoring Nov 21, 2025, 01:13 PM UTC

   We have deployed a fix and customers should now be able to see the presence indicator again.

4. resolved Nov 21, 2025, 01:18 PM UTC

   After monitoring the fix, we can confirm the issue is now fixed for all users.

Read the full incident report →

Started Nov 19, 2025, 04:58 PM UTC· resolved Nov 19, 2025, 04:58 PM UTC

1. monitoring Nov 19, 2025, 04:58 PM UTC

   We have identified and fixed the issue causing degraded webhook performance from 11/12/25 - 11/19/25, which may caused some webhook deliveries to be dropped. We are actively monitoring.

2. resolved Nov 19, 2025, 04:58 PM UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Read the full incident report →

Started Nov 18, 2025, 02:59 PM UTC· resolved Nov 18, 2025, 05:30 PM UTC

1. investigating Nov 18, 2025, 11:53 AM UTC

   Users are currently experiencing problems with Native External References. We are currently investigating.

2. investigating Nov 18, 2025, 12:07 PM UTC

   An issue with a 3rd party platform provider is causing an outage on Contentful Personalisation as well as Contentful Functions and Native External References. We are working with the provider on a resolution.

3. monitoring Nov 18, 2025, 12:21 PM UTC

   We are seeing recovery on all affected services. We will continue to monitor the situation.

4. identified Nov 18, 2025, 12:29 PM UTC

   While we did see initial recovery, Contentful Personalisation, Native External References and Functions are experiencing an outage again.

5. identified Nov 18, 2025, 12:57 PM UTC

   We are seeing brief periods of recovery on Contentful Personalisation, but the situation is still unstable. Customers will be experiencing intermittent failures trying to use affected services.

6. identified Nov 18, 2025, 01:24 PM UTC

   We have seen recovery on Contentful Personalisation for the past 20 mins, but Customers Native External references are experiencing intermittent issue. We are continuing to investigate.

7. identified Nov 18, 2025, 02:03 PM UTC

   Personalisation continues to be recovered. We are still seeing some intermittent errors for Native External References.

8. identified Nov 18, 2025, 02:54 PM UTC

   We are seeing full recovery across all affected services. We will continue to monitor the situation.

9. monitoring Nov 18, 2025, 02:59 PM UTC

   We have confirmed full recovery and are continuing to monitor.

10. resolved Nov 18, 2025, 05:30 PM UTC

    This issue has been resolved

Read the full incident report →

Started Nov 14, 2025, 04:00 PM UTC· resolved Nov 14, 2025, 04:00 PM UTC

1. resolved Nov 14, 2025, 04:11 PM UTC

   Between 15:52 and 15:56 UTC on 14 November, customers experienced a spike in errors on our Content Management and Content Delivery APIs. This also may have affected login and interactions on the Contentful WebApp.

Read the full incident report →

Started Nov 13, 2025, 02:08 PM UTC· resolved Nov 13, 2025, 03:12 PM UTC

1. investigating Nov 13, 2025, 02:08 PM UTC

   Some customers experience increased latency on the content management API. We're currently investigating the issue, and will provide an update soon.

2. monitoring Nov 13, 2025, 02:48 PM UTC

   We identified the cause of the increased errors on Contentful's Management API and have implemented a fix. We will continue to monitor the situation.

3. resolved Nov 13, 2025, 03:12 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Nov 13, 2025, 11:15 AM UTC· resolved Nov 13, 2025, 12:30 PM UTC

1. investigating Nov 13, 2025, 11:15 AM UTC

   Some EU customers experience increased latency on the content management API. We're currently investigating the issue, and will provide an update soon.

2. identified Nov 13, 2025, 11:33 AM UTC

   Some EU customers experience increased latency or error raters on the content management API. We have identified the issue and are working towards a resolution.

3. monitoring Nov 13, 2025, 11:39 AM UTC

   We have addressed the issue and are monitoring the situation.

4. resolved Nov 13, 2025, 12:30 PM UTC

   We have resolved the issue.

Read the full incident report →

Started Nov 05, 2025, 10:46 AM UTC· resolved Nov 05, 2025, 12:47 PM UTC

1. identified Nov 05, 2025, 10:46 AM UTC

   Customers using Chrome 142 or above are experiencing load failure for Preview iFrames due to missing local-network-access permissions. We have identified the cause and are testing a fix.

2. monitoring Nov 05, 2025, 12:42 PM UTC

   We have rolled out a fix for the issue and users should now be able to load their Live Preview content again.

3. resolved Nov 05, 2025, 12:47 PM UTC

   The issue is now resolved.

Read the full incident report →

Started Nov 05, 2025, 09:04 AM UTC· resolved Nov 05, 2025, 10:25 AM UTC

1. investigating Nov 05, 2025, 09:04 AM UTC

   Our team has identified that a recent backfill task caused tokens created over five years ago to become invalid. We are working on a fix and will continue to monitor the situation.

2. monitoring Nov 05, 2025, 10:05 AM UTC

   We have put a fix in place for this issue and API tokens should no longer return a 401 Unauthorized error

3. resolved Nov 05, 2025, 10:25 AM UTC

   This issue is now resolved.

Read the full incident report →

Started Nov 03, 2025, 06:24 PM UTC· resolved Nov 03, 2025, 07:24 PM UTC

1. identified Nov 03, 2025, 06:24 PM UTC

   We are currently experiencing an issue that is causing validation errors during token creation. Additionally, our team has identified that a recent backfill task caused tokens created over five years ago to become invalid. We have deployed a fix to correct these token expirations and are running a backfill to update affected tokens. We are continuing to monitor the situation closely and will provide further updates as they become available. We apologize for any inconvenience this may cause.

2. monitoring Nov 03, 2025, 07:21 PM UTC

   We've reverted the old token invalidation changes. Tokens that were previously resulting in unauthenticated errors should now be working again. We will continue to monitor the situation.

3. resolved Nov 03, 2025, 07:24 PM UTC

   This issue is now resolved.

Read the full incident report →

Started Oct 23, 2025, 03:11 PM UTC· resolved Oct 23, 2025, 03:18 PM UTC

1. identified Oct 23, 2025, 03:11 PM UTC

   We've spotted that something has gone wrong with Personalization UI and some APIs. We're currently investigating the issue, and will provide an update soon.

2. resolved Oct 23, 2025, 03:18 PM UTC

   The issue is resolved.

Read the full incident report →

Started Oct 22, 2025, 08:52 PM UTC· resolved Nov 10, 2025, 01:27 PM UTC

1. identified Oct 22, 2025, 08:52 PM UTC

   We have been receiving reports from customers that their websites are being blocked when end users are using Microsoft Edge in Strict mode. This is due to an incorrect tracker classification for some of Contenful’s domains (cdn.contentful.com). We are following up with the classification service owner to have Contentful domains removed from this list in order to mitigate this issue.

2. resolved Nov 10, 2025, 01:27 PM UTC

   Over the past weeks, we have worked with the Microsoft Edge team around this incorrect tracker classification. Contentful requests should no longer be blocked when Strict Mode is enabled on Microsoft Edge browser.

Read the full incident report →

Started Oct 21, 2025, 11:01 AM UTC· resolved Oct 21, 2025, 01:53 PM UTC

1. investigating Oct 21, 2025, 11:01 AM UTC

   Our monitoring systems have detected an outage of a upstream provider orchestrating jobs that are responsible for executing AI Actions and Workflow Automations. We expect to see delayed execution.

2. identified Oct 21, 2025, 12:57 PM UTC

   Our upstream provider has identified the cause of the issue and working on resolving it at the moment.

3. monitoring Oct 21, 2025, 01:21 PM UTC

   Our upstream provider has implemented a fix and we are seeing AI Actions and Automations recovery on execution durations. We are monitoring the health of the systems.

4. resolved Oct 21, 2025, 01:53 PM UTC

   AI Actions & Workflow Automations executions have been recovered to normal speed.

Read the full incident report →

Started Oct 20, 2025, 07:01 AM UTC· resolved Oct 20, 2025, 09:08 PM UTC

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.

Read the full incident report →

Started Oct 17, 2025, 05:16 PM UTC· resolved Oct 17, 2025, 05:25 PM UTC

1. investigating Oct 17, 2025, 05:16 PM UTC

   Customers are experiencing issues where entries cannot be added to Releases. We are investigating.

2. monitoring Oct 17, 2025, 05:20 PM UTC

   We have provided a resolution and will monitor the situation.

3. resolved Oct 17, 2025, 05:25 PM UTC

   The issue is resolved.

Read the full incident report →