Railway incident

Deployment failures (record added Nov 5)

Resolved after 20 minutes, affecting API - backboard.railway.com and Builds (US East (Virginia, USA)) and 1 more, on September 8, 2026.

identified Sep 08, 2026, 02:30 AM UTC

Deployments were down 40 to 60% for twenty minutes with API errors at 1.9%. No incident was opened at the time. 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: Sep 08, 2026, 02:30 AM UTC
Resolved: Sep 08, 2026, 02:50 AM UTC
Duration: 20m
Detected by Pingoru: Sep 08, 2026, 02:30 AM UTC

Affected components

API - backboard.railway.comBuilds (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 Sep 08, 2026, 02:30 AM UTC

Deployments were down 40 to 60% for twenty minutes with API errors at 1.9%. No incident was opened at the time. 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 Sep 08, 2026, 02:50 AM 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.