DatoCMS incident

Increase in error rate and response time

Minor Resolved View vendor source →

DatoCMS experienced a minor incident on February 23, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 23, 2026, 02:50 PM UTC
Resolved
Feb 23, 2026, 02:50 PM UTC
Duration
Detected by Pingoru
Feb 23, 2026, 02:50 PM UTC

Update timeline

  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.

Looking to track DatoCMS downtime and outages?

Pingoru polls DatoCMS's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when DatoCMS reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track DatoCMS alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring DatoCMS for free

5 free monitors · No credit card required