# Deployment slowness

- Provider: [Railway](https://down.guide/railway)
- Level: confirmed
- Impact: Partial outage
- lasted 5h 31m
- started 2026-03-10 15:19 UTC
- EU West (Amsterdam, Netherlands), US East (Virginia, USA), Southeast Asia (Singapore) +1
- apac, eu, us
- id: DWN-26c02b96f1
- Official page: https://status.railway.com/incident/2LUOHTX3

## Updates from Railway
### 2026-03-10 15:19 UTC: investigating
We are currently investigating an issue causing deployments to take longer than normal

### 2026-03-10 15:36 UTC: identified
We've pushed out a fix and are seeing slow recovery.

### 2026-03-10 15:59 UTC: monitoring
We're seeing recovery, with delays primarily impacting trial deployments. We are monitoring for full recovery.

### 2026-03-10 16:40 UTC: monitoring
We are continuing to monitor this incident. Deployments may be queued, but are going through

### 2026-03-10 17:20 UTC: monitoring
Our team continues to work on this incident. Deploys are still slow, but not failing.

### 2026-03-10 18:00 UTC: monitoring
Deployment slowness is persisting. Deploys are completing but with longer than normal queue and build times. Our team is actively working on a resolution.

### 2026-03-10 18:58 UTC: monitoring
Elevated load continues to cause slowness on our system. We're pausing Free, Trial and Hobby deployments to assist with deployment backpressure.

### 2026-03-10 19:23 UTC: monitoring
Elevated load continues to cause slowness on our system. We' have restored all Pro deployments back to nominal, we are turning on Hobby slowly to assist with deployment backpressure.

### 2026-03-10 19:51 UTC: monitoring
We've successfully eliminated slowness from our deployment pipeline, and are re-enabling deployments for all plans as the backpressure is recovering.

### 2026-03-10 20:07 UTC: monitoring
We are seeing improvement — deployments are now processing without being queued. We continue to monitor the situation and will provide a further update once we are confident the issue is fully resolved

### 2026-03-10 20:49 UTC: resolved
This incident has been resolved.

---
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).
