# Deployments failing due to upstream provider

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Degraded
- lasted 2h 20m
- started 2025-10-28 19:00 UTC
- id: DWN-354085e308
- Official page: https://status.trigger.dev/incident/753125

## Updates from Trigger.dev
### 2025-10-28 19:00 UTC: update
Our upstream remote build provider is currently facing issues, causing some deployment failures on our side. More details on their status page: https://status.depot.dev/

### 2025-10-28 21:20 UTC: resolved
Depot resolved the issue on their side. Deployments are now working normally again.

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