- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 30of 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 40m it lasted.
Anything that failed between 2026-05-23 15:00 UTC and 2026-05-23 17:40 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
Trigger.dev deploy runs are failing with a `401 Unauthorized` push error. This is due to a downstream provider, we're working with them to get this back online. Workaround: deploy with --native-build-server: https://trigger.dev/changelog/deployments-with-native-builds
provider
- resolved
This is now resolved, deploys should be working as normal. We've also implemented a change to prevent further DNS rollbacks.
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-92b8b27fe4
Is Trigger.dev still down?
No, this incident was resolved 2026-05-23 17:40 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
2h 40m, from 2026-05-23 15:00 UTC to 2026-05-23 17:40 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.