- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 15of 100
What to do
Check whether your product depends on Trigger.dev. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 18m it lasted.
Anything that failed between 2025-12-17 15:12 UTC and 2025-12-17 15:30 UTC may need a replay.Subscribe to Trigger.dev's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=trigger-dev works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Trigger.dev 2
- update
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.
provider
- resolved
Runs are now syncing live and the dashboard is back to normal.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2633ed6359
Is Trigger.dev still down?
No, this incident was resolved 2025-12-17 15:30 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
18m, from 2025-12-17 15:12 UTC to 2025-12-17 15:30 UTC, by the times Trigger.dev posted.
What caused it?
Trigger.dev hasn't published a root cause. If it does, it shows here.
Where does this come from?
Trigger.dev's official status page, https://status.trigger.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.