Railway incident

Degraded performance on public networking

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

Update timeline

  1. resolved Mar 05, 2026, 09:36 AM UTC

    Type: Incident Duration: 15 minutes Affected Components: Southeast Asia (Metal / Singapore), EU West (Metal / Amsterdam, Netherlands), TCP Proxy (Metal), , US East (Metal / Virginia, USA), US West (Metal / California, USA), Edge Network (Railway Metal) → Mar 5, 09:36:58 GMT+0 - Identified - We are working on a fix for network degradation on the railway edge. Mar 5, 09:50:20 GMT+0 - Monitoring - We've applied a fix and are seeing recovery across all regions. Mar 5, 09:52:00 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