- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 23of 100
What to do
Check whether you use Trigger.dev in us, us-east-1. 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 18m it lasted.
Anything that failed between 2025-10-05 16:56 UTC and 2025-10-05 17:14 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
Dequeues are slower than normal in us-east-1. We’re investigating.
provider
- resolved
Runs on `large-2x` machines were processing more slowly due to incredibly high volume. One of our customers caused an infinite loop in their large machine tasks which kept triggering more runs. Runs on small and medium machines were unlikely to have been impacted by this.
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-36a4490751
Is Trigger.dev still down?
No, this incident was resolved 2025-10-05 17:14 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
18m, from 2025-10-05 16:56 UTC to 2025-10-05 17:14 UTC, by the times Trigger.dev posted.
What was affected?
Trigger.dev named in us, us-east-1.
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.