A subset of domains are failing with a 503 error page.

What to do

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

  Anything that failed between 2026-02-21 05:34 UTC and 2026-02-21 06:55 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 5

1. investigatingFeb 21, 2026, 5:34 AM UTC

   We are currently investigating this incident. Some users may see an error page with "Error 503".

   provider

2. identifiedFeb 21, 2026, 5:56 AM UTC

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

   provider

3. identifiedFeb 21, 2026, 6:07 AM UTC

   We are continuing to work on a fix for this incident. Some users may see a 429 error as a result.

   provider

4. monitoringFeb 21, 2026, 6:29 AM UTC

   We implemented a fix and are currently monitoring the result.

   provider

5. resolvedFeb 21, 2026, 6:55 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.