Railway incident

DNS resolution is failing for some domains.

Resolved after 6 hours 1 minute, affecting US East (Virginia, USA) (Networking — Public (US East)) and US West (California, USA) (Networking — Public (US West)) and 1 more, on February 20, 2026.

monitoring Feb 20, 2026, 08: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.

Started: Feb 20, 2026, 06:24 PM UTC
Resolved: Feb 21, 2026, 12:25 AM UTC
Duration: 6h 1m
Detected by Pingoru: Feb 20, 2026, 06:24 PM UTC

Affected components

US East (Virginia, USA) (Networking — Public (US East))US West (California, USA) (Networking — Public (US West))EU West (Amsterdam, Netherlands) (Networking — Public (EU West))Southeast Asia (Singapore) (Networking — Public (Southeast Asia))

Update timeline

investigating Feb 20, 2026, 06:24 PM UTC

We are currently investigating this incident.
monitoring Feb 20, 2026, 06:30 PM UTC

We implemented a fix and are currently monitoring the result.
monitoring Feb 20, 2026, 07:21 PM UTC

Cloudflare has identified an issue affecting DNS connectivity.
monitoring Feb 20, 2026, 08: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.
resolved Feb 21, 2026, 12:25 AM UTC

This incident has been resolved.

Your product runs on more than Railway

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.