Trigger.dev Outage History

Trigger.dev major outage View live status →

Trigger.dev had 28 outages in the last 2 years totaling 21h 51m of downtime — averaging 1.2 incidents per month.

There were 28 Trigger.dev outages since December 1, 2025 totaling 21h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.trigger.dev

Minor December 16, 2025

Dashboard is degraded

Detected by Pingoru
Dec 16, 2025, 10:43 AM UTC
Resolved
Dec 16, 2025, 11:05 AM UTC
Duration
22m
Affected: Global (Dashboard)Global (API)Global (OpenTelemetry)
Timeline · 2 updates
  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.

Read the full incident report →

Minor December 4, 2025

Runs list is lagging behind

Detected by Pingoru
Dec 04, 2025, 03:16 PM UTC
Resolved
Dec 04, 2025, 03:35 PM UTC
Duration
19m
Affected: Global (Dashboard)
Timeline · 2 updates
  1. investigating Dec 04, 2025, 03:16 PM UTC

    The runs list is currently showing stale data. Runs are executing like normal. Our replication process from postgresql to our Clickhouse instance is falling behind and so the dashboard will be showing stale run data. We're investigating.

  2. investigating Dec 04, 2025, 03:35 PM UTC

    The runs list has all caught up and the dashboard is no longer displaying stale data. We're continuing to investigate the root cause of this issue

Read the full incident report →

Minor December 1, 2025

open telemetry logs and spa...

Detected by Pingoru
Dec 01, 2025, 02:08 PM UTC
Resolved
Dec 02, 2025, 11:18 AM UTC
Duration
21h 10m
Affected: Global (OpenTelemetry)
Timeline · 2 updates
  1. investigating Dec 01, 2025, 02:08 PM UTC

    We are currently having issues with our ingestion of open telemetry logs and spans after rolling out a fix for the issue that was happening over the weekend with clickhouse. We're investigating

  2. investigating Dec 02, 2025, 11:18 AM UTC

    We've published a full post-mortem on this incident here: https://trigger.dev/blog/clickhouse-too-many-parts-postmortem

Read the full incident report →