Dash0 Outage History

Dash0 is up right now

Pingoru has recorded 28 incidents for Dash0: 27 in the last 12 months and 5 in the last 90 days.

Source: dash0status.com

28incidents recorded
27last 12 months
5last 90 days
4 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Dash0 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202621 of 720 (0%)
May 202613 of 744 (0%)
June 202633 of 720 (0%)
July 2026545 of 744 (6%)
August 202611 of 744 (0%)
September 202635 of 720 (1%)
October 202610 of 744 (0%)
November 202600 of 128 (0%)

Incidents, newest first

Major October 22, 2026 Frontend slow or not loading 11m Authentication, Frontend - app.dash0.com

Started Oct 22, 2026, 12:58 PM UTC· resolved Oct 22, 2026, 01:10 PM UTC

  1. identified Oct 22, 2026, 12:58 PM UTC

    We are currently experiencing issues with our frontend, leading to slow loads or loads timing out. We already identified the issues and are working on mitigations. Ingest and alerting is not affected.

  2. monitoring Oct 22, 2026, 01:10 PM UTC

    We deployed a fix and UI performance has recovered again. We are monitoring system health closely.

  3. monitoring Oct 22, 2026, 01:57 PM UTC

    ℹ️ While we investigate the issue, for the time being our Github integration will remain disabled, meaning Darkplane AI SDLC Insights and Agent0 Github Triggers will not work

  4. resolved Oct 22, 2026, 07:57 PM UTC

    Darkplane AI SDLC Insights and Agent0 Github Triggers are functional again.

Read the full incident report →

Minor September 17, 2026 Spans ingestion delay in AWS eu-west-1 region 2h 21m SignalStore (AWS - Ireland (eu-west-1)), Frontend - app.dash0.com

Started Sep 17, 2026, 12:21 AM UTC· resolved Sep 17, 2026, 02:42 AM UTC

  1. investigating Sep 17, 2026, 12:21 AM UTC

    We have an issue with spans ingestion pipeline in eu-west-1 region. You might see spans/traces delay. We are actively investigating right now.

  2. identified Sep 17, 2026, 01:22 AM UTC

    I have identified the cause and placed the mitigation. The spans/traces should be caught up soon.

  3. monitoring Sep 17, 2026, 02:42 AM UTC

    All spans have been caught up.

  4. resolved Sep 17, 2026, 02:43 AM UTC

    The issue has been resolved.

Read the full incident report →

Major September 8, 2026 Data ingestion issue in eu-central-1 31m SignalStore (AWS - Frankfurt (eu-central-1))

Started Sep 08, 2026, 05:41 AM UTC· resolved Sep 08, 2026, 06:12 AM UTC

  1. investigating Sep 08, 2026, 05:45 AM UTC

    There is an issue with data ingestion in eu-central-1. We are actively investigating.

  2. identified Sep 08, 2026, 06:00 AM UTC

    There was load surge around 5:40 UTC. We have scaled out our components to accommodate the load.

  3. monitoring Sep 08, 2026, 06:30 AM UTC

    The issue is mitigated. We are actively monitoring.

  4. resolved Sep 08, 2026, 07:07 AM UTC

    Ingest issues in eu-central-1 have been resolved. The problem started 5:41 UTC and was resolved around 6:12 UTC.

Read the full incident report →

Minor September 1, 2026 We are experiencing slowness for UI due to an issue with our identity provider. 2h 18m Frontend - app.dash0.com

Started Sep 01, 2026, 05:53 PM UTC· resolved Sep 01, 2026, 08:11 PM UTC

  1. monitoring Sep 01, 2026, 05:53 PM UTC

    Our identity provider is experiencing performance degradation, which is causing slowness in our UI. See https://status.clerk.com/incidents/01M1ETFWW4XQH44X1SZY7RKR8R

  2. resolved Sep 01, 2026, 08:11 PM UTC

    The Clerk is reporting as fully operational, and their latency dashboard shows that the earlier degradation has stabilized. Our validation indicates the customer impact was limited and is now resolved.

Read the full incident report →

Minor August 16, 2026 Delay in Notification Delivery in US-WEST-2 27m

Started Aug 16, 2026, 07:39 AM UTC· resolved Aug 16, 2026, 08:06 AM UTC

  1. investigating Aug 16, 2026, 07:39 AM UTC

    There might be delayed notifications for check-rules, synthetics etc

  2. resolved Aug 16, 2026, 08:06 AM UTC

    Incident has been resolved, RCA and preventive measures will follow

Read the full incident report →

Minor July 29, 2026 Frontend slow or unavailable 1h 11m Frontend - app.dash0.com

Started Jul 29, 2026, 10:43 AM UTC· resolved Jul 29, 2026, 11:55 AM UTC

  1. investigating Jul 29, 2026, 10:43 AM UTC

    We are experiencing slowness and timeouts for UI users and are already investigating the issue

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

    We have identified the issue and are applying mitigations. The UI should be available again

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

    Frontend availability has been restored and we keep monitoring the situation

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

    All services remained stable after mitigations were applied and we are closing the incident

Read the full incident report →

Minor July 20, 2026 Transient failures in alert rule evaluations in `eu-west-1` 1h 33m

Started Jul 20, 2026, 07:40 PM UTC· resolved Jul 20, 2026, 09:14 PM UTC

  1. monitoring Jul 20, 2026, 07:40 PM UTC

    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

    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

    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 52m

Started Jul 20, 2026, 01:39 PM UTC· resolved Jul 20, 2026, 02:31 PM UTC

  1. investigating Jul 20, 2026, 01:39 PM UTC

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

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

    Mitigation applied, we are monitoring the recovery

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

    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 2h 15m

Started Jul 17, 2026, 05:27 PM UTC· resolved Jul 17, 2026, 07:42 PM UTC

  1. investigating Jul 17, 2026, 05:27 PM UTC

    Starting 18:45 CEST we are experiencing a data ingestion outage in eu-west-1 region. We are already working on recovery.

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

    Ingestion pipeline has been stabilized and we are monitoring recovery

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

    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.

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

    All system remain stable. We are resolving the incident

Read the full incident report →

Minor July 6, 2026 Log ingest delay in us-west-2 1d 14h

Started Jul 06, 2026, 06:40 PM UTC· resolved Jul 08, 2026, 09:18 AM UTC

  1. investigating Jul 06, 2026, 06:40 PM UTC

    We are investigating delays in log ingestion in us-west-2 that started 18:35 CEST

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

    We have identified the problem and took first steps to mitigate. We are seeing log ingesting recover now

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

    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.

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

    Log ingestion has fully recovered. Log AI remains disabled until further analysis.

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

    All outstanding fixes haven been shipped and all Log AI features are enabled again

Read the full incident report →

Minor June 25, 2026 Delay in metric processing for a subset of metrics in eu-west-1 1h 34m

Started Jun 25, 2026, 08:53 AM UTC· resolved Jun 25, 2026, 10:28 AM UTC

  1. identified Jun 25, 2026, 08:53 AM UTC

    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

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

    The issue has been mitigated and we continue to monitor our systems before we fully resolve this incident

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

    Problem has been resolved.

Read the full incident report →

Minor June 10, 2026 Span processing lag in eu-west-1 1h 17m

Started Jun 10, 2026, 03:50 PM UTC· resolved Jun 10, 2026, 05:07 PM UTC

  1. investigating Jun 10, 2026, 03:50 PM UTC

    We are investigating a lag in span processing in our eu-west-1 region.

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

    We have identified the problem and implemented a fix. Delayed data has been processed and processing is stable again.

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

    Incident Resolved. All the data has been processed.

Read the full incident report →

Minor June 10, 2026 Delayed data processing 22m

Started Jun 10, 2026, 01:18 PM UTC· resolved Jun 10, 2026, 01:41 PM UTC

  1. monitoring Jun 10, 2026, 01:18 PM UTC

    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.

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

    All delayed data has been processed and systems are fully operational again

Read the full incident report →

Minor May 29, 2026 Span ingestion is lagging in eu-west-1 region 3h 11m

Started May 29, 2026, 02:47 AM UTC· resolved May 29, 2026, 05:59 AM UTC

  1. investigating May 29, 2026, 02:47 AM UTC

    The spans ingestion is lagging in eu-west-1 region. You might experience span delayed.

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

    We have identified the root cause of the issue and have deployed a fix.

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

    All delayed spans have been processed. The service is back to normal. We are currently monitoring the system.

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

    The issue has been resolved.

Read the full incident report →

Minor April 29, 2026 Experiencing delay in data processing 1h 3m

Started Apr 29, 2026, 08:20 PM UTC· resolved Apr 29, 2026, 09:23 PM UTC

  1. identified Apr 29, 2026, 08:20 PM UTC

    We are currently experiencing a delay in data processing starting 19:55 UTC

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

    We have identified the issue and the system is recovering. Some customer might see a gap in telemetry data from 19:55 - 20:10.

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

    The issue has been resolved. We continue to monitor the system to ensure quality of service.

Read the full incident report →

Minor April 27, 2026 Delayed and dropped alert evaluations. – Website - dash0.com, Authentication, Frontend - app.dash0.com

Started Apr 27, 2026, 08:00 PM UTC· resolved Apr 27, 2026, 08:00 PM UTC

  1. resolved Apr 27, 2026, 08:00 PM UTC

    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.

Read the full incident report →

Minor March 20, 2026 Auth Provider Issues 1h 23m Frontend - app.dash0.com

Started Mar 20, 2026, 10:05 AM UTC· resolved Mar 20, 2026, 11:28 AM UTC

  1. investigating Mar 20, 2026, 10:05 AM UTC

    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.

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

    We are seeing error rate recovery and logins are succeeding again. We'll keep monitoring the the issue.

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

    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.

Read the full incident report →

Minor March 17, 2026 Log processing delayed in AWS us-west-2 region 2h 39m

Started Mar 17, 2026, 02:50 PM UTC· resolved Mar 17, 2026, 05:30 PM UTC

  1. investigating Mar 17, 2026, 02:50 PM UTC

    Log processing is delayed in AWS us-west-2 region. We have identified the problem and are working on resolving the issue.

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

    We have implemented a fix and are monitoring the system. Logging data is automatically backfilled.

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

    The issue has been resolved.

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

    Issue has been resolved

Read the full incident report →

Minor March 13, 2026 Intermittent API failures – Website - dash0.com, Authentication, Frontend - app.dash0.com

Started Mar 13, 2026, 02:21 PM UTC· resolved Mar 13, 2026, 02:21 PM UTC

  1. resolved Mar 13, 2026, 02:21 PM UTC

    Between 3:21PM and 3:29PM CET we've seen intermittent API failures causing "Failed to load data" errors in the UI. The problem has been identified and fixed already. Data ingest and processing was unaffected by the issue.

Read the full incident report →

Minor March 10, 2026 Auth Provider issues 21h Frontend - app.dash0.com

Started Mar 10, 2026, 03:55 PM UTC· resolved Mar 11, 2026, 12:55 PM UTC

  1. investigating Mar 10, 2026, 03:55 PM UTC

    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

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

    The situation has stabilized again. We keep monitoring the situation carefully for another 15m before closing the incident.

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

    We have not seen any any further issues and are closing the incident

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

    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

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

    Logins are functional again

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

    We are resolving the incident as all systems have remained healthy since the last update

Read the full incident report →

Minor February 19, 2026 Auth provider issues 53m Frontend - app.dash0.com

Started Feb 19, 2026, 04:26 PM UTC· resolved Feb 19, 2026, 05:20 PM UTC

  1. investigating Feb 19, 2026, 04:26 PM UTC

    Login to Dash0 is currently not possible due to issues with our Auth Provider. We are investigating the problem.

  2. identified Feb 19, 2026, 04:45 PM UTC

    Login to Dash0 is currently not possible due to issues with our Auth Provider. The problem is identified and our auth provider is working on a fix. Authentication might work for short periods but the platform will still feel slow due to auth token verification that is done on the auth provider side.

  3. monitoring Feb 19, 2026, 05:19 PM UTC

    The problems seem to be resolved and authentication / validation errors have gone down. We are actively monitoring the issue.

  4. monitoring Feb 19, 2026, 05:19 PM UTC

    The problems seem to be resolved and authentication / validation errors have gone down. We are actively monitoring the issue.

  5. resolved Feb 19, 2026, 05:20 PM UTC

    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.

Read the full incident report →

Major January 9, 2026 dash0 API issue in AWS us-west-2 and eu-central-1 6h 19m

Started Jan 09, 2026, 01:06 AM UTC· resolved Jan 09, 2026, 07:26 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Notice January 7, 2026 Notification lag for customers in eu-west-1 –

Started Jan 07, 2026, 08:36 AM UTC· resolved Jan 07, 2026, 08:36 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major January 6, 2026 UI Outage 16m

Started Jan 06, 2026, 01:17 PM UTC· resolved Jan 06, 2026, 01:33 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Critical December 5, 2025 Auth provider issues 54m

Started Dec 05, 2025, 08:53 AM UTC· resolved Dec 05, 2025, 09:47 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →