# us-east-1 slow dequeues for large machines

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Degraded
- lasted 18m
- started 2025-10-05 16:56 UTC
- us, us-east-1
- id: DWN-36a4490751
- Official page: https://status.trigger.dev/incident/737975

## Updates from Trigger.dev
### 2025-10-05 16:56 UTC: update
Dequeues are slower than normal in us-east-1. We’re investigating.

### 2025-10-05 17:14 UTC: resolved
Runs on \`large-2x\` machines were processing more slowly due to incredibly high volume. One of our customers caused an infinite loop in their large machine tasks which kept triggering more runs. Runs on small and medium machines were unlikely to have been impacted by this.

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-36a4490751), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
