Railway incident

Builds restored in stages after the October 21 security incident (record added Nov 5)

Resolved after 19 hours 29 minutes, affecting Builds (US East (Virginia, USA)) and Builds (US West (California, USA)) and 1 more, on October 22, 2026.

identified Oct 22, 2026, 03:20 AM UTC

Builds returned one plan at a time: Enterprise 03:20, Pro 06:29, Hobby 21:08, Free and Trial 22:49 UTC. Build errors stayed high until 17:00 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, 03:20 AM UTC
Resolved
Oct 22, 2026, 10:49 PM UTC
Duration
19h 29m
Detected by Pingoru
Oct 22, 2026, 03:20 AM UTC

Affected components

Builds (US East (Virginia, USA))Builds (US West (California, USA))Builds (EU West (Amsterdam, Netherlands))Builds (Southeast Asia (Singapore))External & Third-Party Integrations (GitHub - Auto-Deploys)

Update timeline

  1. identified Oct 22, 2026, 03:20 AM UTC

    Builds returned one plan at a time: Enterprise 03:20, Pro 06:29, Hobby 21:08, Free and Trial 22:49 UTC. Build errors stayed high until 17:00 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.

  2. resolved Oct 22, 2026, 10:49 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.

Add your stack →