Skip to main content

Is Railway Down?

No — Railway is up

Reachable from all 8 checked regions

Average response time: 227ms

Last checked · checks run every 6 hours

Official status page: https://status.railway.com

Railway uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
160ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 25 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

25-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: 100.00% uptime, 16 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 30 checks
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 31 checks
Aug 5: 100.00% uptime, 24 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 38 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 31 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 40 checks
Aug 19: 100.00% uptime, 39 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
33ms
DNS 0ms TCP 2ms TLS 8ms TTFB 16ms
arn
272ms
DNS 0ms TCP 25ms TLS 29ms TTFB 135ms
bom
482ms
DNS 1ms TCP 57ms TLS 63ms TTFB 180ms
cdg
16ms
DNS 0ms TCP 1ms TLS 4ms TTFB 7ms
dfw
123ms
DNS 0ms TCP 6ms TLS 9ms TTFB 86ms
sin
16ms
DNS 0ms TCP 1ms TLS 4ms TTFB 8ms
sjc
15ms
DNS 0ms TCP 1ms TLS 3ms TTFB 6ms
syd
818ms
DNS 0ms TCP 99ms TLS 102ms TTFB 301ms
yyz
61ms
DNS 0ms TCP 0ms TLS 3ms TTFB 54ms

What Railway does

Railway is a developer platform that deploys applications, databases and background workers straight from a Git repository, handling builds, networking, domains and scaling. Teams run production APIs on it as well as smaller projects, so an incident can affect both the services they host there and the dashboard they would otherwise use to investigate.

What an outage looks like

Deployments queue without ever starting, or fail partway through the build step with no useful error. The dashboard loads its shell but never renders project data, and logs and metrics stop updating while the deployed application carries on serving traffic normally. Custom domains can stop resolving or begin serving certificate errors, and provisioning a new service or database hangs indefinitely.

What to do about it

Check status.railway.com, which reports the dashboard at railway.com, the API at backboard.railway.com, observability, logs, metrics, domains, registration and provisioning separately. Railway states the page covers incidents with significant, widespread impact and points smaller or isolated reports at station.railway.com. Confirm whether your deployed service is still answering requests before redeploying, because a control-plane fault often leaves running workloads untouched.

Is it down for everyone, or just you?

If this page says Railway is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

R
Render
Fly.io
Fly.io
Vercel
Vercel
DigitalOcean
DigitalOcean

Railway outage FAQ

Is my app down or just the Railway dashboard?
Request your application's public URL directly, bypassing the dashboard entirely. Railway separates the dashboard and API from the runtime, and the most common shape of incident leaves deployed services answering traffic while the control plane is unreachable. If your URL responds, your users are unaffected and the only thing you have lost is the ability to deploy and inspect.
Do queued deployments resume after an outage?
Builds that were queued generally start once the platform recovers, but a build interrupted midway usually needs triggering again. The riskier case is a deployment that partly applied, where the new version is live without the configuration intended to accompany it. Verify which version is actually serving after recovery rather than trusting the dashboard's last known state.
Does a Railway outage take my database down?
Not necessarily. Provisioning is listed apart from the running services, so creating a new database can fail while existing ones keep accepting connections. A database that has genuinely become unreachable while your application is healthy usually shows up as connection errors in the application logs, which are themselves a separate component that may not be updating during the incident.
Why is nothing on the status page when I have a problem?
Railway limits the page to incidents with significant, widespread user impact and says so on it, so a fault affecting one project, one region or a handful of accounts is not published there. The documented route for those is station.railway.com, its community and support site, which is also where isolated reports get picked up.
Do logs from an outage arrive later?
Sometimes, and sometimes not at all. Observability, logs and metrics are their own components, and when that pipeline is degraded the data is often dropped rather than buffered. A gap in the log timeline that lines up with a status page incident is usually the collector rather than an application that stopped doing anything, which is worth knowing before debugging the silence.

How we measure this

  • We request Railway's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Railway publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Railway goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required