Railway incident

Deployments paused (record added Nov 5)

Critical Vendor's status page →

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

identified Oct 28, 2026, 06:20 PM UTC

Deployments and builds were paused deliberately for twenty minutes inside the October 28 incident. 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 28, 2026, 06:20 PM UTC
Resolved
Oct 28, 2026, 06:40 PM UTC
Duration
20m
Detected by Pingoru
Oct 28, 2026, 06: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

  1. identified Oct 28, 2026, 06:20 PM UTC

    Deployments and builds were paused deliberately for twenty minutes inside the October 28 incident. 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 28, 2026, 06:40 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.

Cloudflare Amazon Web Services Twilio Stripe Slack Okta Figma GitHub Datadog Vercel OpenAI Google Cloud
Add your stack →