Railway incident

Request timeouts and Service Unavailable responses on Edge Network

Major Resolved View vendor source →
Started
Mar 24, 2026, 11:50 PM UTC
Resolved
Mar 24, 2026, 11:50 PM UTC
Duration
Detected by Pingoru
Mar 24, 2026, 11:50 PM UTC

Update timeline

  1. resolved Mar 24, 2026, 11:50 PM UTC

    Type: Incident Duration: 3 hours and 55 minutes Affected Components: EU West (Metal / Amsterdam, Netherlands), Southeast Asia (Metal / Singapore), , US East (Metal / Virginia, USA), US West (Metal / California, USA), Edge Network (Railway Metal) → Mar 24, 23:50:00 GMT+0 - Investigating - We are aware of an issue affecting public traffic routing. Users may experience request timeouts or "Service Unavailable" errors when accessing their services. We are actively investigating and will provide updates as we learn more. Mar 25, 03:10:33 GMT+0 - Identified - We have identified the root cause and are working on a fix. Users may continue to experience request timeouts or "Service Unavailable" responses when accessing their services. We will provide updates as we make progress. Mar 25, 03:20:26 GMT+0 - Monitoring - A fix has been deployed, and we are monitoring for recovery. Users should see request timeouts and "Service Unavailable" responses subsiding. We will continue to monitor and provide a final update once we confirm stability. Mar 25, 03:45:02 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