Trigger.dev experienced a minor incident on March 16, 2026 affecting Current status by service (Trigger.dev cloud), lasting 2h 47m. The incident has been resolved; the full update timeline is below.
Affected components
Current status by service (Trigger.dev cloud)
Update timeline
- investigating Mar 16, 2026, 09:20 PM UTC
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.
- resolved Mar 17, 2026, 12:07 AM UTC
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.