Railway Outage History

Railway's Dashboard experienced loading failures for some users during a 16-minute incident. The issue was identified and a fix was implemented, with the service team monitoring the resolution to ensure stability.

Railway experienced network degradation on their edge infrastructure for 20 minutes. The issue affected public networking performance across all regions. The team applied a fix and confirmed recovery was observed across all regions.

Railway experienced deployment slowdowns that led to a temporary suspension of free, trial, and hobby plan deployments for approximately 1.1 hours. The team identified the root cause, implemented a fix, and gradually restored service by first catching up with the deployment queue before re-enabling non-pro deployments. All deployment systems were fully recovered with hobby, free, and trial deployments restored to normal operation.

Railway's dashboard experienced significantly slower than normal load times, causing delays for users navigating railway.com. The incident lasted 58 minutes, during which the team identified the root cause and deployed a fix. The service was restored and monitored to confirm full recovery.

Railway experienced slow build and deployment times that initially affected the EU West (Amsterdam) region and later expanded to impact deployments across all regions for 1.7 hours. Users experienced significantly longer completion times for their builds and deployments during this period. The issue was identified and resolved through a fix deployment, with build and deployment times returning to normal.

Railway experienced a service disruption affecting some customer requests in the Asia region for 12 minutes. The issue was related to TCP Proxy functionality, which was subsequently restored. The team monitored the service health to ensure full recovery before marking the incident resolved.

Railway's edge network experienced elevated error rates for 3.7 hours, causing degraded service performance. The issue was quickly identified and a fix was implemented within minutes of detection. The incident was resolved and monitored to ensure stability was restored.

Railway experienced a 3-hour incident where builds and deployments were processing slowly, creating a significant backlog. During the incident, Railway temporarily paused builds for Free, Trial, and Hobby tier users to help clear the queue before gradually re-enabling them. The team implemented a fix and worked through the accumulated backlog of queued builds and deployments.