Railway incident
Elevated latency for some services routing through US West
Resolved after 1 hour 22 minutes, affecting US West (California, USA) (Networking — Public (US West)), on June 3, 2026.
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.
Affected components
Update timeline
- investigating Jun 03, 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.
- monitoring Jun 04, 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.
- resolved Jun 04, 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.
Your product runs on more than Railway
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services