- 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 19m it lasted.
Anything that failed between 2025-12-04 15:16 UTC and 2025-12-04 15:35 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 3
- update
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.
provider
- update
We are slowly catching up with live run data and should be back to normal operation very soon.
provider
- resolved
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
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-d7be025662
Is Trigger.dev still down?
No, this incident was resolved 2025-12-04 15:35 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
19m, from 2025-12-04 15:16 UTC to 2025-12-04 15:35 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.