DatoCMS Outage History

Investigating — Separate from the Imgix outage, our status page (this current page) is not correctly showing our upstream provider statuses. We are investigating. Resolved — Earlier today, from approximately 15:00 to 19:00 UTC, our upstream image provider (Imgix) had a partial outage that resulted in occasional rendering errors for some customers in some situations. The issue should now be resolved (see details at https://status.imgix.com/incidents/ch5p1nlqnckd and https://status.imgix.com/incidents/7n22y1mt7jw1

Resolved — A node in our production Kubernetes cluster became unresponsive, causing a brief disruption to some services while workloads were automatically rescheduled to healthy nodes. The duration of the disruption was about 8 minutes.

Resolved — Closing this. Monitoring — Starting from 8:15 AM UTC we received alerts about customers not being able to upload new assets in the media area of their project. This issue only affected uploads made from the administrative area. Uploads performed via the JavaScript client were not impacted. The issue was traced to a recent deploy. We identified and reverted the problematic changes at 9:20 AM UTC. The issue has been resolved and asset uploads are functioning normally. We apologize for the inconvenience.

Resolved — Closing the pinned alert on status Monitoring — A bug prevented daily bandwidth and API call metrics from being saved between January 7 and 12. The data was not lost — it has been aggregated into January 13's totals. Daily metrics will be recorded normally starting January 14. We've added regression tests to prevent this from recurring. We apologize for the inconvenience.

Resolved — On December 2 at 13:13 CET, our API was unavailable for 9 minutes during a deployment, causing errors when accessing the CMS interface. What happened During a routine database migration deployment, code that depended on a not-yet-created database table was accidentally included. This caused the API to fail until we identified and rolled back the changes. Prevention We're implementing stricter code review checks to ensure migration-only deployments don't include dependent code, and adding automated tests to catch this type of issue before deployment. We apologise for the disruption and appreciate your patience.

Completed — Monitoring is completed Verifying — Maintenance completed. We are monitoring the system. Scheduled — We are going to run a maintenance on our billing infrastructure starting from 2025-10-14T05:00 UTC. The expected time to finish is 2 hours. During this maintenance window you could not be able to succesfully complete some operations such as: make changes to your plan (buying a plan, upgrading / downgrading a plan, etc.) update your billing profile (address, credit cards, etc.) tranfer a project destroy an account or an organization destroy a project pay overdue amounts Automatic plan adjustments that we apply to your plan, such as adding an extra collaborator, will be executed after the maintenance.