- Level
- confirmed
- Worst impact
- Major outage
- Components
- Southeast Asia (Singapore), GitHub - Auto-Deploys, US East (Virginia, USA), US West (California, USA), EU West (Amsterdam, Netherlands)
- Regions
- apac, eu, us
- Down Index
- 49of 100
What to do
Check whether you use Railway Southeast Asia (Singapore), GitHub - Auto-Deploys, US East (Virginia, USA), US West (California, USA) and 1 more in apac, eu, us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 20m it lasted.
Anything that failed between 2026-10-05 14:45 UTC and 2026-10-05 15:05 UTC may need a replay.Subscribe to Railway's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=railway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
Builds and deployments ran at 1 to 7% of normal for twenty minutes on October 5, from every source, caused by the API slowdown recorded in W5G4XFDQ.Read the postmortem
Updates from Railway 2
- identified
Builds and deployments ran at 1 to 7% of normal for twenty minutes on October 5, from every source, caused by the API slowdown recorded in W5G4XFDQ. 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.
provider
- resolved
Resolved. This entry was added on November 5, 2026 to correct the record.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-662326adc0
Is Railway still down?
No, this incident was resolved 2026-10-05 15:05 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
20m, from 2026-10-05 14:45 UTC to 2026-10-05 15:05 UTC, by the times Railway posted.
What was affected?
Railway named Southeast Asia (Singapore), GitHub - Auto-Deploys, US East (Virginia, USA), US West (California, USA) and 1 more in apac, eu, us.
What caused it?
Railway wrote: "Builds and deployments ran at 1 to 7% of normal for twenty minutes on October 5, from every source, caused by the API slowdown recorded in W5G4XFDQ." The postmortem: https://status.railway.com/incident/86KOKCLE
Where does this come from?
Railway's official status page, https://status.railway.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.