Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Contentful outage history

    68 recorded Contentful incidents since October 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    Insights Dashboard failing to load

    Started October 20, 2026 at 7:22 AM UTC · 3h 6m

    OutageMajor incident
    Affected components
    Insights API
    1. October 20, 2026 at 7:22 AM UTCinvestigating

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

    2. October 20, 2026 at 8:57 AM UTCinvestigating

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

    3. October 20, 2026 at 9:53 AM UTCmonitoring

      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. October 20, 2026 at 10:28 AM UTCresolved

      This incident has been resolved.

    [INCIDENT] https://www.contentful.com/developers/docs/ is not working

    Started October 12, 2026 at 6:22 PM UTC · 4m

    OutageMajor incident
    Affected components
    Web App
    1. October 12, 2026 at 6:22 PM UTCidentified

      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. October 12, 2026 at 6:27 PM UTCresolved

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

    Issues with advanced caching on Content Delivery API

    Started October 1, 2026 at 9:27 AM UTC · 1d 0h

    OutageMajor incident
    Affected components
    Content Delivery APIContent Delivery API
    1. October 1, 2026 at 9:27 AM UTCidentified

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

    2. October 1, 2026 at 11:29 AM UTCidentified

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

    3. October 2, 2026 at 8:43 AM UTCmonitoring

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

    4. October 2, 2026 at 9:43 AM UTCresolved

      This issue has been resolved.

    CORS errors on CDA

    Started September 29, 2026 at 2:39 PM UTC · 1h 5m

    OutageMajor incident
    Affected components
    Content Delivery APIContent Delivery API
    1. September 29, 2026 at 2:39 PM UTCidentified

      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. September 29, 2026 at 3:16 PM UTCmonitoring

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

    3. September 29, 2026 at 3:44 PM UTCresolved

      The issue has been resolved.

    Cross-space content missing from CDA responses for some customers

    Started September 11, 2026 at 3:46 PM UTC · 2h 11m

    IssuesMinor incident
    Affected components
    Content Delivery API
    1. September 11, 2026 at 3:46 PM UTCidentified

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

    2. September 11, 2026 at 5:38 PM UTCmonitoring

      We have addressed the issue and are monitoring the situation.

    3. September 11, 2026 at 5:57 PM UTCresolved

      The issue has been resolved.

    Stale entries on Content Delivery API

    Started September 3, 2026 at 7:45 AM UTC · 5h 40m

    IssuesMinor incident
    Affected components
    Content Delivery API
    1. September 3, 2026 at 7:45 AM UTCinvestigating

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

    2. September 3, 2026 at 9:23 AM UTCinvestigating

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

    3. September 3, 2026 at 1:25 PM UTCresolved

      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.

    Daily audit logs outage

    Started August 27, 2026 at 4:26 PM UTC · 13h 24m

    IssuesMinor incident
    Affected components
    Enterprise ObservabilityEnterprise Observability
    1. August 27, 2026 at 4:26 PM UTCinvestigating

      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) missing but the log's themselves are intact, including userId and they remain operational.

    2. August 27, 2026 at 4:28 PM UTCidentified

      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. August 28, 2026 at 5:50 AM UTCresolved

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

    Issues with Space Add-ons

    Started August 24, 2026 at 12:12 PM UTC · 9h 25m

    IssuesMinor incident
    1. August 24, 2026 at 12:12 PM UTCidentified

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

    2. August 24, 2026 at 2:03 PM UTCidentified

      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. August 24, 2026 at 9:37 PM UTCresolved

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

    Experience API experiencing issues on upsert operations

    Started August 17, 2026 at 9:05 AM UTC · 2h 52m

    IssuesMinor incident
    Affected components
    Experience API
    1. August 17, 2026 at 9:05 AM UTCinvestigating

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

    2. August 17, 2026 at 9:37 AM UTCidentified

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

    3. August 17, 2026 at 10:19 AM UTCmonitoring

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

    4. August 17, 2026 at 11:56 AM UTCresolved

      The incident is resolved

    Errors on Content Management API

    Started August 13, 2026 at 9:34 AM UTC · 2h 4m

    OutageMajor incident
    Affected components
    Content Management API
    1. August 13, 2026 at 9:34 AM UTCinvestigating

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

    2. August 13, 2026 at 10:31 AM UTCmonitoring

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

    3. August 13, 2026 at 11:38 AM UTCresolved

      The issue has been addressed.

    Increased latency and error rates for Snapshots

    Started August 10, 2026 at 11:08 AM UTC · 3h 6m

    IssuesMinor incident
    Affected components
    Content Management APIContent Management API
    1. August 10, 2026 at 11:08 AM UTCidentified

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

    2. August 10, 2026 at 12:27 PM UTCidentified

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

    3. August 10, 2026 at 1:55 PM UTCmonitoring

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

    4. August 10, 2026 at 2:14 PM UTCresolved

      This incident has been resolved.

    Errors on requests to Contentful from Frankfurt (FRA) region

    Started July 3, 2026 at 9:32 AM UTC · 7h 54m

    IssuesMinor incident
    Affected components
    Web AppContent Management APIWeb AppContent Management API
    1. July 3, 2026 at 9:32 AM UTCidentified

      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 can temporarily workaround the issue by using a VPN when connecting to Contentful (which routes traffic to a different Point of Presence (POP) other than the affected FRA one).

    2. July 3, 2026 at 11:29 AM UTCidentified

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

    3. July 3, 2026 at 5:26 PM UTCresolved

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

    Errors on Contentful Content Management and Preview APIs.

    Started July 2, 2026 at 7:53 AM UTC · 6h 34m

    IssuesMinor incident
    Affected components
    Web AppContent Management APIAuthentication serviceWeb AppContent Management API
    1. July 2, 2026 at 7:53 AM UTCinvestigating

      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. July 2, 2026 at 8:11 AM UTCinvestigating

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

    3. July 2, 2026 at 9:53 AM UTCinvestigating

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

    4. July 2, 2026 at 10:32 AM UTCinvestigating

      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 Presence (POP) other than the affected FRA one).

    5. July 2, 2026 at 11:19 AM UTCidentified

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

    6. July 2, 2026 at 12:21 PM UTCmonitoring

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

    7. July 2, 2026 at 2:27 PM UTCresolved

      This issue has been resolved.

    Latency and errors using Content Model Templates

    Started June 30, 2026 at 10:53 AM UTC · 1h 28m

    IssuesMinor incident
    Affected components
    Content Management APIContent Management API
    1. June 30, 2026 at 10:53 AM UTCinvestigating

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

    2. June 30, 2026 at 11:26 AM UTCmonitoring

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

    3. June 30, 2026 at 12:21 PM UTCresolved

      This issue has been resolved.

    Issues signing in to Contentful using GitHub

    Started June 29, 2026 at 1:30 PM UTC · 1d 1h

    IssuesMinor incident
    Affected components
    Authentication service
    1. June 29, 2026 at 1:30 PM UTCinvestigating

      We are investigating an issue where some customers may be unable to sign in to Contentful using GitHub - all other login methods are operational.

    Periodic errors and latency spikes on Contentful Management and Preview APIs.

    Started June 28, 2026 at 10:00 PM UTC · 0m

    Pending
    1. June 29, 2026 at 1:19 PM UTCresolved

      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 June) - the issue has been resolved

    Connection issues with the Management and Preview APIs

    Started June 18, 2026 at 4:11 PM UTC · 4h 46m

    IssuesMinor incident
    Affected components
    Web AppContent Management API
    1. June 18, 2026 at 4:11 PM UTCinvestigating

      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. June 18, 2026 at 4:13 PM UTCinvestigating

      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. June 18, 2026 at 5:14 PM UTCidentified

      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. June 18, 2026 at 7:24 PM UTCidentified

      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. June 18, 2026 at 8:25 PM UTCmonitoring

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

    6. June 18, 2026 at 8:58 PM UTCresolved

      This issue is now resolved.

    Cloudinary asset picker not working

    Started June 18, 2026 at 7:57 AM UTC · 27m

    Pending
    Affected components
    Marketplace Apps
    1. June 18, 2026 at 7:57 AM UTCinvestigating

      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. June 18, 2026 at 8:24 AM UTCresolved

      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.

    Issues with full-text search and locale-based publishing for some EU customers

    Started June 12, 2026 at 7:53 AM UTC · 12h 47m

    IssuesMinor incident
    Affected components
    Content Management API
    1. June 12, 2026 at 7:53 AM UTCidentified

      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. June 12, 2026 at 11:02 AM UTCidentified

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

    3. June 12, 2026 at 12:26 PM UTCmonitoring

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

    4. June 12, 2026 at 1:48 PM UTCidentified

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

    5. June 12, 2026 at 3:49 PM UTCidentified

      We continue working towards full resolution.

    6. June 12, 2026 at 8:40 PM UTCresolved

      We have resolved the issue.

    Issues with content editing and publishing for some EU customers

    Started June 11, 2026 at 12:29 PM UTC · 8h 32m

    IssuesMinor incident
    Affected components
    Content Management APIContent Delivery APIGraphQL Content APIGraphQL Content APIContent Delivery APIContent Management API
    1. June 11, 2026 at 12:29 PM UTCidentified

      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. June 11, 2026 at 1:37 PM UTCidentified

      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. June 11, 2026 at 3:24 PM UTCidentified

      We continue working on the resolution.

    4. June 11, 2026 at 5:05 PM UTCidentified

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

    5. June 11, 2026 at 9:00 PM UTCresolved

      We have resolved the issue.