Increased latency and error rates for Snapshots
This incident has been resolved.
The latest update from Contentful.
State
Resolved
Started
84 d ago
2026-08-10 11:08 UTC
Lasted
3 h 6 min
until 2026-08-10 14:14 UTC
Worst impact
Degraded
Timeline
4 updatesIdentified
2 h 47 min 90%
Monitoring
19 min 10%
Updates
Times in UTCAs posted by Contentful
This incident has been resolved.
We've addressed the issue and are monitoring the situation.
Snapshot creation remains impacted. We continue to work on resolving the issue.
Some customers are experiencing increased latency and errors when working with Snapshots. We are working on a resolution.
Affected components
2Contentful in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
13
Median duration
3 h 6 min
This incident
About the median
Other Contentful incidents
All incidentsContentful·Insights Dashboard failing to load
This incident has been resolved.
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.
Contentful·Issues with advanced caching on Content Delivery API
This issue has been resolved.
Contentful·CORS errors on CDA
The issue has been resolved.
Contentful·Cross-space content missing from CDA responses for some customers
The issue 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.
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.live/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.
https://outages.live/feed.xml?providers=contentful/feed subscribe https://outages.live/feed.xml?providers=contentfulFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane