- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Payments & Billing
- Down Index
- 27of 100
What to do
Check whether you use Railway Payments & Billing. 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 42m it lasted.
Anything that failed between 2026-10-21 08:30 UTC and 2026-10-21 09:12 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.
Updates from Railway 2
- identified
Billing and plan-upgrade calls failed with an expired payment-provider key until the key was replaced. 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-f7c64a94a0
Is Railway still down?
No, this incident was resolved 2026-10-21 09:12 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
42m, from 2026-10-21 08:30 UTC to 2026-10-21 09:12 UTC, by the times Railway posted.
What was affected?
Railway named Payments & Billing.
What caused it?
Railway hasn't published a root cause. If it does, it shows here.
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.