Railway incident

Hobby deployments paused during the API degradation (record added Nov 5)

Resolved after 50 minutes, affecting Builds (US East (Virginia, USA)) and Running Workloads and Deployments (US East (Virginia, USA)) and 1 more, on September 29, 2026.

identified Sep 29, 2026, 05:20 PM UTC

Hobby deployments were paused for fifty minutes during the September 29 API degradation, a Partial outage for deployments. 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 29, 2026, 05:20 PM UTC
Resolved: Sep 29, 2026, 06:10 PM UTC
Duration: 50m
Detected by Pingoru: Sep 29, 2026, 05:20 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))

Update timeline

identified Sep 29, 2026, 05:20 PM UTC

Hobby deployments were paused for fifty minutes during the September 29 API degradation, a Partial outage for deployments. 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 29, 2026, 06:10 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.