All Systems Operational
Control Plane ? Operational
90 days ago
100.0 % uptime
Today
Frontend - app.dash0.com ? Operational
90 days ago
100.0 % uptime
Today
Website - dash0.com Operational
90 days ago
100.0 % uptime
Today
Amazon Web Services (AWS) Operational
90 days ago
100.0 % uptime
Today
eu-west-1 Operational
90 days ago
100.0 % uptime
Today
us-west-2 Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Mar 18, 2025

No incidents reported today.

Mar 17, 2025

No incidents reported.

Mar 16, 2025

No incidents reported.

Mar 15, 2025
Resolved - The widely used GitHub action, tj-actions/changed-files, experienced a security compromise. Dash0 utilized this action within our GitHub actions. Following a thorough investigation, we have confirmed that while Dash0 employed the compromised action, no evidence of token misuse was identified.

Our implementation of tj-actions/changed-files utilized ephemeral access tokens, restricted to a single repository, and valid only for the duration of individual job executions. We conducted a comprehensive audit of all relevant repository artifacts, including commits, tags, issues, pull requests, releases, and container images published via ghcr.io, to ascertain the absence of any unauthorized or malicious activity.

Dash0 maintains robust security measures, including automated systems that monitor user activity for anomalous behavior. We have taken immediate steps to ensure that similar attack patterns do not affect us going forward for our most important repositories. Furthermore, we are actively refining our security protocols to address the evolving landscape of cyber threats, with a particular focus on the secure integration of GitHub actions.

We strongly advise all GitHub action users to conduct a diligent review of their workflows for potential vulnerabilities associated with this incident. For detailed information, please see:

- https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised
- https://semgrep.dev/blog/2025/popular-github-action-tj-actionschanged-files-is-compromised/

Mar 15, 13:16 UTC
Mar 14, 2025

No incidents reported.

Mar 13, 2025
Resolved - This incident has been resolved.

Deriving operations from spans is working again. The following attributes are now available again:

- dash0.operation.name
- dash0.operation.type
- dash0.span.name
- dash0.span.type

Mar 13, 16:57 UTC
Monitoring - Data ingestion is back to normal. All telemetry data has automatically been backfilled.

Deriving operations from spans is currently not available.

We are monitoring the issue and will deploy a fix shortly that allows deriving operations from spans again.

Mar 13, 16:34 UTC
Update - We have identified the problem and are rolling out a short term fix to mitigate the issue.
Mar 13, 16:12 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 13, 16:05 UTC
Investigating - We are currently investigating this issue.
Mar 13, 15:45 UTC
Mar 12, 2025

No incidents reported.

Mar 11, 2025
Completed - The scheduled maintenance has been completed.
Mar 11, 01:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 11, 00:00 UTC
Scheduled - We will be performing a scheduled maintenance on our backend to ensure the continued reliability and performance of our services.

Impact: During this maintenance window, you may experience metrics ingestion delay and possible small data gap(s).

Reason: This maintenance is necessary to apply important updates and improvements to our backend systems.

Mar 10, 03:28 UTC
Mar 10, 2025
Completed - The scheduled maintenance has been completed.
Mar 10, 01:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 10, 00:00 UTC
Scheduled - We will be performing a scheduled maintenance on our backend to ensure the continued reliability and performance of our services.

Impact: During this maintenance window, you may experience metrics ingestion delay and possible small data gap(s).

Reason: This maintenance is necessary to apply important updates and improvements to our backend systems.

Mar 7, 00:55 UTC
Mar 9, 2025

No incidents reported.

Mar 8, 2025

No incidents reported.

Mar 7, 2025

No incidents reported.

Mar 6, 2025

No incidents reported.

Mar 5, 2025

No incidents reported.

Mar 4, 2025

No incidents reported.