Railway Outage History

Railway experienced outbound networking timeouts to Azure services due to a problematic change involving static IP egress gateways. The incident lasted 1.4 hours and was resolved by rolling back the problematic change, with recovery confirmed during monitoring.

Railway experienced a minor service incident due to a Dockerhub Registry outage that caused Docker image pulls from Dockerhub to fail. The outage lasted approximately 1.2 hours and was resolved. The incident was classified as minor impact to Railway's services.

A certificate discrepancy between Fastly and Railway caused SAN (Subject Alternative Name) errors that made certificate provisioning inoperable for some customer domains. The issue was identified as incorrect domain configuration, and customers were advised to re-add their domains as a workaround. Manual workarounds successfully restored access while the team worked with their upstream vendor to implement domain forwarding to prevent similar misconfigurations.

The Railway dashboard experienced slow load times for 12 minutes on March 25, 2026. Performance mitigations were deployed to Railway.com to resolve the connectivity issues. Users experiencing ongoing application connectivity problems were directed to submit requests through station.railway.com.

Railway's edge network experienced a public traffic routing issue that caused request timeouts and Service Unavailable errors for users accessing their services, with users reporting inability to load railway.com or deploy applications. The incident lasted 2.1 hours before the root cause was identified and a fix was deployed. The service was restored and monitored for stability after the fix implementation.

Railway experienced elevated latency in their EU-West region for 16 minutes. The engineering team implemented a fix and monitored the results to resolve the performance issues.

Railway experienced connectivity issues in the EU West (Amsterdam) region for 24 minutes, causing users to encounter connection failures and intermittent errors when accessing their services. The team identified the source of the problem and applied a fix, then monitored the system to ensure stability was restored.

DNS resolution failures affected Railway services for 20 minutes, preventing users from accessing their applications through Railway-provided domains. The issue was identified and a fix was implemented, with the service returning to normal operation under monitoring.

Railway experienced degraded performance in the EU West region for 2.2 hours, causing slow builds, delayed container creation, and elevated response times for users. The team identified the root cause within 37 minutes and implemented a fix, then monitored the system to ensure resolution.

A railway service experienced degraded network capacity on a single host for 28 minutes. The incident was classified as minor and was resolved after implementing a fix. The service is now being monitored to ensure the resolution remains stable.