Railway: SLA evidence report
Railway: SLA evidence report
We hold no probe record for Railway: we read its status page, so the only incident record here is what Railway declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents Railway declared
- 12
- On its own status page, in this window.
- Window
- 2026-09-22 to 2026-10-22
- UTC, 30 days.
Sep 23, 2026, 1:24 PM UTC to Sep 23, 2026, 3:13 PM UTC
Builds are slow in EU West, impact minor
Sep 29, 2026, 3:29 PM UTC to Sep 29, 2026, 7:15 PM UTC
API degradation causing slow or stuck deployments, impact minor
Sep 30, 2026, 7:34 AM UTC to Sep 30, 2026, 7:57 AM UTC
Domain routing disruption, impact critical
Oct 3, 2026, 4:55 PM UTC to Oct 3, 2026, 7:33 PM UTC
Services and databases unavailable for some users in US West, impact major
Oct 4, 2026, 2:47 AM UTC to Oct 4, 2026, 6:23 AM UTC
Slow attached storage for some users in US West, impact major
Oct 5, 2026, 2:55 PM UTC to Oct 5, 2026, 4:13 PM UTC
GitHub-triggered builds are delayed, impact minor
Oct 5, 2026, 3:37 PM UTC to Oct 5, 2026, 4:12 PM UTC
Dashboard loading issues, impact minor
Oct 9, 2026, 9:29 PM UTC to Oct 9, 2026, 10:07 PM UTC
Builds and deploys failing to pull images from Docker Hub, impact major
Oct 10, 2026, 1:34 AM UTC to Oct 10, 2026, 1:39 AM UTC
Central Station not loading for some users, impact minor
Oct 13, 2026, 4:12 PM UTC to Oct 13, 2026, 5:00 PM UTC
Builds are taking longer than usual, impact minor
Oct 20, 2026, 5:03 PM UTC to Oct 20, 2026, 8:56 PM UTC
New builds are temporarily paused, impact critical
Oct 21, 2026, 7:24 AM UTC to still listed as live
Railway Platform Outage, impact critical
Methodology
These incidents come from Railway's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit Railway owes, if any, is decided under its own SLA.