Dash0 Outage History

Dash0 is up right now

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

There were 29 Dash0 outages since August 12, 2025 totaling 29h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.dash0status.com

Minor July 29, 2026

Frontend slow or unavailable

Detected by Pingoru
Jul 29, 2026, 11:55 AM UTC
Resolved
Jul 29, 2026, 11:55 AM UTC
Duration
—
Affected: Frontend - app.dash0.com
Timeline · 4 updates
  1. investigating Jul 29, 2026, 10:43 AM UTC

    Status: Investigating We are experiencing slowness and timeouts for UI users and are already investigating the issue Affected components Frontend - app.dash0.com (Partial outage)

  2. identified Jul 29, 2026, 10:56 AM UTC

    Status: Identified We have identified the issue and are applying mitigations. The UI should be available again Affected components Frontend - app.dash0.com (Degraded performance)

  3. monitoring Jul 29, 2026, 11:23 AM UTC

    Status: Monitoring Frontend availability has been restored and we keep monitoring the situation Affected components Frontend - app.dash0.com (Operational)

  4. resolved Jul 29, 2026, 11:55 AM UTC

    Status: Resolved All services remained stable after mitigations were applied and we are closing the incident Affected components Frontend - app.dash0.com (Operational)

Read the full incident report →

Minor July 20, 2026

Transient failures in alert rule evaluations in `eu-west-1`

Detected by Pingoru
Jul 20, 2026, 09:14 PM UTC
Resolved
Jul 20, 2026, 09:14 PM UTC
Duration
—
Timeline · 3 updates
  1. monitoring Jul 20, 2026, 07:40 PM UTC

    Status: Monitoring Alert rule evaluations for customers in the eu-west-1 region may have been impacted between 19:03:45 UTC and 19:30:45 UTC. During this time, some alert rules may have been skipped, and some customers may have received "Too many simultaneous queries for user ruler" errors, depending on their rule configuration. The issue has been mitigated, and we are continuing to monitor the system to ensure normal operation.

  2. monitoring Jul 20, 2026, 08:07 PM UTC

    Status: Monitoring Alert rule evaluations for customers in the eu-west-1 region may have been impacted between 19:​03:​45 UTC and 19:​30:​45 UTC. During this time, some alert rules may have been skipped during that time. The issue has been mitigated, and we are continuing to monitor the system to ensure normal operation.

  3. resolved Jul 20, 2026, 09:14 PM UTC

    Status: Resolved Incident has been mitigated, an RCA will follow.

Read the full incident report →

Minor July 20, 2026

Alert Delivery and Evaluation is disrupted in eu-central-1

Detected by Pingoru
Jul 20, 2026, 02:31 PM UTC
Resolved
Jul 20, 2026, 02:31 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jul 20, 2026, 01:39 PM UTC

    Status: Investigating Alert Delivery and Evaluation is disrupted in eu-central-1

  2. monitoring Jul 20, 2026, 01:46 PM UTC

    Status: Monitoring Mitigation applied, we are monitoring the recovery

  3. resolved Jul 20, 2026, 02:31 PM UTC

    Status: Resolved Mitigation has been implemented, and the service is stable. We are continuing to investigate the underlying cause

Read the full incident report →

Minor July 17, 2026

Data ingestion outage - eu-west-1

Detected by Pingoru
Jul 17, 2026, 07:42 PM UTC
Resolved
Jul 17, 2026, 07:42 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Jul 17, 2026, 05:27 PM UTC

    Status: Investigating Starting 18:45 CEST we are experiencing a data ingestion outage in eu-west-1 region. We are already working on recovery. Affected components AWS - Ireland (eu-west-1) (Full outage)

  2. monitoring Jul 17, 2026, 05:51 PM UTC

    Status: Monitoring Ingestion pipeline has been stabilized and we are monitoring recovery Affected components AWS - Ireland (eu-west-1) (Degraded performance)

  3. monitoring Jul 17, 2026, 06:35 PM UTC

    Status: Monitoring All ingestion systems are operational again and we keep monitoring the situation. The root cause of the incident was malformed data that was bypassing our ingestion protection layer. This subsequently overloaded and crashed a critical shared infrastructure part, which was impacting ingestion and processing. Some data has been rejected at the edge between 18:45 and 19:27 CEST. Affected components AWS - Ireland (eu-west-1) (Operational)

  4. resolved Jul 17, 2026, 07:42 PM UTC

    Status: Resolved All system remain stable. We are resolving the incident Affected components AWS - Ireland (eu-west-1) (Operational)

Read the full incident report →

Minor July 8, 2026

Log ingest delay in us-west-2

Detected by Pingoru
Jul 08, 2026, 09:18 AM UTC
Resolved
Jul 08, 2026, 09:18 AM UTC
Duration
—
Timeline · 5 updates
  1. investigating Jul 06, 2026, 06:40 PM UTC

    Status: Investigating We are investigating delays in log ingestion in us-west-2 that started 18:35 CEST Affected components AWS - Oregon (us-west-2) (Partial outage)

  2. identified Jul 06, 2026, 07:03 PM UTC

    Status: Identified We have identified the problem and took first steps to mitigate. We are seeing log ingesting recover now Affected components AWS - Oregon (us-west-2) (Partial outage)

  3. monitoring Jul 06, 2026, 07:26 PM UTC

    Status: Monitoring Long ingestion is still recovering and catching up lag. The delay was related to a bug in Log AI. The feature has been disabled in us-west-2 until we have a full fix ready. Affected components AWS - Oregon (us-west-2) (Degraded performance)

  4. monitoring Jul 06, 2026, 08:04 PM UTC

    Status: Monitoring Log ingestion has fully recovered. Log AI remains disabled until further analysis. Affected components AWS - Oregon (us-west-2) (Operational)

  5. resolved Jul 08, 2026, 09:18 AM UTC

    Status: Resolved All outstanding fixes haven been shipped and all Log AI features are enabled again Affected components AWS - Oregon (us-west-2) (Operational)

Read the full incident report →

Minor June 25, 2026

Delay in metric processing for a subset of metrics in eu-west-1

Detected by Pingoru
Jun 25, 2026, 10:28 AM UTC
Resolved
Jun 25, 2026, 10:28 AM UTC
Duration
—
Timeline · 3 updates
  1. identified Jun 25, 2026, 08:53 AM UTC

    Status: Identified We have identified a delay in metric processing for a subset of metrics in our AWS Ireland region. We are already working on a fix Affected components AWS - Ireland (eu-west-1) (Degraded performance)

  2. monitoring Jun 25, 2026, 09:22 AM UTC

    Status: Monitoring The issue has been mitigated and we continue to monitor our systems before we fully resolve this incident Affected components AWS - Ireland (eu-west-1) (Operational)

  3. resolved Jun 25, 2026, 10:28 AM UTC

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

Read the full incident report →

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 →