Is Dash0 down?

Last checked 4m ago
Current status
Dash0 is up

No incidents right now.

Official status page: https://www.dash0status.com · Polled every 5 minutes · 21 components tracked

Dash0 is operational right now. Last checked 4m ago; the most recent incident resolved 2d ago.

Real-time Dash0 status, recent outages, and incident history — pulled directly from Dash0's official status page at https://www.dash0status.com every 5 minutes. Pingoru tracks 21 Dash0 services and has captured 13 incidents in the last 90 days (99.58% uptime). Get email, Slack, Discord, or webhook alerts the moment Dash0 reports a new incident — free for 5 monitors, no credit card.

Users who monitor Dash0 also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Dash0 uptime 99.58% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jul 29, 2026, 11:55 AM UTC · Resolved Jul 29, 2026, 11:55 AM UTC
    Frontend - app.dash0.com
    Timeline · 4 updates
    • 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)

    • 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)

    • 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)

    • 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)

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

  2. Resolved
    Started Jul 20, 2026, 09:14 PM UTC · Resolved Jul 20, 2026, 09:14 PM UTC
    Timeline · 3 updates
    • 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.

    • 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.

    • resolved · Jul 20, 2026, 09:14 PM UTC

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

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

  3. Resolved
    Started Jul 20, 2026, 02:31 PM UTC · Resolved Jul 20, 2026, 02:31 PM UTC
    Timeline · 3 updates
    • investigating · Jul 20, 2026, 01:39 PM UTC

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

    • monitoring · Jul 20, 2026, 01:46 PM UTC

      Status: Monitoring Mitigation applied, we are monitoring the recovery

    • 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

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

  4. Resolved
    Started Jul 17, 2026, 07:42 PM UTC · Resolved Jul 17, 2026, 07:42 PM UTC
    Timeline · 4 updates
    • 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)

    • 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)

    • 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)

    • 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)

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

  5. Resolved
    Started Jul 08, 2026, 09:18 AM UTC · Resolved Jul 08, 2026, 09:18 AM UTC
    Timeline · 5 updates
    • 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)

    • 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)

    • 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)

    • 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)

    • 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)

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

See the full Dash0 outage history

4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Dash0 outage history →

Or sign up free to get alerts when Dash0 breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 9 incidents View full outage history →