- Level
- confirmed
- Worst impact
- Major outage
- Components
- US West (California, USA), US East (Virginia, USA), Traffic
- Regions
- us
What to do
Check whether you use Railway US West (California, USA), US East (Virginia, USA), Traffic 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 4h 17m it lasted.
Anything that failed between 2026-07-02 07:44 UTC and 2026-07-02 12:01 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 9
- investigating
We are aware of elevated latency and packet loss affecting users in US regions. Users may experience increased response times or intermittent connectivity issues. We are actively investigating and will provide updates as we learn more.
provider
- identified
We have traced the elevated latency and packet loss affecting US regions to an issue with an upstream fiber provider. We are pulling the affected provider from our network path to route traffic around the disruption. While this reroute is in progress, users in US regions may continue to experience increased response times or intermittent connectivity, and private networking between regions may also be affected.
provider
- identified
Traffic continues to route around the affected upstream fiber provider following our earlier reroute. We are seeing conditions in US regions improve, but latency and packet loss have not fully returned to baseline, and cross-region private networking may still be intermittent. We are continuing to work toward full recovery and are monitoring closely.
provider
- identified
The issue affecting US regions has worsened and is now causing widespread disruption. Many users may experience failed connections, significantly elevated latency, and packet loss, and private networking between regions is heavily degraded. This impacts all traffic into and out of our US East region. Our earlier reroute has not fully mitigated the impact. We are working on adjusting our network path to restore service as quickly as possible. We will provide the next update within 30 minutes.
provider
- identified
We are beginning to see recovery across US regions as our network path adjustments take effect. Connectivity is improving and latency and packet loss are trending back toward normal, though some users may still experience intermittent issues, including with private networking between regions. We are continuing to work toward full service restoration.
provider
- identified
Recovery across US regions is continuing as our network path adjustments hold, and latency and packet loss are trending back toward normal. Some users may still experience intermittent connectivity, including with private networking between regions. Services with attached volumes in US East may experience slower read and write performance as storage recovers. We are continuing to work toward full restoration and will provide the next update within 30 minutes.
provider
- identified
We are continuing to work toward full restoration across US regions. Conditions remain improved from earlier, but the incident is not yet fully resolved, and some users may still see intermittent connectivity, including with private networking between regions, and slower volume performance in US East.
provider
- monitoring
Full connectivity has been restored across US regions. Our network path adjustments are holding, latency and packet loss have returned to normal, and private networking between regions and volume performance in US East have recovered. We are monitoring closely to confirm everything remains stable before marking this incident resolved.
provider
- resolved
This incident has been resolved. A post-mortem of this incident will be published once ready. We apologize for the disruption. If you continue to experience any issues, please reach out at https://station.railway.com.
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-ec82da997c
Is Railway still down?
No, this incident was resolved 2026-07-02 12:01 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
4h 17m, from 2026-07-02 07:44 UTC to 2026-07-02 12:01 UTC, by the times Railway posted.
What was affected?
Railway named US West (California, USA), US East (Virginia, USA), Traffic 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.