Deployments may fail to go out

What to do

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

  Anything that failed between 2026-03-09 15:26 UTC and 2026-03-09 16:33 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 7

1. investigatingMar 9, 2026, 3:26 PM UTC

   We're investigating an issue causing a large portion of deployments to error, causing slowdowns across deployments and builds.

   provider

2. identifiedMar 9, 2026, 3:30 PM UTC

   We have identified the root cause of the issue and are working on a fix.

   provider

3. identifiedMar 9, 2026, 3:47 PM UTC

   We are continuing to work on a fix for this incident. New deploys for the hobby, free and trial plans have been paused until a fix is deployed.

   provider

4. identifiedMar 9, 2026, 4:04 PM UTC

   A fix has been pushed and is pending rollout. We're seeing issues with TCP proxy connections, related to this incident.

   provider

5. monitoringMar 9, 2026, 4:24 PM UTC

   We are seeing recovery for deployments. We are continuing to work on a fix for the TCP Proxy:

   provider

6. monitoringMar 9, 2026, 4:26 PM UTC

   We are seeing recovery, and have re-enabled Free, Trial and Hobby deploys.

   provider

7. resolvedMar 9, 2026, 4:33 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.