Public networking traffic may time out.

What to do

• Check whether you use Railway EU West (Amsterdam, Netherlands), Southeast Asia (Singapore), TCP Proxy (Metal), US East (Virginia, USA) and 1 more in apac, eu, 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 2m it lasted.

  Anything that failed between 2026-02-18 13:47 UTC and 2026-02-18 14:48 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. investigatingFeb 18, 2026, 1:47 PM UTC

   We are currently investigating this incident. A subset of users may experience their application returning a 502 error, timing out, or failing to connect to the TCP proxy.

   provider

2. identifiedFeb 18, 2026, 2:07 PM UTC

   We are continuing to work on a fix for this incident.

   provider

3. monitoringFeb 18, 2026, 2:17 PM UTC

   We are seeing full recovery across all public networking pathways.

   provider

4. resolvedFeb 18, 2026, 2:48 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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