outages.live
Live

Contentful

Contentful is operational

Checked 50 s ago Operational

History

90 days agoToday

Incidents in 90 days

11

Days with an incident

13

Median duration

3 h 6 min

Longest incident

24 h 16 min

Components

35
Content Management API Operational
90 days ago1 day with an incidentToday
Content Delivery API Operational
90 days ago4 days with an incidentToday
GraphQL Content API Operational
90 days agoNo incidentsToday
Authentication service Operational
90 days agoNo incidentsToday
Web App Operational
90 days ago1 day with an incidentToday
Website Operational
90 days agoNo incidentsToday
Assets CDN Operational
90 days agoNo incidentsToday
Webhooks Operational
90 days agoNo incidentsToday
Scheduled Publishing Operational
90 days agoNo incidentsToday
Launch Operational
90 days agoNo incidentsToday
Compose Operational
90 days agoNo incidentsToday
Studio Operational
90 days agoNo incidentsToday
Customer Support System Operational
90 days agoNo incidentsToday
Marketplace Apps Operational
90 days agoNo incidentsToday
Image API Operational
90 days agoNo incidentsToday
Transactional Emails Operational
90 days agoNo incidentsToday
Taxonomy Delivery API Operational
90 days agoNo incidentsToday
Enterprise Observability Operational
90 days ago2 days with an incidentToday

EU data residency

Content Management API Operational
90 days ago2 days with an incidentToday
Content Delivery API Operational
90 days ago4 days with an incidentToday
GraphQL Content API Operational
90 days agoNo incidentsToday
Authentication Service Operational
90 days agoNo incidentsToday
Web App Operational
90 days agoNo incidentsToday
Assets CDN Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 20, 2026

Duration3 h 6 min07:22 to 10:28Insights Dashboard failing to loadPartial outage

This incident has been resolved.

Oct 12, 2026

Duration4 min18:22 to 18:27[INCIDENT] https://www.contentful.com/developers/docs/ is not workingPartial outage

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

Oct 1, 2026

Duration24 h 16 min09:27 to 09:43Issues with advanced caching on Content Delivery APIPartial outage

This issue has been resolved.

Sep 29, 2026

Duration1 h 5 min14:39 to 15:44CORS errors on CDAPartial outage

The issue has been resolved.

Sep 11, 2026

Duration2 h 11 min15:46 to 17:57Cross-space content missing from CDA responses for some customersDegraded

The issue has been resolved.

Sep 3, 2026

Duration5 h 40 min07:45 to 13:25Stale entries on Content Delivery APIDegraded

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.

Aug 27, 2026

Duration13 h 24 min16:26 to 05:50Daily audit logs outageDegraded

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

Aug 24, 2026

Duration9 h 25 min12:12 to 21:37Issues with Space Add-onsDegraded

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

Aug 17, 2026

Duration2 h 52 min09:05 to 11:56Experience API experiencing issues on upsert operationsDegraded

The incident is resolved

Aug 13, 2026

Duration2 h 4 min09:34 to 11:38Errors on Content Management APIPartial outage

The issue has been addressed.

Aug 10, 2026

Duration3 h 6 min11:08 to 14:14Increased latency and error rates for SnapshotsDegraded

This incident has been resolved.

Follow Contentful

Your coding agent knows when Contentful is down, and tells you when a failure is theirs, not yours. You can also get Contentful incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "contentful" and tell me if Contentful has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=contentful
Slack
/feed subscribe https://outages.cc/feed.xml?providers=contentful

Go from tracking outages to fixing production issues with Polylane.

Try Polylane