- 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 47m it lasted.
Anything that failed between 2026-03-16 21:20 UTC and 2026-03-17 00:07 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
From user runs we're seeing an increase in DNS related issues like: Error: getaddrinfo ENOTFOUND Error: getaddrinfo EAI_AGAIN We're investigating why this is happening.
provider
- resolved
DNS service is now back to fully operational. Increased traffic combined with a routine infrastructure rollout caused intermittent DNS resolution failures. We've tuned our DNS configuration to resolve the issue and are working on longer-term improvements to prevent recurrence.
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-dd9b52df54
Is Trigger.dev still down?
No, this incident was resolved 2026-03-17 00:07 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
2h 47m, from 2026-03-16 21:20 UTC to 2026-03-17 00:07 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.