Trigger.dev incident

Dashboard is degraded

Minor Resolved View vendor source →

Trigger.dev experienced a minor incident on December 16, 2025 affecting Current status by service (Trigger.dev cloud) and Current status by service (Trigger.dev API) and 1 more component, lasting 22m. The incident has been resolved; the full update timeline is below.

Started
Dec 16, 2025, 10:43 AM UTC
Resolved
Dec 16, 2025, 11:05 AM UTC
Duration
22m
Detected by Pingoru
Dec 16, 2025, 10:43 AM UTC

Affected components

Current status by service (Trigger.dev cloud)Current status by service (Trigger.dev API)Current status by service (Trigger.dev OpenTelemetry)

Update timeline

  1. investigating Dec 16, 2025, 10:43 AM UTC

    The dashboard is currently degraded due to an ongoing issue with our ClickHouse DB. We're currently investigating further. Run executions are not impacted.

  2. resolved Dec 16, 2025, 11:05 AM UTC

    The issue in ClickHouse is now resolved. The dashboard is back to being fully operational. The root cause was a faulty node in the ClickHouse cluster which we couldn't kill. We're speaking to the ClickHouse Cloud team to find out why it happened.