Daily audit logs outage
The issue is resolved and audit logs are delivered as expected again.
The latest update from Contentful.
State
Resolved
Started
66 d ago
2026-08-27 16:26 UTC
Lasted
13 h 24 min
until 2026-08-28 05:50 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
3 min 0%
Identified
13 h 21 min 100%
Updates
Times in UTCAs posted by Contentful
The issue is resolved and audit logs are delivered as expected again.
We've identified the issue and are working to resolve the daily audit logs for today, we've also confirmed that EU is unaffected.
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.
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
4.3× 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.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.
https://outages.cc/feed.xml?providers=contentful/feed subscribe https://outages.cc/feed.xml?providers=contentfulFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane