Railway incident

Issues with networking on a subset of hosts

Minor Resolved View vendor source →
Started
Mar 15, 2026, 09:27 AM UTC
Resolved
Mar 15, 2026, 09:27 AM UTC
Duration
Detected by Pingoru
Mar 15, 2026, 09:27 AM UTC

Update timeline

  1. resolved Mar 15, 2026, 09:27 AM UTC

    Type: Incident Duration: 37 minutes Affected Components: DNS, EU West (Metal / Amsterdam, Netherlands), Traffic, US East (Metal / Virginia, USA), Southeast Asia (Metal / SIngapore), US West (Metal / California, USA), , , Private Networking → Deployments (Railway Metal) → Mar 15, 09:27:36 GMT+0 - Investigating - We are currently investigating failures to reach the internet for a subset of deployments Mar 15, 09:32:21 GMT+0 - Investigating - We were able to confirm impact to be limited to part of the fleet, but to be affecting all networking for affected deployments. Mar 15, 09:42:15 GMT+0 - Identified - We have identified the root cause and are working on a fix Mar 15, 09:52:14 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 15, 10:04:12 GMT+0 - Resolved - This incident has been resolved.

Looking to track Railway downtime and outages?

Pingoru polls Railway's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Railway reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Railway alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Railway for free

5 free monitors · No credit card required