- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2025-12-15 10:55 UTC and 2025-12-15 10:55 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 1
- resolved
Between 08:40 and 09:20 UTC customers experienced errors when trying to log in to Contentful ("Something went wrong"). This was due to a change we made to our bot protection logic. Once we saw the impact of the change, we reverted and the issue was resolved. If any customers continue to see the error after that time period, a refresh will resolve the issue.
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-304ba700b3
Is Contentful still down?
No, this incident was resolved 2025-12-15 10:55 UTC. For Contentful's live state, see https://down.guide/contentful.
How long did it last?
0m, from 2025-12-15 10:55 UTC to 2025-12-15 10:55 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.