Railway incident

Outbound networking to Azure timing out.

Resolved after 1 hour 24 minutes, affecting US East (Virginia, USA) (Deployments (US East)), on March 25, 2026.

monitoring Mar 25, 2026, 09:29 PM UTC

The rollback has completed, we are seeing recovery, and are currently monitoring the result.

Started
Mar 25, 2026, 08:23 PM UTC
Resolved
Mar 25, 2026, 09:47 PM UTC
Duration
1h 24m
Detected by Pingoru
Mar 25, 2026, 08:23 PM UTC

Affected components

US East (Virginia, USA) (Deployments (US East))

Update timeline

  1. investigating Mar 25, 2026, 08:23 PM UTC

    We are currently investigating this incident.

  2. identified Mar 25, 2026, 09:17 PM UTC

    We have traced this back to a change rolled out with static IP egress gateways. We have begun the rollbacks and are already seeing recovery.

  3. monitoring Mar 25, 2026, 09:29 PM UTC

    The rollback has completed, we are seeing recovery, and are currently monitoring the result.

  4. resolved Mar 25, 2026, 09:47 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 →