DatoCMS incident
Problems while accessing DatoCMS projects and performing API calls
DatoCMS experienced a major incident on August 23, 2022, lasting 1d 3h. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Aug 23, 2022, 12:00 AM UTC
We are currently investigating a problem while accessing DatoCMS projects and performing API calls to our CMA / CDA.
- investigating Aug 23, 2022, 12:00 AM UTC
We are still investigating. It seems like an issue with an upstream DNS provider ( https://status.heroku.com/incidents/2453 )
- identified Aug 23, 2022, 12:00 AM UTC
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.
- identified Aug 23, 2022, 12:00 AM UTC
The upstream provider is working on a fix
- monitoring Aug 23, 2022, 12:00 AM UTC
This should be fixed now. Upstream provider did not update their status page yet though
- resolved Aug 24, 2022, 03: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.
- resolved Aug 24, 2022, 03:36 AM UTC
The upstream provider maked the incident as resolved.