DNS resolution is failing for some domains.

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 6h 2m it lasted.

  Anything that failed between 2026-02-20 18:24 UTC and 2026-02-21 00:25 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 20, 2026, 6:24 PM UTC

   We are currently investigating this incident.

   provider

2. monitoringFeb 20, 2026, 6:30 PM UTC

   We implemented a fix and are currently monitoring the result.

   provider

3. monitoringFeb 20, 2026, 7:21 PM UTC

   Cloudflare has identified an issue affecting DNS connectivity.

   provider

4. monitoringFeb 20, 2026, 8:17 PM UTC

   We are seeing full recovery for all Railway domains since 18:30 UTC. Cloudflare has indicated there should be no further impact, and we are continuing to monitor.

   provider

5. resolvedFeb 21, 2026, 12:25 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.