Railway incident

Brief disruption to edge network connectivity. Some users may have experienced intermittent issues reaching their services for a few minutes.

Resolved after 3 minutes, affecting US East (Virginia, USA) (Networking — Public (US East)) and US West (California, USA) (Networking — Public (US West)) and 1 more, on October 16, 2025.

resolved Oct 16, 2025, 08:53 PM UTC

This incident has been resolved and the corresponding incident report can be viewed [here](https://blog.railway.com/p/incident-report-oct-16th-2025)

Started: Oct 16, 2025, 08:50 PM UTC
Resolved: Oct 16, 2025, 08:53 PM UTC
Duration: 3m
Detected by Pingoru: Oct 16, 2025, 08:50 PM UTC

Affected components

US East (Virginia, USA) (Networking — Public (US East))US West (California, USA) (Networking — Public (US West))EU West (Amsterdam, Netherlands) (Networking — Public (EU West))Southeast Asia (Singapore) (Networking — Public (Southeast Asia))

Update timeline

investigating Oct 16, 2025, 08:50 PM UTC

A memory spike in our routing service caused it to become unresponsive, resulting in intermittent failures for HTTP and TCP traffic between 20:50-20:53 UTC. Users may have experienced connection timeouts or inability to reach their services during this period.
resolved Oct 16, 2025, 08:53 PM UTC

This incident has been resolved and the corresponding incident report can be viewed [here](https://blog.railway.com/p/incident-report-oct-16th-2025)

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.