Railway incident

Builds and deployments stopped (record added Nov 5)

Resolved after 20 minutes, affecting Builds (US East (Virginia, USA)) and Running Workloads and Deployments (US East (Virginia, USA)) and 1 more, on October 5, 2026.

identified Oct 05, 2026, 02:45 PM UTC

Builds and deployments ran at 1 to 7% of normal for twenty minutes on October 5, from every source, caused by the API slowdown recorded in W5G4XFDQ. 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 05, 2026, 02:45 PM UTC
Resolved: Oct 05, 2026, 03:05 PM UTC
Duration: 20m
Detected by Pingoru: Oct 05, 2026, 02:45 PM 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))External & Third-Party Integrations (GitHub - Auto-Deploys)

Update timeline

identified Oct 05, 2026, 02:45 PM UTC

Builds and deployments ran at 1 to 7% of normal for twenty minutes on October 5, from every source, caused by the API slowdown recorded in W5G4XFDQ. 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 05, 2026, 03:05 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.