# Intermittent DNS issues in runs

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 2h 47m
- started 2026-03-16 21:20 UTC
- id: DWN-dd9b52df54
- Official page: https://status.trigger.dev/incident/850738

## Updates from Trigger.dev
### 2026-03-16 21:20 UTC: 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.

### 2026-03-17 00:07 UTC: 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.

From the builder: does your app depend on Trigger.dev? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=trigger-dev) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Trigger.dev.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-dd9b52df54), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.