Where does this status come from?

From Railway's own status API at https://status.railway.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Railway's words.

How can my agent or app check Railway status?

Fetch https://upbutler.com/status/railway/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"railway"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Railway's?

Add "railway" to the dependencies of your UpButler workspace. When one of your monitors fails while Railway has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Railway down?

Right now

No. Railway is operational.

No incidents reported.

Read from status.railway.com 6 min ago · every 300s

For agents

proceed

Proceed.

GET upbutler.com/status/railway/status.agent.json

MCP: upstream_status {"service":"railway"}

Builds, deployments, networking and databases per region.

What Railway reports

Operational

Taken as is from Railway's own status API. Incident titles and component names below are theirs.

Open status.railway.com

UpButler's independent probe

There is no keyless endpoint of Railway that says anything useful, so UpButler does not probe it. To check your own Railway account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Railway components

53 operational

Railway

Dashboard — railway.comOperational
API — backboard.railway.comOperational
Support & Community — station.railway.comOperational
Dev Studio — dev.newOperational

Observability

LogsOperational
MetricsOperational

Domains

RegistrationOperational
ProvisioningOperational

Authentication

Payments & BillingOperational

US East (Virginia, USA)

BuildsOperational
DeploymentsOperational
ComputeOperational
Storage BucketsOperational
Networking — PublicOperational
Networking — PrivateOperational
Networking — Outbound Static IPsOperational
SandboxesOperational
StorageOperational

US West (California, USA)

BuildsOperational
DeploymentsOperational
ComputeOperational
Storage BucketsOperational
Networking — PublicOperational
Networking — PrivateOperational
Networking — Outbound Static IPsOperational
SandboxesOperational
StorageOperational

EU West (Amsterdam, Netherlands)

BuildsOperational
DeploymentsOperational
ComputeOperational
Storage BucketsOperational
Networking — PublicOperational
Networking — PrivateOperational
Networking — Outbound Static IPsOperational
SandboxesOperational
StorageOperational

Southeast Asia (Singapore)

BuildsOperational
DeploymentsOperational
ComputeOperational
Storage BucketsOperational
Networking — PublicOperational
Networking — PrivateOperational
Networking — Outbound Static IPsOperational
SandboxesOperational
StorageOperational

External & Third-Party Integrations

GitHub — Auto-DeploysOperational
Image Registry — DockerhubOperational
Image Registry — GitHub (GHCR)Operational
Package Registry — npmOperational

Railway incidents, last 90 days

10 finished incidents seen since UpButler started tracking on 2026-10-10, 4 of them rated major or critical by Railway. A typical one lasted 38 min; the longest 3 h 46 min.

Started (UTC)	Incident	Impact	Lasted
2026-10-10 01:34	Central Station not loading for some users	minor	5 min
2026-10-09 21:29	Builds and deploys failing to pull images from Docker Hub	major	38 min
2026-10-05 15:37	Dashboard loading issues	minor	35 min
2026-10-05 14:55	GitHub-triggered builds are delayed	minor	1 h 18 min
2026-10-04 02:47	Slow attached storage for some users in US West	major	3 h 36 min
2026-10-03 16:55	Services and databases unavailable for some users in US West	major	2 h 38 min
2026-10-02 16:53	Potential intermittent connectivity issues	minor	24 min
2026-09-30 15:06	Slow dashboard and auth timeouts	minor	28 min
2026-09-30 07:34	Domain routing disruption	critical	23 min
2026-09-29 15:29	API degradation causing slow or stuck deployments	minor	3 h 46 min

Tell your outage from Railway's

Declare that your project depends on Railway. When one of your monitors fails while Railway has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - railway

Ask before you retry

curl -s https://upbutler.com/status/railway/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "railway",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Railway down right now?: No. As of 2026-10-10 05:07 UTC, Railway is operational. This page reads the status again every 5 minutes.
Where does this status come from?: From Railway's own status API at https://status.railway.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Railway's words.
How can my agent or app check Railway status?: Fetch https://upbutler.com/status/railway/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"railway"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Railway's?: Add "railway" to the dependencies of your UpButler workspace. When one of your monitors fails while Railway has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in hosting and compute

UpButler is not affiliated with Railway. Status and incident text belong to Railway and are read from their public status source; the probe result is UpButler's own measurement.