2025-07-15: Performance degradation

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-07-17 16:54 UTC and 2025-07-17 16:54 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. resolvedJul 17, 2025, 4:54 PM UTC

   Resolved — The developers traced the issue to an auto-scaling issue in a part of our infrastructure, where a cluster wasn't properly adding more resources as quickly as needed in order to keep up performance under load. We've since tweaked the scaling configuration and it should not happen again. Our apologies for the slowdown! Resolved — Several customers reported intermittent API performance degradation starting from about 1530 UTC (1730 CEST, 8:30am PST) lasting about an hour. Performance appears to be restored now, but we will continue to monitor the situation and investigate the underlying cause. Please email support@datocms.com if you are still experiencing any performance issues.

   provider

Corrections

None so far.

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