Railway incident

Deployment queue backlog after the October 21 security incident (record added Nov 5)

Resolved after 9 hours 45 minutes, affecting Builds (US East (Virginia, USA)) and Running Workloads and Deployments (US East (Virginia, USA)) and 1 more, on October 22, 2026.

identified Oct 22, 2026, 06:30 AM UTC

Deployments queued at up to 47,000 (normal about 1,000) and started slowly until the backlog cleared at about 16:10 UTC. Record added on November 5, 2026 from the incident review that followed the October 21 security incident. This entry corrects the uptime record; no notification was sent for it.

Started: Oct 22, 2026, 06:30 AM UTC
Resolved: Oct 22, 2026, 04:15 PM UTC
Duration: 9h 45m
Detected by Pingoru: Oct 22, 2026, 06:30 AM UTC

Affected components

Builds (US East (Virginia, USA))Running Workloads and Deployments (US East (Virginia, USA))Builds (US West (California, USA))Running Workloads and Deployments (US West (California, USA))Builds (EU West (Amsterdam, Netherlands))Running Workloads and Deployments (EU West (Amsterdam, Netherlands))Builds (Southeast Asia (Singapore))Running Workloads and Deployments (Southeast Asia (Singapore))

Update timeline

identified Oct 22, 2026, 06:30 AM UTC

Deployments queued at up to 47,000 (normal about 1,000) and started slowly until the backlog cleared at about 16:10 UTC. Record added on November 5, 2026 from the incident review that followed the October 21 security incident. This entry corrects the uptime record; no notification was sent for it.
resolved Oct 22, 2026, 04:15 PM UTC

Resolved. This entry was added on November 5, 2026 to correct the record.

Your product runs on more than Railway

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.