Skip to main content
DatoCMS

Increased error rates

Partial outage Lasted 0m · started · DatoCMS's page

Level
confirmed
Worst impact
Partial outage
Down Index
28of 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 2025-08-26 14:16 UTC and 2025-08-26 14:16 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

  1. resolved

    Resolved — Monitoring completed Monitoring — Between 07:18 UTC and 07:28 UTC a faulty deploy caused degraded performance on our infrastructure. Customers might have noticed increased error rates when trying to access the admin interface, CMA (REST API) and CDA (graphql API). We reverted the deploy and we are monitoring the situation

    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-15ee2dcef0

Is DatoCMS still down?

No, this incident was resolved 2025-08-26 14:16 UTC. For DatoCMS's live state, see https://down.guide/datocms.

How long did it last?

0m, from 2025-08-26 14:16 UTC to 2025-08-26 14:16 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.