Railway incident

Deployments and builds stopped (record added Nov 5)

Resolved after 15 minutes, affecting Builds (US East (Virginia, USA)) and Running Workloads and Deployments (US East (Virginia, USA)) and 1 more, on August 28, 2026.

identified Aug 28, 2026, 11:45 PM UTC

Deployments and builds stopped fully for fifteen minutes inside the August 28 deployment slowdown. 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: Aug 28, 2026, 11:45 PM UTC
Resolved: Aug 29, 2026, 12:00 AM UTC
Duration: 15m
Detected by Pingoru: Aug 28, 2026, 11: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))

Update timeline

identified Aug 28, 2026, 11:45 PM UTC

Deployments and builds stopped fully for fifteen minutes inside the August 28 deployment slowdown. 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 Aug 29, 2026, 12:00 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.