Skip to main content
Railway logo

Is Railway Down?

No — Railway is up

Reachable from all 8 checked regions

Average response time: 217ms

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
299ms
Avg response, 30 days

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

30-day history

76-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 40 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 31 checks
Oct 1: 100.00% uptime, 24 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 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.

cdg
168ms
DNS 43ms TCP 1ms TLS 4ms TTFB 161ms
dfw
171ms
DNS 79ms TCP 6ms TLS 8ms TTFB 144ms
ewr
110ms
DNS 65ms TCP 2ms TLS 5ms TTFB 98ms
fra
223ms
DNS 43ms TCP 8ms TLS 11ms TTFB 184ms
gru
290ms
DNS 151ms TCP 0ms TLS 3ms TTFB 286ms
iad
86ms
DNS 62ms TCP 1ms TLS 3ms TTFB 80ms
jnb
559ms
DNS 173ms TCP 0ms TLS 3ms TTFB 543ms
lax
136ms
DNS 13ms TCP 3ms TLS 4ms TTFB 129ms

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 up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Render
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 — the most recent check ran from 8 of them.
  • 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 up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required