Runs list/logs degraded
Affected: Global (Dashboard)Global (API)Global (OpenTelemetry)
Trigger.dev Outage History
Trigger.dev is up right nowTrigger.dev had 28 outages in the last 2 years totaling 215h 51m of downtime — averaging 1.2 incidents per month.
There were 28 Trigger.dev outages since December 1, 2025 totaling 215h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.
Runs list dashboard and API...
Affected: Global (Dashboard)Global (API)
Timeline · 2 updates
- investigating Aug 24, 2026, 02:25 PM UTC
The runs list dashboard and API is degraded leading to increased latency and/or timeouts.We're investigating and attempting to bring this back online.
- resolved Aug 24, 2026, 03:34 PM UTC
We are still working on the root cause patch and it will rollout as soon as its tested and ready. We're resolving this status update for now as the run list API and dashboard have been running in good health for the last 30 minutes
Deployments recovered
Timeline · 1 update
- resolved Aug 13, 2026, 12:21 PM UTC
Deployments recovered
Realtime streams are degraded
Affected: Global (Realtime)
Timeline · 2 updates
- investigating Aug 05, 2026, 08:28 PM UTC
Realtime streams are currently degraded, we're working with our partner to bring full performance back as quickly as possible.
- resolved Aug 05, 2026, 08:34 PM UTC
A small percentage of streams experienced issues but it's resolved now. The root cause was some server crashes for our provider which they're working on a permanent fix for now.
Single sign-on (SSO) recovered
Timeline · 1 update
- investigating Jul 31, 2026, 04:02 PM UTC
Single sign-on (SSO) went down
Dashboard is unavailable
Affected: Global (Dashboard)
Timeline · 2 updates
- investigating Jul 16, 2026, 04:19 PM UTC
The dashboard is currently unavailable for all users. A fix has been identified and is being applied. Task runs are not impacted by this issue.
- resolved Jul 16, 2026, 04:26 PM UTC
The dashboard is now available. If you are still experiencing issues please hard reload the dashboard application.
Runs listing is degraded
Affected: Global (Dashboard)Global (API)
Timeline · 2 updates
- investigating Jul 16, 2026, 01:27 PM UTC
Listing runs on the dashboard and via the API is currently degraded. A fix is being rolled out now. Run operations are unaffected.
- resolved Jul 16, 2026, 02:16 PM UTC
The issue is now resolved, the dashboard and API are operating normally.
Single Sign On (SSO) is una...
Affected: Global (Dashboard)
Timeline · 1 update
- investigating Jul 16, 2026, 09:38 AM UTC
SSO login to the Trigger.dev dashboard is unavailable. We are investigating. Operations are unaffected.
Run Lists and Logs Are Degr...
Affected: Global (Dashboard)Global (API)
Timeline · 1 update
- investigating Jul 15, 2026, 11:57 AM UTC
Runs are executing normally. The replication of runs to ClickHouse which powers the Runs list are impacted. We're investigating.
Realtime recovered
Timeline · 1 update
- resolved Jul 01, 2026, 02:12 AM UTC
Realtime recovered
Task execution recovered
Timeline · 1 update
- resolved Jun 23, 2026, 02:07 PM UTC
Task execution recovered
us-east-1 region dequeue de...
Affected: Global (Dashboard)
Timeline · 3 updates
- investigating Jun 22, 2026, 07:05 PM UTC
This predominantly affects larger machine sizes. AWS is having capacity issues.
- resolved Jun 23, 2026, 09:43 PM UTC
US East 1 and EU Central 1 dequeue performance issues have been resolved. We're continuing to monitor the situation and a full post-mortem will follow.
- resolved Jun 27, 2026, 02:54 PM UTC
The full postmortem has been posted here: https://trigger.dev/blog/incident-report-jun-22-2026
DNS in us-east-1 is degraded
Affected: Global (Dashboard)Global (OpenTelemetry)
Timeline · 3 updates
Realtime is behind
Affected: Global (Realtime)Global (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: Global (Dashboard)
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: Global (Dashboard)Global (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: Global (Dashboard)
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: Global (Dashboard)
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: Global (Dashboard)
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: Global (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: Global (Dashboard)
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: Global (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: Global (Dashboard)
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: Global (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: Global (Dashboard)
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.