- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 36of 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 14m it lasted.
Anything that failed between 2025-11-28 19:40 UTC and 2025-11-28 19:54 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
Parts of the dashboard are either missing data or unresponsive at the moment as we work through some issues with our clickhouse database. Currently trying to get it back online and then will update with more details.
provider
- resolved
We have recovered the clickhouse instance and the dashboard is responsive again and serving queries and data ingestion is back online. There has been some loss of otel data during this downtime but we don't know the extent of it at this moment as we continue to recover and investigate.
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-7dcf9b77f8
Is Trigger.dev still down?
No, this incident was resolved 2025-11-28 19:54 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
14m, from 2025-11-28 19:40 UTC to 2025-11-28 19:54 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.