Request timeouts and Service Unavailable responses on Edge Network

What to do

• Check whether you use Railway EU West (Amsterdam, Netherlands), Southeast Asia (Singapore), US East (Virginia, USA), US West (California, USA) 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 3h 55m it lasted.

  Anything that failed between 2026-03-24 23:50 UTC and 2026-03-25 03:45 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. investigatingMar 24, 2026, 11:50 PM UTC

   We are aware of an issue affecting public traffic routing. Users may experience request timeouts or "Service Unavailable" errors when accessing their services. We are actively investigating and will provide updates as we learn more.

   provider

2. identifiedMar 25, 2026, 3:10 AM UTC

   We have identified the root cause and are working on a fix. Users may continue to experience request timeouts or "Service Unavailable" responses when accessing their services. We will provide updates as we make progress.

   provider

3. monitoringMar 25, 2026, 3:20 AM UTC

   A fix has been deployed, and we are monitoring for recovery. Users should see request timeouts and "Service Unavailable" responses subsiding. We will continue to monitor and provide a final update once we confirm stability.

   provider

4. resolvedMar 25, 2026, 3:45 AM 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.