Skip to content

Outage tracker / Railway

Is Railway down?

I'm having a problem

Vendor reports an incidentWhat Railway reports

Railway reports an incident on its status page: Railway Platform Outage.

Impact: critical. Since 2026-10-21 07:24 UTC.

Latest update, 2026-10-22 19:42 UTC: There is no change since our last update. New signups remain temporarily paused while we focus on existing customers. Builds and deployments for Pro and Enterprise workspaces are running normally, and enabling builds for Hobby remains our current focus. Free and Trial will follow after Hobby. We will provide another update by 20:30 UTC at the latest.

Railway's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Railway pass from all 10 regions we check.

As of Oct 22, 2026, 8:04 PM UTC, RealUptime's checks of Railway passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 8:04 PM UTC
US-East1041 msChecks passing
US-West1325 msChecks passing
Europe526 msChecks passing
Asia-Pacific1330 msChecks passing
US-Central160 msChecks passing
Canada185 msChecks passing
UK202 msChecks passing
Southeast Asia276 msChecks passing
Australia378 msChecks passing
South America1333 msChecks passing
their status pagetheir claim, not our reading

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

Railway response time, by region

US-East
1.6sp95 · 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-09-23 UTC: p95 829ms2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 845ms2026-09-26 UTC: p95 763ms2026-09-27 UTC: p95 629ms2026-09-28 UTC: p95 520ms2026-09-29 UTC: p95 666ms2026-09-30 UTC: p95 646ms2026-10-01 UTC: p95 622ms2026-10-02 UTC: p95 590ms2026-10-03 UTC: p95 549ms2026-10-04 UTC: p95 497ms2026-10-05 UTC: p95 487ms2026-10-06 UTC: p95 427ms2026-10-07 UTC: p95 539ms2026-10-08 UTC: p95 567ms2026-10-09 UTC: p95 773ms2026-10-10 UTC: p95 693ms2026-10-11 UTC: p95 601ms2026-10-12 UTC: p95 471ms2026-10-13 UTC: p95 569ms2026-10-14 UTC: p95 607ms2026-10-15 UTC: p95 625ms2026-10-16 UTC: p95 498ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
US-West
1.7sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 730ms2026-09-24 UTC: p95 923ms2026-09-25 UTC: p95 865ms2026-09-26 UTC: p95 975ms2026-09-27 UTC: p95 905ms2026-09-28 UTC: p95 838ms2026-09-29 UTC: p95 644ms2026-09-30 UTC: p95 657ms2026-10-01 UTC: p95 557ms2026-10-02 UTC: p95 687ms2026-10-03 UTC: p95 690ms2026-10-04 UTC: p95 181ms2026-10-05 UTC: p95 297ms2026-10-06 UTC: p95 292ms2026-10-07 UTC: p95 461ms2026-10-08 UTC: p95 489ms2026-10-09 UTC: p95 526ms2026-10-10 UTC: p95 499ms2026-10-11 UTC: p95 546ms2026-10-12 UTC: p95 487ms2026-10-13 UTC: p95 626ms2026-10-14 UTC: p95 372ms2026-10-15 UTC: p95 335ms2026-10-16 UTC: p95 480ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
Europe
705msp95 · 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-09-23 UTC: p95 635ms2026-09-24 UTC: p95 827ms2026-09-25 UTC: p95 752ms2026-09-26 UTC: p95 518ms2026-09-27 UTC: p95 572ms2026-09-28 UTC: p95 555ms2026-09-29 UTC: p95 499ms2026-09-30 UTC: p95 457ms2026-10-01 UTC: p95 537ms2026-10-02 UTC: p95 617ms2026-10-03 UTC: p95 626ms2026-10-04 UTC: p95 613ms2026-10-05 UTC: p95 675ms2026-10-06 UTC: p95 615ms2026-10-07 UTC: p95 659ms2026-10-08 UTC: p95 416ms2026-10-09 UTC: p95 454ms2026-10-10 UTC: p95 396ms2026-10-11 UTC: p95 379ms2026-10-12 UTC: p95 440ms2026-10-13 UTC: p95 431ms2026-10-14 UTC: p95 634ms2026-10-15 UTC: p95 555ms2026-10-16 UTC: p95 378ms2026-10-17 UTC: p95 819ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 937ms2026-10-21 UTC: p95 507ms2026-10-22 UTC: p95 705ms
Sep 23Oct 7Oct 22
Asia-Pacific
2.0sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.8s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 741ms2026-10-02 UTC: p95 718ms2026-10-03 UTC: p95 649ms2026-10-04 UTC: p95 617ms2026-10-05 UTC: p95 660ms2026-10-06 UTC: p95 641ms2026-10-07 UTC: p95 646ms2026-10-08 UTC: p95 645ms2026-10-09 UTC: p95 601ms2026-10-10 UTC: p95 648ms2026-10-11 UTC: p95 634ms2026-10-12 UTC: p95 600ms2026-10-13 UTC: p95 573ms2026-10-14 UTC: p95 708ms2026-10-15 UTC: p95 712ms2026-10-16 UTC: p95 701ms2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 2.0s
Sep 23Oct 7Oct 22
US-Central
469msp95 · 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-23 UTC: p95 849ms2026-09-24 UTC: p95 957ms2026-09-25 UTC: p95 822ms2026-09-26 UTC: p95 839ms2026-09-27 UTC: p95 855ms2026-09-28 UTC: p95 734ms2026-09-29 UTC: p95 692ms2026-09-30 UTC: p95 707ms2026-10-01 UTC: p95 608ms2026-10-02 UTC: p95 663ms2026-10-03 UTC: p95 609ms2026-10-04 UTC: p95 593ms2026-10-05 UTC: p95 676ms2026-10-06 UTC: p95 680ms2026-10-07 UTC: p95 611ms2026-10-08 UTC: p95 630ms2026-10-09 UTC: p95 572ms2026-10-10 UTC: p95 567ms2026-10-11 UTC: p95 582ms2026-10-12 UTC: p95 579ms2026-10-13 UTC: p95 542ms2026-10-14 UTC: p95 387ms2026-10-15 UTC: p95 406ms2026-10-16 UTC: p95 672ms2026-10-17 UTC: p95 832ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 469ms
Sep 23Oct 7Oct 22
Canada
456msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 811ms2026-09-24 UTC: p95 882ms2026-09-25 UTC: p95 901ms2026-09-26 UTC: p95 853ms2026-09-27 UTC: p95 666ms2026-09-28 UTC: p95 740ms2026-09-29 UTC: p95 706ms2026-09-30 UTC: p95 812ms2026-10-01 UTC: p95 747ms2026-10-02 UTC: p95 597ms2026-10-03 UTC: p95 712ms2026-10-04 UTC: p95 504ms2026-10-05 UTC: p95 567ms2026-10-06 UTC: p95 554ms2026-10-07 UTC: p95 463ms2026-10-08 UTC: p95 510ms2026-10-09 UTC: p95 536ms2026-10-10 UTC: p95 482ms2026-10-11 UTC: p95 444ms2026-10-12 UTC: p95 463ms2026-10-13 UTC: p95 477ms2026-10-14 UTC: p95 396ms2026-10-15 UTC: p95 368ms2026-10-16 UTC: p95 602ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 416ms2026-10-22 UTC: p95 456ms
Sep 23Oct 7Oct 22
UK
654msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 838ms2026-09-24 UTC: p95 930ms2026-09-25 UTC: p95 932ms2026-09-26 UTC: p95 750ms2026-09-27 UTC: p95 733ms2026-09-28 UTC: p95 748ms2026-09-29 UTC: p95 849ms2026-09-30 UTC: p95 888ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 947ms2026-10-03 UTC: p95 926ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 992ms2026-10-06 UTC: p95 913ms2026-10-07 UTC: p95 927ms2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 946ms2026-10-10 UTC: p95 855ms2026-10-11 UTC: p95 866ms2026-10-12 UTC: p95 907ms2026-10-13 UTC: p95 833ms2026-10-14 UTC: p95 812ms2026-10-15 UTC: p95 894ms2026-10-16 UTC: p95 978ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 285ms2026-10-22 UTC: p95 654ms
Sep 23Oct 7Oct 22
Southeast Asia
474msp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 2.1s2026-09-24 UTC: p95 2.1s2026-09-25 UTC: p95 2.1s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 2.2s2026-09-29 UTC: p95 2.2s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.6s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 772ms2026-10-15 UTC: p95 746ms2026-10-16 UTC: p95 679ms2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 474ms
Sep 23Oct 7Oct 22
Australia
1.5sp95 · 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-23 UTC: p95 2.3s2026-09-24 UTC: p95 2.4s2026-09-25 UTC: p95 2.0s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 2.2s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 960ms2026-10-05 UTC: p95 938ms2026-10-06 UTC: p95 702ms2026-10-07 UTC: p95 805ms2026-10-08 UTC: p95 914ms2026-10-09 UTC: p95 966ms2026-10-10 UTC: p95 982ms2026-10-11 UTC: p95 960ms2026-10-12 UTC: p95 927ms2026-10-13 UTC: p95 968ms2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 873ms2026-10-16 UTC: p95 578ms2026-10-17 UTC: p95 448ms2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s
Sep 23Oct 7Oct 22
South America
2.4sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 842ms2026-10-15 UTC: p95 930ms2026-10-16 UTC: p95 655ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.4s
Sep 23Oct 7Oct 22

Check your own site while you wait on Railway

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 we measured, function by function

Railway answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Railway reports an incident on its status page, and again when it reports it resolved.

Get an email when Railway reports an incident

Email me when Railway reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Railway's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1041msstatus code: 400checked: Oct 22, 2026, 8:04 PM 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
      Checks passinglatency: 1325msstatus code: 400checked: Oct 22, 2026, 7:57 PM 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
      Checks passinglatency: 160msstatus code: 400checked: Oct 22, 2026, 7:52 PM 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
      Checks passinglatency: 185msstatus code: 400checked: Oct 22, 2026, 7:51 PM 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
    Checks passinglatency: 1333msstatus code: 400checked: Oct 22, 2026, 7:53 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 526msstatus code: 400checked: Oct 22, 2026, 8:03 PM 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
      Checks passinglatency: 202msstatus code: 400checked: Oct 22, 2026, 7:52 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1330msstatus code: 400checked: Oct 22, 2026, 8:04 PM 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
      Checks passinglatency: 276msstatus code: 400checked: Oct 22, 2026, 7:52 PM 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
      Checks passinglatency: 378msstatus code: 400checked: Oct 22, 2026, 7:52 PM 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 probe events

Railway Platform Outagedeclared on their status page2026-10-21
Builds paused for Free, Trial and Hobby workspaces, 2mdeclared on their status page2026-10-21
New builds are temporarily paused, 3h 52mdeclared on their status page2026-10-20
Builds are taking longer than usual, 48mdeclared on their status page2026-10-13
Central Station not loading for some users, 5mdeclared on their status page2026-10-10
Builds and deploys failing to pull images from Docker Hub, 38mdeclared on their status page2026-10-09
Dashboard loading issues, 35mdeclared on their status page2026-10-05
GitHub-triggered builds are delayed, 1h 18mdeclared on their status page2026-10-05

check 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 check readings and Railway's own claim at the time, side by side.

Full check history for Railway: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Railway uptime by RealUptime's checksLive, from this page's own readings.
[![Railway uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Railway down?", https://realuptime.io/outages/railway. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

secondary
https://railway.app/
secondary
https://status.railway.com/
primaryfunctional: live API
https://backboard.railway.com/graphql/v2
RealUptime is not affiliated with Railway; the name identifies what we checked, 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. At least one endpoint we check for Railway is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.