TL;DR
Railway published four incident reports in five months covering four unrelated failure domains: its own abuse automation, its CDN, a shared control-plane dependency, and its networking and storage layers.
In May, applications running on Railway Metal and AWS became unreachable for hours while the containers themselves stayed healthy. No action on the customer side would have restored service.
Below $5,000/month in spend, there is no contractual response time. Free and Hobby tiers receive a public forum with no guaranteed reply; Pro receives a private thread, typically within 72 hours, with Railway's own documentation explicitly disclaiming any SLO.
The only hard spending cap Railway offers works by taking your workloads offline.
