Skip to content

Outage tracker / Railway

Is Railway down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Railway from all 10 regions we check.

Reachability verified

Last outage: 10 min on Aug 28, 2026 (web surface, from US-East).

our independent probeslive · checked Sep 5, 2026, 2:07 AM UTC
US-East322 msOperational
US-West504 msOperational
Europe460 msOperational
Asia-Pacific870 msOperational
US-Central800 msOperational
Canada269 msOperational
UK302 msOperational
Southeast Asia651 msOperational
Australia1638 msOperational
South America1855 msOperational
their status pagetheir claim, not our reading

Railway publishes no status feed we can read, so the only independent reading here is ours on the left.

Railway response time, by region

US-East
614msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 859ms2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 1.4s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.6s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 1.8s2026-08-29 UTC: p95 1.2s2026-08-30 UTC: p95 1.2s2026-08-31 UTC: p95 1.4s2026-09-01 UTC: p95 1.5s2026-09-02 UTC: p95 1.4s2026-09-03 UTC: p95 1.9s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 614ms
Aug 7Aug 21Sep 5
US-West
553msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 201ms2026-08-23 UTC: p95 406ms2026-08-24 UTC: p95 397ms2026-08-25 UTC: p95 310ms2026-08-26 UTC: p95 774ms2026-08-27 UTC: p95 787ms2026-08-28 UTC: p95 640ms2026-08-29 UTC: p95 804ms2026-08-30 UTC: p95 795ms2026-08-31 UTC: p95 676ms2026-09-01 UTC: p95 678ms2026-09-02 UTC: p95 587ms2026-09-03 UTC: p95 790ms2026-09-04 UTC: p95 683ms2026-09-05 UTC: p95 553ms
Aug 7Aug 21Sep 5
Europe
491msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 267ms2026-08-23 UTC: p95 538ms2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 615ms2026-08-26 UTC: p95 430ms2026-08-27 UTC: p95 648ms2026-08-28 UTC: p95 695ms2026-08-29 UTC: p95 445ms2026-08-30 UTC: p95 513ms2026-08-31 UTC: p95 551ms2026-09-01 UTC: p95 623ms2026-09-02 UTC: p95 639ms2026-09-03 UTC: p95 920ms2026-09-04 UTC: p95 1.0s2026-09-05 UTC: p95 491ms
Aug 7Aug 21Sep 5
Asia-Pacific
948msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 443ms2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 831ms2026-08-26 UTC: p95 1.4s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 1.0s2026-08-29 UTC: p95 888ms2026-08-30 UTC: p95 876ms2026-08-31 UTC: p95 919ms2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 948ms
Aug 7Aug 21Sep 5
US-Central
1.2sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 815ms2026-09-04 UTC: p95 857ms2026-09-05 UTC: p95 1.2s
Aug 7Aug 21Sep 5
Canada
442msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 772ms2026-09-04 UTC: p95 561ms2026-09-05 UTC: p95 442ms
Aug 7Aug 21Sep 5
UK
447msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 477ms2026-09-04 UTC: p95 428ms2026-09-05 UTC: p95 447ms
Aug 7Aug 21Sep 5
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.1s
Aug 7Aug 21Sep 5
Australia
2.7sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.1s2026-09-04 UTC: p95 2.0s2026-09-05 UTC: p95 2.7s
Aug 7Aug 21Sep 5
South America
1.8sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 1.8s
Aug 7Aug 21Sep 5

Is it Railway, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Railway -- it cannot diagnose Railway's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 322msstatus code: 200checked: Sep 5, 2026, 2:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Railway normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 504msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Railway normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 800msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Railway normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 269msstatus code: 200checked: Sep 5, 2026, 2:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Railway normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1855msstatus code: 200checked: Sep 5, 2026, 2:07 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Railway normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 460msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Railway normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 302msstatus code: 200checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Railway normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 870msstatus code: 200checked: Sep 5, 2026, 1:58 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Railway normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 651msstatus code: 200checked: Sep 5, 2026, 1:56 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Railway normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1638msstatus code: 200checked: Sep 5, 2026, 1:55 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Railway normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Railway, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Railway yet, which is not evidence that nothing is wrong.

Recent outages

Partial outage, under our ~10m probe resolutionmeasured by our probes · US-East2026-08-28

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Railway since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Railway covering any window you pick, with our measurements and Railway's own claim at the time, side by side.

Full availability history for Railway: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Railway, and again when they can reach it again. That is our own measurement from ten regions, not Railway's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Railway uptime measured by RealUptimeLive, from this page's own readings.
[![Railway uptime measured by RealUptime](https://realuptime.io/outages/railway/badge.svg?days=30)](https://realuptime.io/outages/railway)
<a href="https://realuptime.io/outages/railway"><img src="https://realuptime.io/outages/railway/badge.svg?days=30" alt="Railway uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Railway's SLA implies, from our measurement

At or above your target

We measured none of downtime for Railway over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

Separately, we measured 9 minutes where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from Railway's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primary
https://railway.app/
secondary
https://status.railway.com/
RealUptime is not affiliated with Railway; the name identifies what we measured, and nothing here speaks for Railway's own team. We send a single web request to Railway from 10 regions on our own schedule and time the response. We do not see inside Railway's systems, do not use an account or real transaction, and are not the same signal Railway's own team has access to. Treat this as one external data point, not a verdict. What we check for Railway proves reachability only: the endpoints above answer, but that does not confirm the underlying product or account features work. Read the full methodology.