Deployments recovered
Timeline · 1 update
- resolved Jun 03, 2026, 07:35 PM UTC
Deployments recovered
Trigger.dev Outage History
Trigger.dev is up right nowTrigger.dev had 18 outages in the last 2 years totaling 97h 43m of downtime — averaging 0.7 incidents per month.
There were 18 Trigger.dev outages since December 1, 2025 totaling 97h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
DNS in us-east-1 is degraded
Affected: Current status by service (Trigger.dev cloud)Current status by service (Trigger.dev OpenTelemetry)
Timeline · 3 updates
Realtime recovered
Timeline · 1 update
- resolved Apr 01, 2026, 07:09 PM UTC
Realtime recovered
Realtime is behind
Affected: Current status by service (Realtime)
Timeline · 2 updates
- investigating Apr 01, 2026, 12:00 PM UTC
Realtime metadata updates and streaming v1 are not live, they've fallen behind. We're trying to remediate this.
- resolved Apr 01, 2026, 06:57 PM UTC
Realtime is back to live. We're really sorry for this extended period of large delays. The service couldn't keep up the number of runs being processed and was falling further behind. We have made some configuration changes and upgraded it so it can cope with a higher throughput of runs. If you were using our React hooks that just did streaming, they were unimpacted by this.
Intermittent DNS issues in ...
Affected: Current status by service (Trigger.dev cloud)
Timeline · 2 updates
- investigating Mar 16, 2026, 09:20 PM UTC
From user runs we're seeing an increase in DNS related issues like: Error: getaddrinfo ENOTFOUND Error: getaddrinfo EAI_AGAIN We're investigating why this is happening.
- resolved Mar 17, 2026, 12:07 AM UTC
DNS service is now back to fully operational. Increased traffic combined with a routine infrastructure rollout caused intermittent DNS resolution failures. We've tuned our DNS configuration to resolve the issue and are working on longer-term improvements to prevent recurrence.
Dashboard and telemetry deg...
Affected: Current status by service (Trigger.dev cloud)Current status by service (Trigger.dev OpenTelemetry)
Timeline · 2 updates
- investigating Mar 06, 2026, 02:16 PM UTC
The runs list and detail pages in the dashboard are currently degraded due to an ongoing issue with our ClickHouse DB. We're also observing some logs and span ingestion failures. We're currently investigating. Run executions are not impacted.
- resolved Mar 06, 2026, 03:15 PM UTC
The issue has been resolved. Dashboard and telemetry are now fully operational.
Elevated dequeue times in u...
Affected: Current status by service (Trigger.dev cloud)
Timeline · 2 updates
- investigating Mar 01, 2026, 01:39 AM UTC
Dequeues are slower than normal in us-east-1. Runs are still executing, but they are slower to start. We’re investigating the issue.
- resolved Mar 01, 2026, 02:36 AM UTC
The issue is now resolved and dequeue times are back to normal. Mainly free-tier runs were affected. This was caused by a spike in the free-tier run volume.
Intermittent DNS failures a...
Affected: Current status by service (Trigger.dev cloud)
Timeline · 2 updates
- investigating Jan 23, 2026, 01:37 AM UTC
We are experiencing intermittent issues that may cause some task runs to fail. Automatic retries are in place and should recover most affected runs. Our team is actively working on resolution.
- resolved Jan 23, 2026, 04:19 AM UTC
Full service has been restored. Task execution is back to normal. If you experienced failures between 01:37 and 04:19 UTC, those runs can be retried successfully now. What happened: During a period of high activity, a backlog of completed runs built up faster than our cleanup processes could handle, which put pressure on internal services and caused intermittent failures. What we did: We spun up additional cleanup capacity to clear the backlog and restore normal operation. What we're doing next: We're increasing resource limits on critical internal services and adding better alerting so we can catch this earlier if it happens again.
Some schedules have stopped...
Affected: Current status by service (Trigger.dev cloud)
Timeline · 2 updates
- investigating Jan 21, 2026, 10:56 AM UTC
We had a brief outage earlier which affected a subset of schedules. We are working on a fix to get them going again.
- resolved Jan 21, 2026, 11:15 AM UTC
All schedules have been fully restored.
Issue with task logs
Affected: Current status by service (Trigger.dev OpenTelemetry)
Timeline · 2 updates
- investigating Jan 16, 2026, 05:03 PM UTC
Our task log storage system is currently overloaded and we are working on bringing up additional capacity, but in the meantime some logs may be lost.
- resolved Jan 16, 2026, 05:44 PM UTC
We have finally been able to provision additional capacity and logs are working again. A full post-mortem will follow.
Dashboard runs list is delayed
Affected: Current status by service (Trigger.dev cloud)
Timeline · 2 updates
- investigating Jan 02, 2026, 06:17 PM UTC
Our run sync to clickhouse process is currently delayed. The runs list in the dashboard will be behind but runs are executing as normal.
- resolved Jan 02, 2026, 09:16 PM UTC
The runs list is now up to do and syncing live updates again.
Batches are slow to process
Affected: Current status by service (Trigger.dev API)
Timeline · 2 updates
- investigating Jan 01, 2026, 10:00 AM UTC
There is a backlog in processing batchTrigger and batchTriggerAndWait calls. This means runs are being created slower than normal for these. We're investigating why this is happening
- resolved Jan 01, 2026, 03:10 PM UTC
The new batch concurrency processing defaults have brought the processing queue down to zero
Runs list is delayed
Affected: Current status by service (Trigger.dev cloud)
Timeline · 2 updates
- investigating Dec 17, 2025, 03:12 PM UTC
Runs are not syncing to our clickhouse instances fast enough and so there is a delay in data in the runs list dashboard. Runs are operating normally.
- resolved Dec 17, 2025, 03:30 PM UTC
Runs are now syncing live and the dashboard is back to normal.
Realtime streams v2 is degr...
Affected: Current status by service (Realtime)
Timeline · 2 updates
- investigating Dec 17, 2025, 07:28 AM UTC
Writes and reads to Realtime streams v2 are currently suffering an outage and we're investigating.
- investigating Dec 17, 2025, 08:16 AM UTC
Fix has been applied and realtime streams v2 is fully operational.
Dashboard issues due to Cli...
Affected: Current status by service (Trigger.dev cloud)
Timeline · 2 updates
- investigating Dec 16, 2025, 09:02 PM UTC
We’re seeing a percentage of queries failing from ClickHouse Cloud which powers some pages in the dashboard, like Tasks graphs, Runs page and the logs. We’re talking to their team to try resolve this.
- investigating Dec 16, 2025, 10:42 PM UTC
Operations have returned to normal, we're continuing to investigate the root cause and will provide more detail as we know more.
Dashboard is degraded
Affected: Current status by service (Trigger.dev cloud)Current status by service (Trigger.dev API)Current status by service (Trigger.dev OpenTelemetry)
Timeline · 2 updates
- 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.
- 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.
Runs list is lagging behind
Affected: Current status by service (Trigger.dev cloud)
Timeline · 2 updates
- 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.
- 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
open telemetry logs and spa...
Affected: Current status by service (Trigger.dev OpenTelemetry)
Timeline · 2 updates
- 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
- 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