Railway down for 8 hours – PHP?

This incident has been resolved. Canvas loading and build performance are back to normal and have been stable. Thank you for your patience while we worked through this.

March99.82% uptime

Unauthenticated pages erroneously cached12:20 PM

Dashboard failing to load.7:38 AM

Increased latency on the EU-West Edge.8:46 PM

Railway Dashboard Load Times Impacted3:55 PM

Outbound networking to Azure timing out.8:23 PM

Request timeouts and Service Unavailable responses on Edge Network 11:50 PM

Request timeouts and Service Unavailable responses on Edge Network 11:50 PM

We're currently experiencing elevated latency in our EU-West region6:54 PM

Connectivity issues in EU West (Amsterdam)11:15 PM

DNS Resolution Failures7:18 PM

Degraded Performance in EU West2:12 PM

Degraded network capacity on a single host3:30 AM

Suspected hardware failure affecting a subset of deployments in EU West10:57 AM

Outbound networking issues for a subset of hosts7:34 AM

Issues with networking on a subset of hosts9:27 AM

Logs loading slowly3:25 PM

Deployment slowness3:19 PM

Deployments stuck10:16 PM

Deployments may fail to go out3:26 PM

Dashboard may fail to load for some people4:41 PM

Degraded performance on public networking9:36 AM

Issue with deployments11:05 PM

Issue with deployments11:05 PM

Dashboard slow to load6:18 PM

Slow build and deployment times5:38 PM

Elevated error rates on Edge Network8:43 PM

31Tue

30Mon

Unauthenticated pages erroneously cached12:20 UTC

This incident has been resolved. A postmortem is available at https://blog.railway.com/p/incident-report-march-30-2026-accidental-cdn-caching.