- Level
- confirmed
- Worst impact
- Partial outage
- Components
- US West (California, USA), US East (Virginia, USA)
- Regions
- us
- Down Index
- 32of 100
What to do
Check whether you use Railway US West (California, USA), US East (Virginia, USA) in 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 1h 8m it lasted.
Anything that failed between 2026-07-01 22:29 UTC and 2026-07-01 23:37 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 3
- investigating
We are aware of elevated latency affecting some users. We are actively investigating and will provide updates as we learn more.
provider
- monitoring
We have identified packet loss affecting several edge network points of presence in North America. We have seen recovery and are monitoring the situation.
provider
- resolved
We have observed healthy response times and are resolving this incident.
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-b3bc0d5ec4
Is Railway still down?
No, this incident was resolved 2026-07-01 23:37 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
1h 8m, from 2026-07-01 22:29 UTC to 2026-07-01 23:37 UTC, by the times Railway posted.
What was affected?
Railway named US West (California, USA), US East (Virginia, USA) in us.
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.