# Deploys failing with 401

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 2h 40m
- started 2026-05-23 15:00 UTC
- id: DWN-92b8b27fe4
- Official page: https://status.trigger.dev/incident/903613

## Updates from Trigger.dev
### 2026-05-23 15:00 UTC: update
Trigger.dev deploy runs are failing with a \`401 Unauthorized\` push error. This is due to a downstream provider, we're working with them to get this back online.
Workaround: deploy with --native-build-server: https://trigger.dev/changelog/deployments-with-native-builds

### 2026-05-23 17:40 UTC: resolved
This is now resolved, deploys should be working as normal. We've also implemented a change to prevent further DNS rollbacks.

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