Elevated latency in US East edge network

What to do

• Check whether you use Railway 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 24m it lasted.

  Anything that failed between 2026-05-04 17:21 UTC and 2026-05-04 17:46 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 4

1. investigatingMay 4, 2026, 5:21 PM UTC

   We are aware of elevated latency affecting our edge network in US East. Requests to services running in this region may take longer than normal to complete. We are actively investigating and we will provide updates as we learn more.

   provider

2. identifiedMay 4, 2026, 5:34 PM UTC

   We have identified the issue affecting US East edge latency and are rolling out a fix. Some users may already see improvement, though latency remains elevated for others. We will continue to provide updates as the fix takes effect.

   provider

3. monitoringMay 4, 2026, 5:39 PM UTC

   We suspect the elevated latency is related to an issue with our upstream CDN layer. As a mitigation, we have removed the affected provider from our edge network and are now seeing performance return to normal. We will continue to monitor before resolving.

   provider

4. resolvedMay 4, 2026, 5:46 PM UTC

   The elevated latency affecting our US East edge network has been resolved. We removed the affected upstream provider, and performance has returned to normal. We apologize for any inconvenience. If you continue to experience issues, please contact us at https://station.railway.com.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.