Trigger.dev status history
37 incidents over the last year, newest first; 100.00% uptime (90 days), 99.96% uptime (12 months). History from before down.guide started reading the page is imported from Trigger.dev's own archive.
Month
2026-11
1 incident
Month
2026-10
1 incident
Month
2026-09
2 incidents
Month
2026-08
1 incident
Month
2026-07
4 incidents
- Trigger.devMajor outageDashboard is unavailable
- Trigger.devDegradedRuns listing is degraded
- Trigger.devMajor outageSingle Sign On (SSO) is unavailable
- Trigger.devDegradedRun Lists and Logs Are Degraded
Month
2026-06
2 incidents
Month
2026-05
2 incidents
- Trigger.devPartial outageDeploys failing with 401
- Trigger.devPartial outageDeploys failing
Month
2026-04
2 incidents
Month
2026-03
3 incidents
Month
2026-01
6 incidents
- Trigger.devDegradedIntermittent DNS failures affecting some run executions
- Trigger.devDegradedDashboard runs list is delayed
- Trigger.devPartial outageSome schedules have stopped working
- Trigger.devDegradedIssue with task logs
- Trigger.devDegradedDashboard runs list is delayed
- Trigger.devDegradedBatches are slow to process
Month
2025-12
6 incidents
Month
2025-11
1 incident
Month
2025-10
6 incidents
- Trigger.devDegradedDeployments failing due to upstream provider
- Trigger.devDegradedus-east-1 slow dequeues for large machines
- Trigger.devDegradedDashboard runs list is delayed
- Trigger.devPartial outageRuns list and dashboard logs are impacted by the AWS us-east-1 outage
- Trigger.devPartial outageDeploys are still impacted by the us-east-1 outage
- Trigger.devPartial outageAWS outage in us-east-1 is causing service disruption
More
Keep reading
Trigger.dev's live status, comparisons with similar providers and the site-wide rankings.