DatoCMS Outage History

Started Sep 27, 2026, 12:00 AM UTC· resolved Sep 30, 2026, 04:43 PM UTC

1. investigating Sep 27, 2026, 12:00 AM UTC

   We are currently investigating an issue with our email delivery service. At the moment, our platform is unable to send emails to customers. This affects all system-generated emails, including account verification emails and invitations to collaborate on projects. Until the issue is resolved, these emails will not be delivered. We will post an update as soon as we have more information. We apologize for the inconvenience.

2. identified Sep 27, 2026, 12:00 AM UTC

   Email delivery has resumed and should be working again. We are investigating whether we can add further safeguards to prevent re-occurrence.

3. monitoring Sep 27, 2026, 10:51 AM UTC

   Investigating — We are currently investigating an issue with our email delivery service. At the moment, our platform is unable to send emails to customers. This affects all system-generated emails, including account verification emails and invitations to collaborate on projects. Until the issue is resolved, these emails will not be delivered. We will post an update as soon as we have more information. We apologize for the inconvenience.

4. resolved Sep 30, 2026, 04:43 PM UTC

   The issue has been resolved.

Read the full incident report →

Started Sep 01, 2026, 12:00 AM UTC· resolved Sep 02, 2026, 01:11 PM UTC

1. resolved Sep 01, 2026, 12:00 AM UTC

   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

2. investigating Sep 01, 2026, 12:00 AM UTC

   Separate from the Imgix outage, our status page (this current page) is not correctly showing our upstream provider statuses. We are investigating.

3. resolved Sep 01, 2026, 10:01 PM UTC

   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

4. resolved Sep 02, 2026, 01:11 PM UTC

   This is now resolved. A date handling bug was hiding the Third-Party Components section whenever a provider had an ongoing incident, and several of the provider feeds we relied on had been discontinued upstream. Both are fixed, and the section now reads each provider's status API directly.

Read the full incident report →

Started Aug 10, 2026, 12:00 AM UTC· resolved Aug 17, 2026, 08:20 AM UTC

1. monitoring Aug 10, 2026, 12:00 AM UTC

   Starting from August 9th at 16:00 UTC, our platform was unable to send emails to customers. This affected all system-generated emails, including account verification and billing notifications. Email delivery was restored today, August 10th, at around 14:30 UTC, and emails are now being sent normally. No emails have been lost: messages generated during this period have been queued and are being delivered. We are monitoring the situation and we apologize for the inconvenience.

2. monitoring Aug 10, 2026, 02:35 PM UTC

   Monitoring — Starting from August 9th at 16:00 UTC, our platform was unable to send emails to customers. This affected all system-generated emails, including account verification and billing notifications. Email delivery was restored today, August 10th, at around 14:30 UTC, and emails are now being sent normally. No emails have been lost: messages generated during this period have been queued and are being delivered. We are monitoring the situation and we apologize for the inconvenience.

3. resolved Aug 17, 2026, 08:20 AM UTC

   The issue has been resolved.

Read the full incident report →

Started Feb 23, 2026, 02:50 PM UTC· resolved Feb 23, 2026, 02:50 PM UTC

1. resolved Feb 23, 2026, 02:50 PM UTC

   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.

2. resolved Feb 23, 2026, 02:50 PM UTC

   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.

Read the full incident report →

Started Feb 18, 2026, 12:00 AM UTC· resolved Feb 18, 2026, 07:25 PM UTC

1. monitoring Feb 18, 2026, 12:00 AM UTC

   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.

2. resolved Feb 18, 2026, 07:25 PM UTC

   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.

3. resolved Feb 18, 2026, 07:25 PM UTC

   Closing this.

Read the full incident report →

Started Jan 13, 2026, 12:00 AM UTC· resolved Jan 13, 2026, 08:25 AM UTC

1. investigating Jan 13, 2026, 12:00 AM UTC

   We’re currently investigating an issue affecting the ability to upload new assets to DatoCMS. The issue impacts Cloudflare R2 buckets in the EU jurisdiction, which is the default storage configuration. Uploads to custom storage solutions are working as expected, indicating the problem is specific to Cloudflare R2 in the EU region. Our team is actively investigating the root cause and working with the relevant providers to restore full functionality as quickly as possible. We will share further updates as soon as we have more information.

2. monitoring Jan 13, 2026, 12:00 AM UTC

   The issue affecting uploads to DatoCMS using Cloudflare R2 in the EU region appears to be resolved at this time. Uploads are currently working as expected, including on the default Cloudflare R2 (EU) storage. We are continuing to monitor the situation closely to ensure stability.

3. resolved Jan 13, 2026, 08:25 AM UTC

   Resolved — All issues affecting uploads to DatoCMS using Cloudflare R2 in the EU region have now been fully resolved. Uploads are operating normally again across the default EU R2 storage as well as custom storage configurations. We are no longer seeing errors related to this incident. Monitoring — The issue affecting uploads to DatoCMS using Cloudflare R2 in the EU region appears to be resolved at this time. Uploads are currently working as expected, including on the default Cloudflare R2 (EU) storage. We are continuing to monitor the situation closely to ensure stability. Investigating — We’re currently investigating an issue affecting the ability to upload new assets to DatoCMS. The issue impacts Cloudflare R2 buckets in the EU jurisdiction, which is the default storage configuration. Uploads to custom storage solutions are working as expected, indicating the problem is specific to Cloudflare R2 in the EU region. Our team is actively investigating the root cause and working with the relevant providers to restore full functionality as quickly as possible. We will share further updates as soon as we have more information.

4. resolved Jan 13, 2026, 08:25 AM UTC

   All issues affecting uploads to DatoCMS using Cloudflare R2 in the EU region have now been fully resolved. Uploads are operating normally again across the default EU R2 storage as well as custom storage configurations. We are no longer seeing errors related to this incident.

Read the full incident report →

Started Jan 13, 2026, 12:00 AM UTC· resolved Jan 20, 2026, 11:40 AM UTC

1. monitoring Jan 13, 2026, 12:00 AM UTC

   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.

2. resolved Jan 20, 2026, 11:40 AM UTC

   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.

3. resolved Jan 20, 2026, 11:40 AM UTC

   Closing the pinned alert on status

Read the full incident report →

Started Dec 03, 2025, 12:00 AM UTC· resolved Dec 03, 2025, 11:44 AM UTC

1. resolved Dec 03, 2025, 11:44 AM UTC

   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.

2. resolved Dec 03, 2025, 11:44 AM UTC

   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.

Read the full incident report →

Started Nov 18, 2025, 12:00 AM UTC· resolved Nov 19, 2025, 08:36 AM UTC

1. investigating Nov 18, 2025, 12:00 AM UTC

   We are currently experiencing degraded performance caused by an ongoing Cloudflare incident. Due to issues within Cloudflare’s infrastructure, a percentage of API requests are not being properly routed to our servers. This may result in intermittent errors or failed requests for some customers. Our systems remain fully operational, and we are actively monitoring the situation while Cloudflare works to resolve the upstream problem. We will provide updates as soon as more information becomes available. More info on: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

2. investigating Nov 18, 2025, 12:00 AM UTC

   The Cloudflare outage has escalated, and is now causing service disruptions across DatoCMS. We are experiencing outages with: DatoCMS APIs (CDA and CMA) datocms-assets.com The dashboard and admin area The community forum The status page uptime indicators are stuck at "loading" Our Slack remains available: https://join.slack.com/t/datocms/shared_invite/zt-3j142172p-nou_g2g5vUAPL6cjOOz5zQ We will update as soon as we can.

3. monitoring Nov 18, 2025, 12:00 AM UTC

   Services are gradually coming back up, but we don't know yet if this is a stable fix or if there will be further downtime. APIs, datocms-assets.com, dashboard, project admin area, and forum are back up for the time being. EDIT: As of 14:42 UTC, Cloudflare believes services are restored: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7. We will keep monitoring to be sure. Please keep an eye here for further updates, join our Slack (https://join.slack.com/t/datocms/shared_invite/zt-3j142172p-nou_g2g5vUAPL6cjOOz5zQ), or reach out to us at [email protected] if you need help.

4. monitoring Nov 18, 2025, 12:00 AM UTC

   As of 14:42 UTC (15:42 CEST/06:42 PST), Cloudflare believes the issue to be resolved. All DatoCMS services should be back up. We will continue to monitor, just in case. If you need help, please email [email protected].

5. resolved Nov 18, 2025, 12:00 AM UTC

   The outage should be resolved.

6. resolved Nov 19, 2025, 08:36 AM UTC

   Resolved — Post-mortem by Cloudflare: https://blog.cloudflare.com/18-november-2025-outage/ Resolved — The outage should be resolved. Monitoring — As of 14:42 UTC (15:42 CEST/06:42 PST), Cloudflare believes the issue to be resolved. All DatoCMS services should be back up. We will continue to monitor, just in case. If you need help, please email [email protected]. Monitoring — Services are gradually coming back up, but we don't know yet if this is a stable fix or if there will be further downtime. APIs, datocms-assets.com, dashboard, project admin area, and forum are back up for the time being. EDIT: As of 14:42 UTC, Cloudflare believes services are restored: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7. We will keep monitoring to be sure. Please keep an eye here for further updates, join our Slack (https://join.slack.com/t/datocms/shared_invite/zt-3j142172p-nou_g2g5vUAPL6cjOOz5zQ), or reach out to us at [email protected] if you need help. Investigating — The Cloudflare outage has escalated, and is now causing service disruptions across DatoCMS. We are experiencing outages with: DatoCMS APIs (CDA and CMA) datocms-assets.com The dashboard and admin area The community forum The status page uptime indicators are stuck at "loading" Our Slack remains available: https://join.slack.com/t/datocms/shared_invite/zt-3j142172p-nou_g2g5vUAPL6cjOOz5zQ We will update as soon as we can. Investigating — We are currently experiencing degraded performance caused by an ongoing Cloudflare incident. Due to issues within Cloudflare’s infrastructure, a percentage of API requests are not being properly routed to our servers. This may result in intermittent errors or failed requests for some customers. Our systems remain fully operational, and we are actively monitoring the situation while Cloudflare works to resolve the upstream problem. We will provide updates as soon as more information becomes available. More info on: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

7. resolved Nov 19, 2025, 08:36 AM UTC

   Post-mortem by Cloudflare: https://blog.cloudflare.com/18-november-2025-outage/

Read the full incident report →

Started Aug 30, 2025, 10:31 AM UTC· resolved Aug 30, 2025, 10:31 AM UTC

1. resolved Aug 30, 2025, 10:31 AM UTC

   Completed — All systems are nominal Verifying — Maintenance has been completed successfully. Read-only mode has been disabled. All operations have returned to normal. We are monitoring the system. In case of problems, please contact support. In progress — Maintenance has begun. The platform is now in read-only mode. All write operations will return a 503 error with code "PLATFORM_SCHEDULED_MAINTENANCE" Calls to graphql.datocms.com continue to work correctly without interruptions. There may be brief periods of time when the platform will stop responding to all requests, even read-only ones. In this scenario, calls to graphql.datocms.com already cached in our CDN will continue to work anyway. We will continue to update the status page as soon as we have updates. Scheduled — Maintenance is about to start Scheduled — We are going to perform an important system upgrade. 📅 Timeline: Full maintenance window begins: August 30th, 2025 05:50 UTC Full maintenance window expected duration: 2 hours ⚠️ Service Restrictions (Starting 05:50 UTC): Consider that for the full 2h window the system will be read-only There is going to be a limited-time window in which the system might be completely down. We will provide more status updates during the maintenance window. Thank you for your understanding.

Read the full incident report →

Started Aug 26, 2025, 12:00 AM UTC· resolved Aug 26, 2025, 02:16 PM UTC

1. monitoring Aug 26, 2025, 12:00 AM UTC

   Between 07:18 UTC and 07:28 UTC a faulty deploy caused degraded performance on our infrastructure. Customers might have noticed increased error rates when trying to access the admin interface, CMA (REST API) and CDA (graphql API). We reverted the deploy and we are monitoring the situation

2. resolved Aug 26, 2025, 02:16 PM UTC

   Resolved — Monitoring completed Monitoring — Between 07:18 UTC and 07:28 UTC a faulty deploy caused degraded performance on our infrastructure. Customers might have noticed increased error rates when trying to access the admin interface, CMA (REST API) and CDA (graphql API). We reverted the deploy and we are monitoring the situation

3. resolved Aug 26, 2025, 02:16 PM UTC

   Monitoring completed

Read the full incident report →

Started Aug 05, 2025, 12:00 AM UTC· resolved Aug 05, 2025, 12:28 PM UTC

1. resolved Aug 05, 2025, 12:28 PM UTC

   Resolved — On August 4th, 2025, starting from 14:00 UTC, some customers reported issues building their Gatsby projects that use our gatsby-source-datocms plugin due to records being missing from their GraphQL responses, despite being present in the CMS admin area. The issue was related to a recent change in our code that caused pagination issues with the records fetched by our gatsby-source-datocms plugin. This prevented some records from being visible in the Gatsby GraphQL responses. A rollback of that change was deployed on August 5th at 7:15 UTC. A regression test has been added to ensure that this particular issue with pagination won't happen again.

2. resolved Aug 05, 2025, 12:28 PM UTC

   On August 4th, 2025, starting from 14:00 UTC, some customers reported issues building their Gatsby projects that use our gatsby-source-datocms plugin due to records being missing from their GraphQL responses, despite being present in the CMS admin area. The issue was related to a recent change in our code that caused pagination issues with the records fetched by our gatsby-source-datocms plugin. This prevented some records from being visible in the Gatsby GraphQL responses. A rollback of that change was deployed on August 5th at 7:15 UTC. A regression test has been added to ensure that this particular issue with pagination won't happen again.

Read the full incident report →

Started Jul 15, 2025, 12:00 AM UTC· resolved Jul 17, 2025, 04:54 PM UTC

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!

Read the full incident report →

Started Jun 12, 2025, 12:00 AM UTC· resolved Jun 12, 2025, 09:58 PM UTC

1. monitoring Jun 12, 2025, 12:00 AM UTC

   On 2025-06-12, both Cloudflare and Google Cloud started having broad outages: https://www.cloudflarestatus.com/incidents/25r9t0vz99rp https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW This is in turn impacting the availability and performance of some of our services, both in the CMS and the API. It doesn't seem like a full outage yet, but general slowdowns so far. These are in turn also affecting our image CDN: https://status.imgix.com/incidents/ww7rgnbpkqg7 And our videos CDN: https://status.mux.com/incidents/8l2vdkxgs0pp This is an evolving situation and we'll post updates as we can. It is extremely uncommon for major different internet providers to have simultaneous broad outages like this... we are not sure what is going on either, but we will try to post any information we get.

2. resolved Jun 12, 2025, 09:58 PM UTC

   Resolved — The incidents should be resolved. Monitoring — On 2025-06-12, both Cloudflare and Google Cloud started having broad outages: https://www.cloudflarestatus.com/incidents/25r9t0vz99rp https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW This is in turn impacting the availability and performance of some of our services, both in the CMS and the API. It doesn't seem like a full outage yet, but general slowdowns so far. These are in turn also affecting our image CDN: https://status.imgix.com/incidents/ww7rgnbpkqg7 And our videos CDN: https://status.mux.com/incidents/8l2vdkxgs0pp This is an evolving situation and we'll post updates as we can. It is extremely uncommon for major different internet providers to have simultaneous broad outages like this... we are not sure what is going on either, but we will try to post any information we get.

3. resolved Jun 12, 2025, 09:58 PM UTC

   The incidents should be resolved.

Read the full incident report →

Started Jun 07, 2025, 01:07 PM UTC· resolved Jun 07, 2025, 01:07 PM UTC

1. resolved Jun 07, 2025, 01:07 PM UTC

   Completed — The scheduled maintenance has been completed and all services are fully operational. Verifying — Maintenance has been completed successfully. Read-only mode has been disabled. All operations have returned to normal. We are monitoring the system. In case of problems, please contact support. In progress — Maintenance has begun. The platform is now in read-only mode. All write operations will return a 503 error with code "PLATFORM_SCHEDULED_MAINTENANCE" Calls to graphql.datocms.com continue to work correctly without interruptions. There may be brief periods of time when the platform will stop responding to all requests, even read-only ones. In this scenario, calls to graphql.datocms.com already cached in our CDN will continue to work anyway. We will continue to update the status page as soon as we have updates. Scheduled — We are going to perform an important system upgrade. 📅 Timeline: Full maintenance window begins: June 7, 2025 04:00 UTC Full maintenance window expected duration: 4 hours ⚠️ Service Restrictions (Starting 04:00 UTC): Consider that for the full 4h window the system will be read-only There is going to be a limited-time window in which the system might be completely down. We will provide more status updates during the maintenance window. Thank you for your understanding.

Read the full incident report →

Started Apr 09, 2025, 12:00 AM UTC· resolved Apr 09, 2025, 10:17 AM UTC

1. monitoring Apr 09, 2025, 12:00 AM UTC

   Our services experienced increased response times for 12 minutes between 4:25 CEST and 4:37 CEST today. The issue was promptly identified and resolved by our engineering team. Please note that the status page graphs incorrectly show a +50-minute degradation period due to a misconfiguration in our reporting system. This does not reflect the actual duration of the incident. The reporting system has been corrected. All services are now operating normally with regular response times.

2. resolved Apr 09, 2025, 10:17 AM UTC

   Resolved — Postmortem: we made some changes in our Cloudflare configuration to enable a higher cache hit ratio. We relied on the fact that Cloudflare explicitly states that they support URLs up to 16KB long: https://developers.cloudflare.com/workers/platform/limits/#request-limits Turns out it's not true: we asked for more info from Cloudflare; in the meantime, we reverted our optimization. Monitoring — Our services experienced increased response times for 12 minutes between 4:25 CEST and 4:37 CEST today. The issue was promptly identified and resolved by our engineering team. Please note that the status page graphs incorrectly show a +50-minute degradation period due to a misconfiguration in our reporting system. This does not reflect the actual duration of the incident. The reporting system has been corrected. All services are now operating normally with regular response times.

3. resolved Apr 09, 2025, 10:17 AM UTC

   Postmortem: we made some changes in our Cloudflare configuration to enable a higher cache hit ratio. We relied on the fact that Cloudflare explicitly states that they support URLs up to 16KB long: https://developers.cloudflare.com/workers/platform/limits/#request-limits Turns out it's not true: we asked for more info from Cloudflare; in the meantime, we reverted our optimization.

Read the full incident report →

Started Mar 19, 2025, 12:00 AM UTC· resolved Mar 20, 2025, 03:22 AM UTC

1. investigating Mar 19, 2025, 12:00 AM UTC

   PDFs served from datocms-assets.com are currently showing up as image thumbnails rather than PDF files for Chromium-based browsers (Chrome and Edge). Firefox and Safari are not affected. A current workaround is to append ?skip-default-optimizations to the end of the URL, like: https://www.datocms-assets.com/123456/123456789-your-file.pdf?skip-default-optimizations That should allow the PDF to load normally. We are working on a permanent resolution and will update here as soon as we can.

2. resolved Mar 20, 2025, 03:22 AM UTC

   Resolved — The issue has been resolved. Investigating — PDFs served from datocms-assets.com are currently showing up as image thumbnails rather than PDF files for Chromium-based browsers (Chrome and Edge). Firefox and Safari are not affected. A current workaround is to append ?skip-default-optimizations to the end of the URL, like: https://www.datocms-assets.com/123456/123456789-your-file.pdf?skip-default-optimizations That should allow the PDF to load normally. We are working on a permanent resolution and will update here as soon as we can.

3. resolved Mar 20, 2025, 03:22 AM UTC

   The issue has been resolved.

Read the full incident report →

Started Feb 03, 2025, 12:00 AM UTC· resolved Feb 05, 2025, 09:14 PM UTC

1. investigating Feb 03, 2025, 12:00 AM UTC

   We’ve received and confirmed some reports about the login page (https://dashboard.datocms.com/login) not working, resulting in a hanged browser window. We are trying to find a fix. The problem seems to be intermittent and related to how we handle some third-party network issues. The best temporary workaround seems to be to block posthog.com in your adblocker (if you have one) or browser inspector or system hosts file. If you can’t do that, sometimes forcibly reloading the page (you might have to close the whole browser and try again) several times in a row will work. The issue seems to be intermittent. Our APIs do not seem to be affected. Your websites should continue to work. Devs have been notified and we’ll update as soon as we can.

2. monitoring Feb 03, 2025, 12:00 AM UTC

   Login should be working now after the latest hotfix. Please close your browser and try again. We've temporarily disabled a problematic script that was causing this, and will roll out a full fix as soon as we can. We don't expect any additional downtime from the fix.

3. resolved Feb 03, 2025, 12:00 AM UTC

   This issue should be resolved.

4. identified Feb 03, 2025, 12:00 AM UTC

   The issue has resurfaced and the login page is having issues again. We are working on it. Sorry! Our APIs are not affected.

5. identified Feb 03, 2025, 12:00 AM UTC

   The issue is intermittent, and the login is working again for the time being. We are working with our third-party partner to resolve the underlying issue.

6. resolved Feb 05, 2025, 09:14 PM UTC

   Resolved — We've hotfixed the issue again for now. Sincerely apologize for the regression. We'll be more careful next time. Identified — The issue is intermittent, and the login is working again for the time being. We are working with our third-party partner to resolve the underlying issue. Identified — The issue has resurfaced and the login page is having issues again. We are working on it. Sorry! Our APIs are not affected. Resolved — This issue should be resolved. Monitoring — Login should be working now after the latest hotfix. Please close your browser and try again. We've temporarily disabled a problematic script that was causing this, and will roll out a full fix as soon as we can. We don't expect any additional downtime from the fix. Investigating — We’ve received and confirmed some reports about the login page (https://dashboard.datocms.com/login) not working, resulting in a hanged browser window. We are trying to find a fix. The problem seems to be intermittent and related to how we handle some third-party network issues. The best temporary workaround seems to be to block posthog.com in your adblocker (if you have one) or browser inspector or system hosts file. If you can’t do that, sometimes forcibly reloading the page (you might have to close the whole browser and try again) several times in a row will work. The issue seems to be intermittent. Our APIs do not seem to be affected. Your websites should continue to work. Devs have been notified and we’ll update as soon as we can.

7. resolved Feb 05, 2025, 09:14 PM UTC

   We've hotfixed the issue again for now. Sincerely apologize for the regression. We'll be more careful next time.

Read the full incident report →

Started Jan 26, 2025, 04:49 PM UTC· resolved Jan 26, 2025, 04:49 PM UTC

1. resolved Jan 26, 2025, 04:49 PM UTC

   Completed — The monitoring phase has ended Verifying — Maintenance is completed. The environments are now in write mode. We are monitoring the situation. In progress — The required downtime is over. Now the environments will be in read-only mode for the rest of the maintenance window. In progress — Maintenance is starting now. In progress — Pre maintenance restrictions now apply The following operations will return 403 errors throughout the maintenance period: Creating sandbox environments Destroying sandbox environments Project duplication Project deletion Scheduled — 🔄 Based on your feedback, we have revised our maintenance approach to minimize service disruption Key Changes: Reduced downtime: system will only be offline for the first 10 minutes (starting at 09:00 UTC) After the initial 10-minute downtime, services will be available in read-only mode for the remaining 50 minutes Total duration increased from 45 to 60 minutes Please refer to the maintenance schedule and impact sections above for complete details. Thank you for your understanding. Scheduled — We will be performing critical database maintenance that will affect our services. 📅 Timeline: Pre-maintenance restrictions begin: January 26, 2025 08:45 UTC Full maintenance window begins: January 26, 2025 09:00 UTC Full maintenance window expected duration: 60 minutes ⚠️ Service Restrictions (Starting 08:45 UTC): The following operations will return 403 errors throughout the maintenance period: Creating sandbox environments Destroying sandbox environments Project duplication Project deletion ⚠️ Full Maintenance Impact (Starting 09:00 UTC): Phase 1 - System Downtime (First 10 minutes): Content Management API: Complete outage Content Delivery API: Complete outage (cached CDN requests will still work) Admin Interface: Complete outage Assets URLs: Fully functional Phase 2 - Restricted Access (Remaining duration): The system will return online with all environments in maintenance mode: Read operations: Fully functional Write operations: Temporarily disabled, returning 403 errors for operations including content updates, schema changes, upload management, all other write operations on environments. We will provide more status updates during the maintenance window. Thank you for your understanding.

Read the full incident report →

Started Nov 07, 2024, 12:00 AM UTC· resolved Nov 08, 2024, 08:01 AM UTC

1. monitoring Nov 07, 2024, 12:00 AM UTC

   Between 2024-11-07 12:57 UTC and 13:03 UTC customers have noticed an increase of error rates when accessing their projects admin interface, CMA endpoint and CDA endpoint. This was caused by a temporary increase of activity on one of our databases. The situation went back to normal at about 13:03 UTC and we are monitoring the situation. Cached graphql queries in our edge network were not affected by this. We are sorry for the inconvenience.

2. resolved Nov 08, 2024, 08:01 AM UTC

   Resolved — This issue can be considered resolved Monitoring — Between 2024-11-07 12:57 UTC and 13:03 UTC customers have noticed an increase of error rates when accessing their projects admin interface, CMA endpoint and CDA endpoint. This was caused by a temporary increase of activity on one of our databases. The situation went back to normal at about 13:03 UTC and we are monitoring the situation. Cached graphql queries in our edge network were not affected by this. We are sorry for the inconvenience.

3. resolved Nov 08, 2024, 08:01 AM UTC

   This issue can be considered resolved

Read the full incident report →