- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on DatoCMS. 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 2026-01-20 11:40 UTC and 2026-01-20 11:40 UTC may need a replay.Subscribe to DatoCMS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=datocms works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from DatoCMS 1
- resolved
Resolved — Closing the pinned alert on status Monitoring — A bug prevented daily bandwidth and API call metrics from being saved between January 7 and 12. The data was not lost — it has been aggregated into January 13's totals. Daily metrics will be recorded normally starting January 14. We've added regression tests to prevent this from recurring. We apologize for the inconvenience.
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-d3bd4c4661
Is DatoCMS still down?
No, this incident was resolved 2026-01-20 11:40 UTC. For DatoCMS's live state, see https://down.guide/datocms.
How long did it last?
0m, from 2026-01-20 11:40 UTC to 2026-01-20 11:40 UTC, by the times DatoCMS posted.
What caused it?
DatoCMS hasn't published a root cause. If it does, it shows here.
Where does this come from?
DatoCMS's official status page, https://status.datocms.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.