Dash0 Outage History

Dash0 is up right now

Dash0 had 28 outages in the last 2 years totaling 186h 35m of downtime — averaging 1.2 incidents per month.

There were 28 Dash0 outages since June 26, 2025 totaling 186h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.dash0status.com

Minor June 10, 2026

Span processing lag in eu-west-1

Detected by Pingoru
Jun 10, 2026, 05:07 PM UTC
Resolved
Jun 10, 2026, 05:07 PM UTC
Duration
Timeline · 3 updates
  1. investigating Jun 10, 2026, 03:50 PM UTC

    Status: Investigating We are investigating a lag in span processing in our eu-west-1 region. Affected components AWS - Ireland (eu-west-1) (Degraded performance)

  2. monitoring Jun 10, 2026, 04:14 PM UTC

    Status: Monitoring We have identified the problem and implemented a fix. Delayed data has been processed and processing is stable again. Affected components AWS - Ireland (eu-west-1) (Operational)

  3. resolved Jun 10, 2026, 05:07 PM UTC

    Status: Resolved Incident Resolved. All the data has been processed. Affected components AWS - Ireland (eu-west-1) (Operational)

Read the full incident report →

Minor June 10, 2026

Delayed data processing

Detected by Pingoru
Jun 10, 2026, 01:41 PM UTC
Resolved
Jun 10, 2026, 01:41 PM UTC
Duration
Timeline · 2 updates
  1. monitoring Jun 10, 2026, 01:18 PM UTC

    Status: Monitoring We have been experiencing partial delays in data processing across our data processing regions, starting 13:05 CEST. The problem has been identified and delayed data is getting processed. Affected components AWS - Oregon (us-west-2) (Degraded performance) AWS - Ireland (eu-west-1) (Degraded performance) GCP - Netherlands (europe-west4) (Degraded performance) AWS - Frankfurt (eu-central-1) (Degraded performance)

  2. resolved Jun 10, 2026, 01:41 PM UTC

    Status: Resolved All delayed data has been processed and systems are fully operational again Affected components GCP - Netherlands (europe-west4) (Operational) AWS - Frankfurt (eu-central-1) (Operational) AWS - Oregon (us-west-2) (Operational) AWS - Ireland (eu-west-1) (Operational)

Read the full incident report →

Minor May 29, 2026

Span ingestion is lagging in eu-west-1 region

Detected by Pingoru
May 29, 2026, 05:59 AM UTC
Resolved
May 29, 2026, 05:59 AM UTC
Duration
Timeline · 4 updates
  1. investigating May 29, 2026, 02:47 AM UTC

    Status: Investigating The spans ingestion is lagging in eu-west-1 region. You might experience span delayed. Affected components AWS - Ireland (eu-west-1) (Degraded performance)

  2. identified May 29, 2026, 03:16 AM UTC

    Status: Identified We have identified the root cause of the issue and have deployed a fix. Affected components AWS - Ireland (eu-west-1) (Degraded performance)

  3. monitoring May 29, 2026, 03:57 AM UTC

    Status: Monitoring All delayed spans have been processed. The service is back to normal. We are currently monitoring the system. Affected components AWS - Ireland (eu-west-1) (Operational)

  4. resolved May 29, 2026, 05:59 AM UTC

    Status: Resolved The issue has been resolved. Affected components AWS - Ireland (eu-west-1) (Operational)

Read the full incident report →

Minor April 29, 2026

Experiencing delay in data processing

Detected by Pingoru
Apr 29, 2026, 09:23 PM UTC
Resolved
Apr 29, 2026, 09:23 PM UTC
Duration
Timeline · 3 updates
  1. identified Apr 29, 2026, 08:20 PM UTC

    Status: Identified We are currently experiencing a delay in data processing starting 19:55 UTC Affected components AWS - Oregon (us-west-2) (Degraded performance) AWS - Ireland (eu-west-1) (Degraded performance) GCP - Netherlands (europe-west4) (Degraded performance) AWS - Frankfurt (eu-central-1) (Degraded performance)

  2. monitoring Apr 29, 2026, 08:46 PM UTC

    Status: Monitoring We have identified the issue and the system is recovering. Some customer might see a gap in telemetry data from 19:55 - 20:10. Affected components AWS - Frankfurt (eu-central-1) (Degraded performance) AWS - Oregon (us-west-2) (Degraded performance) AWS - Ireland (eu-west-1) (Degraded performance) GCP - Netherlands (europe-west4) (Degraded performance)

  3. resolved Apr 29, 2026, 09:23 PM UTC

    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)

Read the full incident report →

Minor April 27, 2026

Delayed and dropped alert evaluations.

Detected by Pingoru
Apr 27, 2026, 08:00 PM UTC
Resolved
Apr 27, 2026, 08:00 PM UTC
Duration
Affected: Website - dash0.comControl PlaneFrontend - app.dash0.com
Timeline · 1 update
  1. resolved Apr 27, 2026, 08:00 PM UTC

    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)

Read the full incident report →

Minor March 20, 2026

Auth Provider Issues

Detected by Pingoru
Mar 20, 2026, 11:28 AM UTC
Resolved
Mar 20, 2026, 11:28 AM UTC
Duration
Affected: Frontend - app.dash0.com
Timeline · 3 updates
  1. investigating Mar 20, 2026, 10:05 AM UTC

    Status: Investigating We are experiencing issues with our authentication provider. Those are causing new logins to fail atm. We are investigating the issues. Data processing remains unaffected. Affected components Frontend - app.dash0.com (Partial outage)

  2. monitoring Mar 20, 2026, 10:28 AM UTC

    Status: Monitoring We are seeing error rate recovery and logins are succeeding again. We'll keep monitoring the the issue. Affected components Frontend - app.dash0.com (Operational)

  3. resolved Mar 20, 2026, 11:28 AM UTC

    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)

Read the full incident report →

Minor March 17, 2026

Log processing delayed in AWS us-west-2 region

Detected by Pingoru
Mar 17, 2026, 05:30 PM UTC
Resolved
Mar 17, 2026, 05:30 PM UTC
Duration
Timeline · 4 updates
  1. investigating Mar 17, 2026, 02:50 PM UTC

    Status: Investigating Log processing is delayed in AWS us-west-2 region. We have identified the problem and are working on resolving the issue. Affected components AWS - Oregon (us-west-2) (Partial outage)

  2. monitoring Mar 17, 2026, 04:04 PM UTC

    Status: Monitoring We have implemented a fix and are monitoring the system. Logging data is automatically backfilled. Affected components AWS - Oregon (us-west-2) (Degraded performance)

  3. monitoring Mar 17, 2026, 05:15 PM UTC

    Status: Monitoring The issue has been resolved. Affected components AWS - Oregon (us-west-2) (Operational)

  4. resolved Mar 17, 2026, 05:30 PM UTC

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

Read the full incident report →

Minor March 11, 2026

Auth Provider issues

Detected by Pingoru
Mar 11, 2026, 12:55 PM UTC
Resolved
Mar 11, 2026, 12:55 PM UTC
Duration
Affected: Frontend - app.dash0.com
Timeline · 6 updates
  1. investigating Mar 10, 2026, 03:55 PM UTC

    Status: Investigating Starting at 16:55 CET we are experiencing degraded UI performance due to issues with our authentication provider. This can cause login timeouts and slow UI performance. We are monitoring the situation. Data processing remains unaffected Affected components Frontend - app.dash0.com (Degraded performance)

  2. monitoring Mar 10, 2026, 04:34 PM UTC

    Status: Monitoring The situation has stabilized again. We keep monitoring the situation carefully for another 15m before closing the incident. Affected components Frontend - app.dash0.com (Operational)

  3. resolved Mar 10, 2026, 04:56 PM UTC

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

  4. investigating Mar 11, 2026, 12:00 PM UTC

    Status: Investigating We are seeing new issues with our Auth provider and are thus re-opening this incident. Update: New Logins are currently not possible. Active sessions are not affected Affected components Frontend - app.dash0.com (Degraded performance)

  5. monitoring Mar 11, 2026, 12:17 PM UTC

    Status: Monitoring Logins are functional again Affected components Frontend - app.dash0.com (Operational)

  6. resolved Mar 11, 2026, 12:55 PM UTC

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

Read the full incident report →