Dash0 Outage History

Status: Resolved The issue has been resolved. We continue to monitor the system to ensure quality of service. Affected components AWS - Ireland (eu-west-1) (Operational) GCP - Netherlands (europe-west4) (Operational) AWS - Frankfurt (eu-central-1) (Operational) AWS - Oregon (us-west-2) (Operational)

Status: Resolved Between yesterday 10:00 PM and this morning 8:00 AM we were experiencing issues in our alert processing pipeline, leading to a subset of alerts being delayed or dropped in our eu-west-1 and us-west-2 regions. We have identified the issues and are already implementing measures to avoid that failure case in the future. Affected components Website - dash0.com (Operational) AWS - Oregon (us-west-2) (Operational) Frontend - app.dash0.com (Operational) Melbourne (AU) (Operational) Oregon (US) (Operational) Brussels (BE) (Operational) Frankfurt (DE) (Operational) Control Plane (Operational) AWS - Ireland (eu-west-1) (Operational) GCP - Netherlands (europe-west4) (Operational) AWS - Frankfurt (eu-central-1) (Operational) London (UK) (Operational) North Virginia (US) (Operational)

Status: Resolved We have not seen any issues since the last update and are closing the incident. Impact on new logins was observed from 10:54 AM to 11:14 AM CET. Active sessions remained unaffected. Affected components Frontend - app.dash0.com (Operational)

Status: Resolved Issue has been resolved Affected components AWS - Oregon (us-west-2) (Operational)

Status: Resolved We have not seen any any further issues and are closing the incident Affected components Frontend - app.dash0.com (Operational)

Status: Resolved We are resolving the incident as all systems have remained healthy since the last update Affected components Frontend - app.dash0.com (Operational)

Status: Resolved Duration: February 19, 2026, 4:11 PM – 5:43 PM UTC (~1 hour 32 minutes) Impact: Login to Dash0 was intermittently unavailable. Authenticated users may have experienced degraded performance due to auth token verification failures. Summary: Between 4:11 PM and 5:43 PM UTC, Dash0 users were unable to reliably log in or maintain authenticated sessions. The issue was caused by degraded performance at our authentication provider, who experienced elevated latency across their core services including session management and user authentication Our auth provider deployed a fix and confirmed stable operations on their end. The last authentication errors in our system occurred at 5:43 PM UTC, after which all Dash0 services returned to normal operation. Data ingestion and the data processing pipeline were not impacted by this incident. All telemetry data (metrics, traces, and logs) continued to be collected and processed without interruption throughout the incident. Affected components Frontend - app.dash0.com (Operational)