Intermittent connectivity issues with a subset of user workloads

What to do

• Check whether you use Railway Dashboard - railway.com, TCP Proxy (Metal), US East (Virginia, USA), Southeast Asia (Singapore) and 2 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 23m it lasted.

  Anything that failed between 2026-05-22 14:45 UTC and 2026-05-22 15:07 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. investigatingMay 22, 2026, 2:45 PM UTC

   We are investigating reports of intermittent connectivity issues affecting railway.com and user-deployed services. Some users may have experienced SSL handshake failures, 400 errors, or brief unavailability when accessing the platform or their workloads. We are actively investigating the root cause and will provide updates as we learn more.

   provider

2. monitoringMay 22, 2026, 3:02 PM UTC

   We have identified the cause of the connectivity issues and have deployed a fix that is being The affected workload has been isolated and connectivity has recovered. We are continuing to monitor to confirm stability

   provider

3. resolvedMay 22, 2026, 3:07 PM UTC

   We have identified the cause of the connectivity issues and deployed a fix. Connectivity has fully recovered. We apologize for any disruption this caused to your services. Update: Following the initial resolution, a brief spike in HTTP request latency was observed in the EU West region for approximately 1-2 minutes. Users in this region may have experienced slower response times. The issue has subsided.

   provider

Corrections

None so far.

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