- Detected by Pingoru
- Jan 22, 2026, 07:59 PM UTC
- Resolved
- Jan 22, 2026, 09:00 PM UTC
- Duration
- 1h
Affected: Web AppWeb AppScheduled PublishingScheduled Publishing
Timeline · 4 updates
-
investigating Jan 22, 2026, 07:59 PM UTC
Some customers are experiencing issues with scheduling actions. We are investigating the situation.
-
investigating Jan 22, 2026, 08:33 PM UTC
Scheduling publishing is affected when publishing entries in certain time zones. We are continuing the investigation.
-
monitoring Jan 22, 2026, 08:38 PM UTC
We have resolved the issue and are monitoring the situation.
-
resolved Jan 22, 2026, 09:00 PM UTC
The issue was resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 12:41 PM UTC
- Resolved
- Jan 22, 2026, 01:21 PM UTC
- Duration
- 40m
Affected: Content Management APIContent Delivery API
Timeline · 4 updates
-
investigating Jan 22, 2026, 12:41 PM UTC
We are seeing elevated errors for Management API traffic in our EU region, we are investigating the issue.
-
investigating Jan 22, 2026, 12:44 PM UTC
We are continuing to investigate this issue.
-
monitoring Jan 22, 2026, 12:57 PM 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.
-
resolved Jan 22, 2026, 01:21 PM UTC
This issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 21, 2026, 10:05 AM UTC
- Resolved
- Jan 21, 2026, 10:59 AM UTC
- Duration
- 54m
Affected: Web App
Timeline · 4 updates
-
investigating Jan 21, 2026, 10:05 AM UTC
We are investigating an issue where errors/warnings are inadvertently showing up in the Contentful WebApp.
-
investigating Jan 21, 2026, 10:07 AM UTC
We are still working on a fix for the issue - for some customers the licences page in Org Settings is failing to load.
-
monitoring Jan 21, 2026, 10:08 AM UTC
We have rolled out a fix and are monitoring the results.
-
resolved Jan 21, 2026, 10:59 AM UTC
This issue has been resolved
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 01:14 PM UTC
- Resolved
- Jan 16, 2026, 02:34 PM UTC
- Duration
- 1h 19m
Affected: Web AppWeb App
Timeline · 3 updates
-
investigating Jan 16, 2026, 01:14 PM UTC
We're investigating an issue reported by customers that while uploading assets it stays in processing until the page is refreshed.
-
monitoring Jan 16, 2026, 02:03 PM UTC
The issue causing assets to be stuck in processing state has been addressed, we are monitoring the fix.
-
resolved Jan 16, 2026, 02:34 PM UTC
The problem with assets being stuck in processing has been addressed all back to operational
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2026, 09:32 PM UTC
- Resolved
- Jan 14, 2026, 11:00 PM UTC
- Duration
- 1h 28m
Affected: Web AppWeb App
Timeline · 4 updates
-
investigating Jan 14, 2026, 09:32 PM UTC
Some customers are experiencing issues with adding entries to releases. We are investigating the situation.
-
identified Jan 14, 2026, 10:04 PM UTC
We have identified the issue and are addressing it.
-
monitoring Jan 14, 2026, 10:12 PM UTC
The issue is addressed. We are monitoring the situation.
-
resolved Jan 14, 2026, 11:00 PM UTC
The issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2026, 04:56 PM UTC
- Resolved
- Jan 14, 2026, 06:03 PM UTC
- Duration
- 1h 6m
Affected: Web App
Timeline · 4 updates
-
investigating Jan 14, 2026, 04:56 PM UTC
We are currently investigating an issue where customers are unable to upload assets in the Contentful WebApp.
-
monitoring Jan 14, 2026, 05:02 PM 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.
-
monitoring Jan 14, 2026, 05:06 PM UTC
This issue has been resolved.
-
resolved Jan 14, 2026, 06:03 PM UTC
Issue resolved. Customers can now upload assets through the web app as usual.
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 10:55 AM UTC
- Resolved
- Dec 15, 2025, 10:55 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 15, 2025, 10:55 AM 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 continue to see the error after that time period, a refresh will resolve the issue.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 01:12 PM UTC
- Resolved
- Dec 10, 2025, 02:01 PM UTC
- Duration
- 49m
Affected: Web AppWebsite
Timeline · 2 updates
-
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
-
resolved Dec 10, 2025, 02:01 PM UTC
The issue is resolved now
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2025, 10:33 AM UTC
- Resolved
- Dec 04, 2025, 11:40 AM UTC
- Duration
- 1h 6m
Affected: Content Management API
Timeline · 4 updates
-
investigating Dec 04, 2025, 10:33 AM UTC
We are investigating spikes of increased latency on our Content Management API (CMA).
-
identified Dec 04, 2025, 10:54 AM UTC
We have identified the cause of the issue and are working on a fix.
-
monitoring Dec 04, 2025, 11:23 AM UTC
This issue has been mitigated and we are monitoring the result.
-
resolved Dec 04, 2025, 11:40 AM UTC
This issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 03:12 PM UTC
- Resolved
- Dec 03, 2025, 09:03 AM UTC
- Duration
- 17h 50m
Timeline · 4 updates
-
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.
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Dec 02, 2025, 01:06 PM UTC
- Resolved
- Dec 02, 2025, 02:16 PM UTC
- Duration
- 1h 10m
Affected: Content Delivery APIGraphQL Content API
Timeline · 4 updates
-
investigating Dec 02, 2025, 01:06 PM UTC
Some customers are experiencing errors for cross-space references. We are investigating the situation.
-
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.
-
monitoring Dec 02, 2025, 01:35 PM UTC
We've resolved the issue and are monitoring the situation.
-
resolved Dec 02, 2025, 02:16 PM UTC
The issue is resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 12:04 PM UTC
- Resolved
- Nov 21, 2025, 01:18 PM UTC
- Duration
- 1h 13m
Affected: Web App
Timeline · 4 updates
-
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.
-
identified Nov 21, 2025, 12:22 PM UTC
We have identified the issue and are working to deploy a fix.
-
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.
-
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 →
- Detected by Pingoru
- Nov 19, 2025, 04:58 PM UTC
- Resolved
- Nov 19, 2025, 04:58 PM UTC
- Duration
- 29s
Affected: Webhooks
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Nov 18, 2025, 02:59 PM UTC
- Resolved
- Nov 18, 2025, 05:30 PM UTC
- Duration
- 2h 31m
Affected: Experience APIContent Delivery APIContent Delivery APIInsights APIManagement APIIntegration API
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Nov 14, 2025, 04:11 PM UTC
- Resolved
- Nov 14, 2025, 04:00 PM UTC
- Duration
- —
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Nov 13, 2025, 02:08 PM UTC
- Resolved
- Nov 13, 2025, 03:12 PM UTC
- Duration
- 1h 3m
Affected: Content Management APIWeb App
Timeline · 3 updates
-
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.
-
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.
-
resolved Nov 13, 2025, 03:12 PM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 13, 2025, 11:15 AM UTC
- Resolved
- Nov 13, 2025, 12:30 PM UTC
- Duration
- 1h 14m
Affected: Content Management API
Timeline · 4 updates
-
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.
-
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.
-
monitoring Nov 13, 2025, 11:39 AM UTC
We have addressed the issue and are monitoring the situation.
-
resolved Nov 13, 2025, 12:30 PM UTC
We have resolved the issue.
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 10:46 AM UTC
- Resolved
- Nov 05, 2025, 12:47 PM UTC
- Duration
- 2h
Affected: Web App
Timeline · 3 updates
-
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.
-
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.
-
resolved Nov 05, 2025, 12:47 PM UTC
The issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 05, 2025, 09:04 AM UTC
- Resolved
- Nov 05, 2025, 10:25 AM UTC
- Duration
- 1h 21m
Affected: Content Management API
Timeline · 3 updates
-
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.
-
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
-
resolved Nov 05, 2025, 10:25 AM UTC
This issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 03, 2025, 06:24 PM UTC
- Resolved
- Nov 03, 2025, 07:24 PM UTC
- Duration
- 1h
Affected: Content Management API
Timeline · 3 updates
-
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.
-
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.
-
resolved Nov 03, 2025, 07:24 PM UTC
This issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 23, 2025, 03:11 PM UTC
- Resolved
- Oct 23, 2025, 03:18 PM UTC
- Duration
- 7m
Affected: Management API
Timeline · 2 updates
-
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.
-
resolved Oct 23, 2025, 03:18 PM UTC
The issue is resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 22, 2025, 08:52 PM UTC
- Resolved
- Nov 10, 2025, 01:27 PM UTC
- Duration
- 18d 16h
Affected: Content Delivery API
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Oct 21, 2025, 11:01 AM UTC
- Resolved
- Oct 21, 2025, 01:53 PM UTC
- Duration
- 2h 52m
Affected: Content Management APIWeb App
Timeline · 4 updates
-
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.
-
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.
-
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.
-
resolved Oct 21, 2025, 01:53 PM UTC
AI Actions & Workflow Automations executions have been recovered to normal speed.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 07:01 AM UTC
- Resolved
- Oct 20, 2025, 09:08 PM UTC
- Duration
- 14h 6m
Affected: Content Management APIContent Delivery APIGraphQL Content APIAuthentication serviceWebhooksMarketplace AppsTaxonomy Delivery API
Timeline · 24 updates
Read the full incident report →
- Detected by Pingoru
- Oct 17, 2025, 05:16 PM UTC
- Resolved
- Oct 17, 2025, 05:25 PM UTC
- Duration
- 8m
Affected: Web AppWeb App
Timeline · 3 updates
-
investigating Oct 17, 2025, 05:16 PM UTC
Customers are experiencing issues where entries cannot be added to Releases. We are investigating.
-
monitoring Oct 17, 2025, 05:20 PM UTC
We have provided a resolution and will monitor the situation.
-
resolved Oct 17, 2025, 05:25 PM UTC
The issue is resolved.
Read the full incident report →
