- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 10of 100
What to do
Check whether you use Trigger.dev API. 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 4d 13h it lasted.
Anything that failed between 2026-11-01 22:50 UTC and 2026-11-06 12:27 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
- resolved
There has been a security incident at Trigger.dev. We've blocked the exploit used in this attack but our investigation has identified exposure across a subset of organizations. The attacker gained unauthorized access to environment variables for these organizations. We have emailed all impacted account owners with steps to mitigate. We will follow up with more details.
provider
- resolved
We’ve published our report on the November 1, 2026 security incident: [https://trigger.dev/blog/security-incident-report-nov-2026](https://trigger.dev/blog/security-incident-report-nov-2026)
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-c704a53289
Is Trigger.dev still down?
No, this incident was resolved 2026-11-06 12:27 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
4d 13h, from 2026-11-01 22:50 UTC to 2026-11-06 12:27 UTC, by the times Trigger.dev posted.
What was affected?
Trigger.dev named API.
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.