Elevated latency for some services routing through US West

What to do

• Check whether you use Railway US West (California, 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 22m it lasted.

  Anything that failed between 2026-06-03 23:17 UTC and 2026-06-04 00:39 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

1. investigatingJun 3, 2026, 11:17 PM UTC

   We are aware of elevated latency affecting HTTP requests routed through our US West (Los Angeles) edge. Apps and services whose traffic enters through this region may see slow responses or timeouts. We are actively investigating the root cause and will provide updates as we learn more.

   provider

2. monitoringJun 4, 2026, 12:08 AM UTC

   We have implemented a mitigation and are monitoring this incident. Due to DNS caching and connection closing, some users may take a few minutes to see improvement.

   provider

3. resolvedJun 4, 2026, 12:39 AM UTC

   The issue affecting elevated latency for services routing through our US West (Los Angeles) edge has been resolved. We identified the cause as an issue with our edge location in Los Angeles and implemented a mitigation. We apologize for any inconvenience. If you continue to experience issues, please contact support 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.