- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Contentful. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 28m it lasted.
Anything that failed between 2026-05-05 13:13 UTC and 2026-05-05 14:41 UTC may need a replay.Subscribe to Contentful's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=contentful works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Contentful 2
- identified
Due to an internal change in data permissions, some audit logging data was not delivered to customers between April 30 and May 4. The pipeline has since recovered, and today’s logs are being delivered as expected. We are now working to restore the missing logs from the past few days.
provider
- resolved
We've recovered the logs for all customers for the affected dates and these have been sent through to customer storage.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-7229cdf3a2
Is Contentful still down?
No, this incident was resolved 2026-05-05 14:41 UTC. For Contentful's live state, see https://down.guide/contentful.
How long did it last?
1h 28m, from 2026-05-05 13:13 UTC to 2026-05-05 14:41 UTC, by the times Contentful posted.
What caused it?
Contentful hasn't published a root cause. If it does, it shows here.
Where does this come from?
Contentful's official status page, https://www.contentfulstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.