DatoCMS: Problems while accessing DatoCMS projects and performing API calls

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 2022-08-24 03:36 UTC and 2022-08-24 03:36 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.

resolvedAug 24, 2022, 3:36 AM UTC
Resolved — The upstream provider maked the incident as resolved. Monitoring — This should be fixed now. Upstream provider did not update their status page yet though Identified — The upstream provider is working on a fix Identified — It is confirmed that there is an issue with the upstream DNS provider (Heroku). We will update this page as soon as we have news. Cached graphql queries should not be affected by this down. Investigating — We are still investigating. It seems like an issue with an upstream DNS provider ( https://status.heroku.com/incidents/2453 ) Investigating — We are currently investigating a problem while accessing DatoCMS projects and performing API calls to our CMA / CDA.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is DatoCMS still down?

No, this incident was resolved 2022-08-24 03:36 UTC. For DatoCMS's live state, see https://down.guide/datocms.

How long did it last?

0m, from 2022-08-24 03:36 UTC to 2022-08-24 03:36 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.