- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 25of 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 57m it lasted.
Anything that failed between 2026-03-01 01:39 UTC and 2026-03-01 02:36 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
Dequeues are slower than normal in us-east-1. Runs are still executing, but they are slower to start. We’re investigating the issue.
provider
- update
We have identified the root cause and we're applying a fix. Mainly free-tier runs were affected.
provider
- resolved
The issue is now resolved and dequeue times are back to normal. Mainly free-tier runs were affected. This was caused by a spike in the free-tier run volume.
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-adfdf7673e
Is Trigger.dev still down?
No, this incident was resolved 2026-03-01 02:36 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
57m, from 2026-03-01 01:39 UTC to 2026-03-01 02:36 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.