# Intermittent DNS failures affecting some run executions

- Provider: [Trigger.dev](https://down.guide/trigger-dev)
- Level: confirmed
- Impact: Degraded
- lasted 2h 42m
- started 2026-01-23 01:37 UTC
- id: DWN-4139a85cfa
- Official page: https://status.trigger.dev/incident/810341

## Updates from Trigger.dev
### 2026-01-23 01:37 UTC: update
We are experiencing intermittent issues that may cause some task runs to fail. Automatic retries are in place and should recover most affected runs. Our team is actively working on resolution.

### 2026-01-23 04:19 UTC: resolved
Full service has been restored. Task execution is back to normal. If you experienced failures between 01:37 and 04:19 UTC, those runs can be retried successfully now. 
What happened: During a period of high activity, a backlog of completed runs built up faster than our cleanup processes could handle, which put pressure on internal services and caused intermittent failures. 
What we did: We spun up additional cleanup capacity to clear the backlog and restore normal operation. 
What we're doing next: We're increasing resource limits on critical internal services and adding better alerting so we can catch this earlier if it happens again.

---
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://sazabi.com/?utm_source=down-guide&utm_medium=markdown).