outages.live
Live
ContentfulIncident · 2026-10-01 09:27 UTC

Issues with advanced caching on Content Delivery API

ResolvedOfficial update

This issue has been resolved.

The latest update from Contentful.

State

Resolved

Started

31 d ago

2026-10-01 09:27 UTC

Lasted

24 h 16 min

until 2026-10-02 09:43 UTC

Worst impact

Partial outage

Timeline

4 updates
09:2715:3121:3503:3909:43
Partial outageUpdate postedTimes in UTC

Identified

23 h 16 min 96%

Monitoring

1 h 4%

Updates

Times in UTC

As posted by Contentful

Resolved2026-10-02 09:43 UTC

This issue has been resolved.

Monitoring2026-10-02 08:43 UTC

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

Identified2026-10-01 11:29 UTC

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

Identified2026-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.

Affected components

2
Content Delivery APIEU data residency - Content Delivery API

Contentful in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

11

Days with an incident

13

Median duration

3 h 6 min

This incident

7.8× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

24 h 16 min
median 3 h 6 min
90 days agoToday

Other Contentful incidents

All incidents

Contentful·Insights Dashboard failing to load

This incident has been resolved.

Resolvedresolved 12 d ago

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

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

Resolvedresolved 20 d ago

Contentful·CORS errors on CDA

The issue has been resolved.

Resolvedresolved 33 d ago

Contentful·Cross-space content missing from CDA responses for some customers

The issue has been resolved.

Resolvedresolved 51 d ago

Contentful·Stale entries on Content Delivery API

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.

Resolvedresolved 59 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane