DatoCMS incident

2025-07-15: Performance degradation

Major Resolved View vendor source →

DatoCMS experienced a major incident on July 15, 2025, lasting 2d 16h. The incident has been resolved; the full update timeline is below.

Started
Jul 15, 2025, 12:00 AM UTC
Resolved
Jul 17, 2025, 04:54 PM UTC
Duration
2d 16h
Detected by Pingoru
Jul 15, 2025, 12:00 AM UTC

Update timeline

  1. resolved Jul 15, 2025, 12:00 AM UTC

    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 [email protected] if you are still experiencing any performance issues.

  2. resolved Jul 17, 2025, 04: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 [email protected] if you are still experiencing any performance issues.

  3. resolved Jul 17, 2025, 04:54 PM UTC

    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!