Deploys may be delayed to go out

What to do

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

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

1. triageApr 6, 2026, 3:09 PM UTC

   We are currently investigating this issue.

   provider

2. investigatingApr 6, 2026, 3:17 PM UTC

   Triage escalated to incident

   provider

3. identifiedApr 6, 2026, 3:17 PM UTC

   We are currently investigating this issue

   provider

4. identifiedApr 6, 2026, 3:40 PM UTC

   We have paused hobby deploys to alleviate deploy pressure.

   provider

5. monitoringApr 6, 2026, 4:21 PM UTC

   We have unpaused hobby as we are seeing recovery. We are currently monitoring this

   provider

6. resolvedApr 6, 2026, 4:26 PM UTC

   This incident is resolved

   provider

Corrections

None so far.

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