- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- eu, eu-central-1, us, us-east-1
- Down Index
- 43of 100
What to do
Check whether you use Trigger.dev in eu, eu-central-1, 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 58m it lasted.
Anything that failed between 2025-10-20 08:35 UTC and 2025-10-20 09:33 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
There is an ongoing AWS outage that is affecting our services in us-east-1. We are actively monitoring the situation and putting mitigations in place. Please check the AWS Health dashboard for updates: https://health.aws.amazon.com/health/status
provider
- update
Currently the main issue is cold starts because image pulls from AWS ECR are failing because of the AWS us-east-1 outage. Warm starts are unaffected. A workaround is currently available by navigating to the Regions page in the Trigger.dev dashboard and switching the default region to eu-central-1.
provider
- resolved
AWS us-east-1's latest update has stated that they are seeing "significant signs of recovery" and we're seeing the same in our worker cluster, as now image pulls are working and both cold and warm starts are now processing as normal. We'll continue to closely monitor the situation.
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-e21ca9419c
Is Trigger.dev still down?
No, this incident was resolved 2025-10-20 09:33 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
58m, from 2025-10-20 08:35 UTC to 2025-10-20 09:33 UTC, by the times Trigger.dev posted.
What was affected?
Trigger.dev named in eu, eu-central-1, 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.