Railway incident

Builds unavailable during the October 21 security incident (record added Nov 5)

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

identified Oct 21, 2026, 07:15 AM UTC

No builds or deployments completed between 07:15 UTC on October 21 and 03:20 UTC on October 22, when Enterprise builds were restored. The platform incident (QH8L8B3E) recorded builds as Degraded. 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 21, 2026, 07:15 AM UTC
Resolved: Oct 22, 2026, 03:20 AM UTC
Duration: 20h 5m
Detected by Pingoru: Oct 21, 2026, 07:15 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))External & Third-Party Integrations (GitHub - Auto-Deploys)

Update timeline

identified Oct 21, 2026, 07:15 AM UTC

No builds or deployments completed between 07:15 UTC on October 21 and 03:20 UTC on October 22, when Enterprise builds were restored. The platform incident (QH8L8B3E) recorded builds as Degraded. 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, 03:20 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.