- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 6m it lasted.
Anything that failed between 2025-10-22 09:23 UTC and 2025-10-22 11:29 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
We're currently experiencing an issue with our Clickhouse cluster that is causing runs list in the dashboard and via the `runs.list()` endpoint to return stale data as inserts into clickhouse have degraded p95 latencies. We're investigating the issue. Runs executions are uneffected.
provider
- update
We're working with Clickhouse Cloud to find the root cause of the issue, in the meantime we are working on a temporary mitigation which should hopefully help. There may be some missing runs from the dashboard temporarily, but runs will be backfilled into clickhouse after the issue has been addressed.
provider
- resolved
We are still working with clickhouse cloud on identifying the root cause of the issue but have pushed out a fix that has allowed the runs list to come back online and show live results in the meantime. We suspect the issue is related to our clickhouse server being "rotated" into another AZ which caused network degradation and cause our replication pipeline from postgresql to clickhouse to fall behind and unable to keep up with changes. The fix was to stop sending payload data to clickhouse which is not currently being used but we planned to in the future. Turning it off for now while we investigate the underlying cause seems like a good tradeoff and we suspect will fix this issue going forward.
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-47f592784c
Is Trigger.dev still down?
No, this incident was resolved 2025-10-22 11:29 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
2h 6m, from 2025-10-22 09:23 UTC to 2025-10-22 11:29 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.