- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 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 2h 59m it lasted.
Anything that failed between 2026-01-02 18:17 UTC and 2026-01-02 21:16 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 5
- update
Our run sync to clickhouse process is currently delayed. The runs list in the dashboard will be behind but runs are executing as normal.
provider
- update
We've identified the issue and are working on a fix now. Runs are still delayed (at the time of this update, the delay is about 32 minutes behind.
provider
- update
A fix has been deployed but the runs list continues to lag behind, but should be catching up soon. We're continuing to investigate and monitor the deployed fix.
provider
- update
We've confirmed the fix has improved the situation but the runs list is still behind. It's currently just over 45 minutes behind but that's down from the max of 57 minutes. We estimate the runs list will be live again in about 1-2 hours. We're sorry for the delay and will be pushing fixing this sync service to the top of our priority in the new year.
provider
- resolved
The runs list is now up to do and syncing live updates again.
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-10cf14cbc7
Is Trigger.dev still down?
No, this incident was resolved 2026-01-02 21:16 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
2h 59m, from 2026-01-02 18:17 UTC to 2026-01-02 21:16 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.