Railway incident

DNS Resolution Failures

Resolved after 37 minutes, affecting US East (Virginia, USA) (Networking — Public (US East)) and US West (California, USA) (Networking — Public (US West)) and 1 more, on March 21, 2026.

monitoring Mar 21, 2026, 07:44 PM UTC

We implemented a fix and are currently monitoring the result.

Started
Mar 21, 2026, 07:18 PM UTC
Resolved
Mar 21, 2026, 07:55 PM UTC
Duration
37m
Detected by Pingoru
Mar 21, 2026, 07:18 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

  1. identified Mar 21, 2026, 07:18 PM UTC

    We are aware of DNS resolution failures affecting Railway services. Users may experience failures when accessing their services via Railway-provided domains.

  2. monitoring Mar 21, 2026, 07:44 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Mar 21, 2026, 07:55 PM 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.

Add your stack →