Contentful

Affected: Insights API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-20 07:22 UTC

   We are investigating an issue where the Contentful Insights Dashboard is failing to load for customers.

2. investigating 2026-10-20 08:57 UTC

   Our upstream data provider is experiencing degrading performance, making most of our Optimization insights unavailable

3. monitoring 2026-10-20 09:53 UTC

   The issue with our upstream provider has been resolved and the Insights API and Dashboard are back to normal operation. We are monitoring the situation.

4. resolved 2026-10-20 10:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-12 18:22 UTC

   Our monitoring systems have detected an outage of Contentful Docs (https://www.contentful.com/developers/docs/) we're investigating the nature and the cause of the outage and we'll update this incident as we have more details

2. resolved 2026-10-12 18:27 UTC

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

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Delivery API, Content Delivery API

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-01 09:27 UTC

   We are investigating issues with advanced caching (specifically Stale While Revalidate (SWR)). We have identified the issue and are working towards a resolution.

2. identified 2026-10-01 11:29 UTC

   The issue has been resolved for most customers. We continue to work on a resolution for everyone.

3. monitoring 2026-10-02 08:43 UTC

   The fix we implemented has resolved the issue for the remaining customers. We continue to monitor the situation.

4. resolved 2026-10-02 09:43 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Delivery API, Content Delivery API

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-29 14:39 UTC

   Some customers are seeing CORS preflight failures when requesting cross-space references on CDA through webbrowsers. We've identified the cause and are working on resolution.

2. monitoring 2026-09-29 15:16 UTC

   The issue has been resolved. We are monitoring the situation.

3. resolved 2026-09-29 15:44 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Delivery API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-11 15:46 UTC

   Some customers are experiencing issues on CDA where cross-space requests are returning incomplete results. We are working on a resolution.

2. monitoring 2026-09-11 17:38 UTC

   We have addressed the issue and are monitoring the situation.

3. resolved 2026-09-11 17:57 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Delivery API

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 07:45 UTC

   Some customers in the EU data residency region are receiving stale entries from Content Delivery API. We are investigating.

2. investigating 2026-09-03 09:23 UTC

   We are continuing to investigate this issue impacting a subset of customers in the EU.

3. resolved 2026-09-03 13:25 UTC

   We identified the source of the issue which caused some items which were purged to get stuck in cache. We have complete a full cache purge in the EU and the issue is now resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Enterprise Observability, Enterprise Observability

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-27 16:26 UTC

   Our monitoring systems have detected an outage of daily audit logs we're investigating the nature and the cause of the outage and we'll update this incident as we have more details. There is minor side effects on real time audit logs in terms of actor details (email, username)...

2. identified 2026-08-27 16:28 UTC

   We've identified the issue and are working to resolve the daily audit logs for today, we've also confirmed that EU is unaffected.

3. resolved 2026-08-28 05:50 UTC

   The issue is resolved and audit logs are delivered as expected again.

Excerpts are shortened. Read the full incident on Contentful's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-24 12:12 UTC

   Some customers are experiencing issues with add-ons not being applied correctly to their spaces. We are working on a fix.

2. identified 2026-08-24 14:03 UTC

   Some customers in the US data residency region are still experiencing issues with add-ons not being applied correctly to their spaces. We are working on a resolution.

3. resolved 2026-08-24 21:37 UTC

   We have implemented a fix and the issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Experience API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-17 09:05 UTC

   We are investigating an issue where customers are experiencing errors with upsert operations on the Personalization Experience API.

2. identified 2026-08-17 09:37 UTC

   We have identified the issue and are working with our upstream provider to provide a fix.

3. monitoring 2026-08-17 10:19 UTC

   We have mitigated the issue and are seeing improvements on the error rates. We will continue monitoring the situation.

4. resolved 2026-08-17 11:56 UTC

   The incident is resolved

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-13 09:34 UTC

   Some customers in the EU data residency region are experiencing latency and errors on Content Management API. We are investigating.

2. monitoring 2026-08-13 10:31 UTC

   Error rates and latency on Content Management API in the EU data residency have improved. We continue to monitor the situation.

3. resolved 2026-08-13 11:38 UTC

   The issue has been addressed.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Content Management API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-10 11:08 UTC

   Some customers are experiencing increased latency and errors when working with Snapshots. We are working on a resolution.

2. identified 2026-08-10 12:27 UTC

   Snapshot creation remains impacted. We continue to work on resolving the issue.

3. monitoring 2026-08-10 13:55 UTC

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

4. resolved 2026-08-10 14:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Content Management API, Web App, Web App

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-03 09:32 UTC

   We are seeing elevated errors and latency for some customer requests which are routing through the Frankfurt (FRA) region for Content Management, Preview and the Contentful WebApp. We are working with our upstream CDN provider to mitigate the issue. Customers affected by this...

2. identified 2026-07-03 11:29 UTC

   Error rates have dropped back down again to normal levels. We are continuing to monitor the situation.

3. resolved 2026-07-03 17:26 UTC

   We have taken action and error rates have returned to normal.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Content Management API, Authentication service, Web App, Web App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-02 07:53 UTC

   We are investigating an issues where some customers are seeing increased errors and latency when trying to access Contentful Management and Preview APIs (CMA and CPA) - this issue also affects the Contentful WebApp.

2. investigating 2026-07-02 08:11 UTC

   We are continuing to investigate this issue. Note: This is mostly affecting customer requests routed through the Frankfurt region.

3. investigating 2026-07-02 09:53 UTC

   We are continuing to work with one of our upstream CDN providers on resolving this issue.

4. investigating 2026-07-02 10:32 UTC

   We are continuing to work with our upstream CDN provider on mitigating this issue with traffic routing through the Frankfurt region. Some customers have been able workaround the issue by using a VPN when connecting to Contentful (which routes traffic to a different Point of...

5. identified 2026-07-02 11:19 UTC

   Traffic has been routed away from the affected POP (FRA) and error rates have dropped as a result.

6. monitoring 2026-07-02 12:21 UTC

   Routing traffic away from the affected POP (FRA) has been effective in mitigating this issue. We are continuing to monitor the situation.

7. resolved 2026-07-02 14:27 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Content Management API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-30 10:53 UTC

   Customers are experiencing increased latency and errors working with Content Model Templates . We are investigating.

2. monitoring 2026-06-30 11:26 UTC

   We have applied a fix for the issues with Content Model Templates and are monitoring the results.

3. resolved 2026-06-30 12:21 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-06-28 22:00 UTC

   Due to an issue identified with an external provider a small portion of customer traffic may have experienced periodic spells of higher latency or timeouts / errors when making requests to the Contentful Management and Contentful Preview APIs in the past few days (26th to 29th...

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Web App

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-18 16:11 UTC

   Some customers are receiving 500 error responses when accessing the Content Preview API. The Management API also powers our Web App and therefore the Web App is also operating in degraded mode. We are investigating the issue.

2. investigating 2026-06-18 16:13 UTC

   Some customers are receiving 500 error responses when accessing the Content Preview and Management APIs. The Management API also powers our Web App and therefore the Web App is also operating in degraded mode. We are investigating the issue

3. identified 2026-06-18 17:14 UTC

   We have identified the issue and are working to resolve it. The impact remains limited to specific points of presence in our CDN so the majority of customers should see no impact at all.

4. identified 2026-06-18 19:24 UTC

   The issue has been mitigated in one of our edge network PoPs, although a small number of customers continue to see errors. We are continuing to engage our third-party provider to resolve the issue completely.

5. monitoring 2026-06-18 20:25 UTC

   Error rates have returned to normal. We continue to monitor the situation.

6. resolved 2026-06-18 20:58 UTC

   This issue is now resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Marketplace Apps

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-18 07:57 UTC

   We have noticed an issue where the asset picker in the Cloudinary Marketplace app is not working. We are investigating and will post an update when we know more.

2. resolved 2026-06-18 08:24 UTC

   The asset picker in the Cloudinary Marketplace app was not working. The issue is resolved. Customers may need to do a hard refresh to clear their browser cache.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-12 07:53 UTC

   Some customers in the EU may experience issues finding content via full-text search. We have identified the issue and are working on a resolution.

2. identified 2026-06-12 11:02 UTC

   We have resolved the issue for the majority of customers and are continuing working on full resolution.

3. monitoring 2026-06-12 12:26 UTC

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

4. identified 2026-06-12 13:48 UTC

   A small amount of EU customers might still experience issues related to locale-based publishing. We are working on resolving these.

5. identified 2026-06-12 15:49 UTC

   We continue working towards full resolution.

6. resolved 2026-06-12 20:40 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Content Management API, Content Delivery API, Content Delivery API, GraphQL Content API, GraphQL Content API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-11 12:29 UTC

   Some customers in the EU might see intermittent problems with editing and publishing content. We have identified the underlying issue and are working to resolve it.

2. identified 2026-06-11 13:37 UTC

   Editing and publishing errors have been resolved, but some published entries may not yet appear in filtered API requests for a small amount of EU customers. We continue working on the resolution.

3. identified 2026-06-11 15:24 UTC

   We continue working on the resolution.

4. identified 2026-06-11 17:05 UTC

   We continue working on the fix and have already seen resolution for the majority of customers affected by it.

5. resolved 2026-06-11 21:00 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Contentful's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-09 13:57 UTC

   The Optimization tab is unavailable for Contentful Personalization and Contentful Analytics customers.

2. resolved 2026-06-09 14:18 UTC

   We have resolved the underlying issue, the Optimization Hub is available again.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App, Web App, Website

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-02 13:02 UTC

   Some customers are experiencing issues uploading files. We are investigating.

2. identified 2026-06-02 13:27 UTC

   Uploads via 3rd party cloud integrations are affected. We are working on a resolution.

3. resolved 2026-06-02 14:51 UTC

   We think the impact from the issue is over, however, uploads using 3rd cloud providers (Google Drive, Instagram, Box, Dropbox etc) are temporarily disabled.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App, Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-26 17:02 UTC

   Some customers are experiencing issues with the Contentful Web App. We are investigating.

2. monitoring 2026-05-26 17:08 UTC

   We have addressed the issue and are monitoring the situation.

3. resolved 2026-05-26 17:17 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-19 16:57 UTC

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

2. resolved 2026-05-19 20:17 UTC

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

Excerpts are shortened. Read the full incident on Contentful's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-05-19 16:28 UTC

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

2. resolved 2026-05-19 16:29 UTC

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

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-13 13:47 UTC

   Customers are experiencing errors on CMA and within the Web App, we are investigating.

2. monitoring 2026-05-13 13:52 UTC

   We have resolved the issue and are monitoring the situation.

3. resolved 2026-05-13 13:57 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-05 13:13 UTC

   Due to an internal change in data permissions, some audit logging data was not delivered to customers between April 30 and May 4. The pipeline has since recovered, and today’s logs are being delivered as expected. We are now working to restore the missing logs from the past few...

2. resolved 2026-05-05 14:41 UTC

   We've recovered the logs for all customers for the affected dates and these have been sent through to customer storage.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Website

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-04 13:20 UTC

   Some customers are experiencing issues logging in/receiving email communication such as invitations and password resets. We are investigating.

2. identified 2026-05-04 14:06 UTC

   We have identified the issue and are addressing it. Most emails are being sent again. SSO login issues have been resolved

3. monitoring 2026-05-04 14:08 UTC

   All issues have been resolved, we are monitoring the situation.

4. resolved 2026-05-04 16:30 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-28 11:59 UTC

   Some customers are reporting issues accessing their spaces/environments in the Contentful web app. We are investigating the issue.

2. monitoring 2026-04-28 12:05 UTC

   This was a transient issue and has resolved. We continue to monitor the situation.

3. resolved 2026-04-28 12:22 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-23 13:39 UTC

   Some Customers are experiencing issues with workflows, we are investigating.

2. identified 2026-04-23 14:09 UTC

   We are working on improving the situation and see reduced error rates on workflows management.

3. resolved 2026-04-23 14:18 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Content Delivery API, GraphQL Content API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-23 11:38 UTC

   Some customers are experiencing 500 errors on our APIs. We are investigating.

2. monitoring 2026-04-23 11:52 UTC

   The situation has improved. We will continue to monitor.

3. resolved 2026-04-23 11:57 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App, Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-13 13:02 UTC

   Some customers are reporting spaces not being shown in the Contentful web app. We are investigating.

2. monitoring 2026-04-13 13:33 UTC

   Customers are reporting spaces are accessible in the web app again. We are monitoring the situation.

3. resolved 2026-04-13 14:03 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-07 19:33 UTC

   We've spotted that something has gone wrong with certain components in the web app. We're currently investigating the issue, and will provide an update soon.

2. identified 2026-04-07 19:44 UTC

   We have identified the issue and are beginning to roll out a fix. We anticipate this taking approximately one hour, and will continue to provide updates. This incident is impacting web app views only for certain components, but is not impacting data.

3. resolved 2026-04-07 20:31 UTC

   We have completed the rollout of the fix and believe all organizations should have restored functionality.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-03-31 14:58 UTC

   We have identified an issue where customers see an error when trying to access organisation settings in the Contentful WebApp. We have already applied a fix and are verifying the results.

2. resolved 2026-03-31 15:03 UTC

   We have validated that the fix resolved the issue and customers are no longer seeing errors when accessing the org settings page in the Contentful WebApp.

Excerpts are shortened. Read the full incident on Contentful's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-19 18:36 UTC

   We're currently investigating reports of SSO login errors.

2. identified 2026-03-19 18:42 UTC

   We have identified a possible cause of the SSO login error, and are addressing it now.

3. monitoring 2026-03-19 18:49 UTC

   We have confirmed that customers are seeing resolution of the issue, and are currently monitoring for further confirmation.

4. resolved 2026-03-19 18:54 UTC

   The issue is fully resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-13 12:41 UTC

   We've spotted that something has gone wrong. The Optimization page is not loading. We're currently investigating the issue, and will provide an update soon.

2. resolved 2026-03-13 13:13 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 17:48 UTC

   We observed a high amount of CMA errors in the past 15 minutes. The errors have already subsided but we are actively investigating the problem.

2. monitoring 2026-03-12 18:00 UTC

   The issue which caused the error spike on the Contentful Management API (CMA) has resolved. We are continuing to monitor.

3. resolved 2026-03-12 18:29 UTC

   This issue is fully resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Content Delivery API, GraphQL Content API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-03 12:25 UTC

   Some customers may be seeing elevated error rates from Contentful APIs. We are currently investigating the issue.

2. monitoring 2026-03-03 13:01 UTC

   We have identified the issue and customers should see errors reduced to normal levels.

3. resolved 2026-03-03 13:47 UTC

   This issue should now be resolved for all customers.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App, Studio

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-17 20:55 UTC

   Some customers will find certain features like e.g. Studio disabled. We have identified the issue and are working on a fix.

2. monitoring 2026-02-17 21:33 UTC

   We addressed the issue and are monitoring the situation.

3. identified 2026-02-17 21:54 UTC

   We are still observing issues for some customers and are working on a resolution.

4. monitoring 2026-02-17 22:07 UTC

   We have resolved the issue and are monitoring the situation.

5. resolved 2026-02-17 22:16 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App, Web App, Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-09 12:31 UTC

   Customers are experiencing issues with uploading assets, specifically SVGs. We are investigating.

2. identified 2026-02-09 12:48 UTC

   Uploads of XML-like file types, e.g. SVG, are failing. We are working on a resolution.

3. identified 2026-02-09 13:20 UTC

   We have enabled a simpler fallback uploader that provides less functionality while we investigate the issue (XML-like file types, e.g. SVG, are working again though). Customers will need to reload the Contentful WebApp to use the fallback uploader.

4. monitoring 2026-02-09 20:21 UTC

   We were able to mitigate the issue and have re-enabled the regular file uploader.

5. resolved 2026-02-09 20:54 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Content Delivery API, GraphQL Content API

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-06 11:03 UTC

   We are investigating an issue where cache purges are not being processed (which may result in customers seeing stale data).

2. identified 2026-02-06 11:35 UTC

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

3. identified 2026-02-06 14:09 UTC

   We are still working to mitigate the issue and expect to have a fix in place within the next 30 minutes

4. monitoring 2026-02-06 14:25 UTC

   We have deployed a fix which has resolved the issue. We will continue to monitor.

5. monitoring 2026-02-06 16:46 UTC

   We think the impact from the issue is over.

6. resolved 2026-02-06 17:19 UTC

   The issue is now resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Marketplace Apps

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-06 09:34 UTC

   Customers are experiencing issues loading the typeform app, we are investigating.

2. monitoring 2026-02-06 10:37 UTC

   We have put a fix in place and the Typeform app should now be functional again.

3. monitoring 2026-02-06 10:38 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-02-06 10:44 UTC

   The issue is now resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: GraphQL Content API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-27 15:41 UTC

   We are investigating an issue where some customers are experiencing errors containing “COLLIDING_TYPE_NAMES” when using Contentful GraphQL API. This is occurring in particular when customers have content types named “Pages”. We are working on a fix for this issue.

2. monitoring 2026-01-27 16:06 UTC

   We have deployed a fix which has mitigated the issue for customers. We are continuing to monitor the situation.

3. resolved 2026-01-27 16:28 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App, Web App, Scheduled Publishing, Scheduled Publishing

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-22 19:59 UTC

   Some customers are experiencing issues with scheduling actions. We are investigating the situation.

2. investigating 2026-01-22 20:33 UTC

   Scheduling publishing is affected when publishing entries in certain time zones. We are continuing the investigation.

3. monitoring 2026-01-22 20:38 UTC

   We have resolved the issue and are monitoring the situation.

4. resolved 2026-01-22 21:00 UTC

   The issue was resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Content Management API, Content Delivery API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-22 12:41 UTC

   We are seeing elevated errors for Management API traffic in our EU region, we are investigating the issue.

2. investigating 2026-01-22 12:44 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-01-22 12:57 UTC

   We have implemented a fix and the Contentful Management API is now operated normally again in the EU region. We are continuing to monitor the situation.

4. resolved 2026-01-22 13:21 UTC

   This issue is now resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-21 10:05 UTC

   We are investigating an issue where errors/warnings are inadvertently showing up in the Contentful WebApp.

2. investigating 2026-01-21 10:07 UTC

   We are still working on a fix for the issue - for some customers the licences page in Org Settings is failing to load.

3. monitoring 2026-01-21 10:08 UTC

   We have rolled out a fix and are monitoring the results.

4. resolved 2026-01-21 10:59 UTC

   This issue has been resolved

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App, Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-16 13:14 UTC

   We're investigating an issue reported by customers that while uploading assets it stays in processing until the page is refreshed.

2. monitoring 2026-01-16 14:03 UTC

   The issue causing assets to be stuck in processing state has been addressed, we are monitoring the fix.

3. resolved 2026-01-16 14:34 UTC

   The problem with assets being stuck in processing has been addressed all back to operational

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App, Web App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-14 21:32 UTC

   Some customers are experiencing issues with adding entries to releases. We are investigating the situation.

2. identified 2026-01-14 22:04 UTC

   We have identified the issue and are addressing it.

3. monitoring 2026-01-14 22:12 UTC

   The issue is addressed. We are monitoring the situation.

4. resolved 2026-01-14 23:00 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-14 16:56 UTC

   We are currently investigating an issue where customers are unable to upload assets in the Contentful WebApp.

2. monitoring 2026-01-14 17:02 UTC

   We have deployed a fix which has resolved the issue with Asset uploads in the WebApp. Customers may need to refresh their page if the file uploads are still not working.

3. monitoring 2026-01-14 17:06 UTC

   This issue has been resolved.

4. resolved 2026-01-14 18:03 UTC

   Issue resolved. Customers can now upload assets through the web app as usual.

Excerpts are shortened. Read the full incident on Contentful's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-12-15 10:55 UTC

   Between 08:40 and 09:20 UTC customers experienced errors when trying to log in to Contentful ("Something went wrong"). This was due to a change we made to our bot protection logic. Once we saw the impact of the change, we reverted and the issue was resolved. If any customers...

Excerpts are shortened. Read the full incident on Contentful's status page.

Affected: Web App, Website

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-10 13:12 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 2025-12-10 14:01 UTC

   The issue is resolved now

Excerpts are shortened. Read the full incident on Contentful's status page.