Home
Uptime monitoring Observability AI monitoring Real User Monitoring Incident response Integrations & API AI assistants (MCP) Explore the platform →
Pricing
Uptime Calculator Cron Expression Builder HTTP Status Codes Is It Down? All free tools
Platform Blog About Contact FAQ Partners
Sign in Start free

Is Railway down?

Not fully, but Railway is having problems.

Railway’s status page reports “Railway Recovery after October 21 Incident” (monitoring), backboard.railway.com and railway.com responded from 6 regions, and nobody reported problems in the last hour.

Last checked Since 01:31 UTC (2 h 49 min) Status changed

  • Official statusMinor issuestatus.railway.com
  • Reachable6 of 6 regionsRailway API 6/6 · railway.com 6/6
  • Reports in the last hour0Normal

Incident on Railway’s status pageMonitoring

Railway Recovery after October 21 Incident

Note: This is a recovery update for the October 21 incident, not an announcement of a new incident. Recovery progress Our engineers are continuing work around the clock to harden existing systems to meet market demand. We will provide more information as we have it, while considering the ongoing forensic investigation. New signups New signups remain paused while we prioritize reliability for existing customers during recovery. We do not yet have a date to share for reopening signups. Further updates We will now post updates here once a day, with additional updates as new information becomes…

Updated Started Support & Community — station.railway.com

MongoDB Atlas and Twilio started having problems within 10 minutes of Railway, so the cause may be shared.

Railway’s status page

From status.railway.com. Read at

  • Support & Community — station.railway.com RailwayDegraded
  • Dashboard — railway.com RailwayOperational
  • API — backboard.railway.com RailwayOperational
  • Dev Studio — dev.new RailwayOperational
  • Logs ObservabilityOperational
  • Metrics ObservabilityOperational
  • Registration DomainsOperational
  • Provisioning DomainsOperational
Show all 53 components
  • Login — GitHub AuthenticationOperational
  • Login — Google AuthenticationOperational
  • Login — Emails AuthenticationOperational
  • Login — Railway OAuth AuthenticationOperational
  • Payments & BillingOperational
  • Builds US East (Virginia, USA)Operational
  • Deployments US East (Virginia, USA)Operational
  • Compute US East (Virginia, USA)Operational
  • Storage Buckets US East (Virginia, USA)Operational
  • Networking — Public US East (Virginia, USA)Operational
  • Networking — Private US East (Virginia, USA)Operational
  • Networking — Outbound Static IPs US East (Virginia, USA)Operational
  • Sandboxes US East (Virginia, USA)Operational
  • Storage US East (Virginia, USA)Operational
  • Builds US West (California, USA)Operational
  • Deployments US West (California, USA)Operational
  • Compute US West (California, USA)Operational
  • Storage Buckets US West (California, USA)Operational
  • Networking — Public US West (California, USA)Operational
  • Networking — Private US West (California, USA)Operational
  • Networking — Outbound Static IPs US West (California, USA)Operational
  • Sandboxes US West (California, USA)Operational
  • Storage US West (California, USA)Operational
  • Builds EU West (Amsterdam, Netherlands)Operational
  • Deployments EU West (Amsterdam, Netherlands)Operational
  • Compute EU West (Amsterdam, Netherlands)Operational
  • Storage Buckets EU West (Amsterdam, Netherlands)Operational
  • Networking — Public EU West (Amsterdam, Netherlands)Operational
  • Networking — Private EU West (Amsterdam, Netherlands)Operational
  • Networking — Outbound Static IPs EU West (Amsterdam, Netherlands)Operational
  • Sandboxes EU West (Amsterdam, Netherlands)Operational
  • Storage EU West (Amsterdam, Netherlands)Operational
  • Builds Southeast Asia (Singapore)Operational
  • Deployments Southeast Asia (Singapore)Operational
  • Compute Southeast Asia (Singapore)Operational
  • Storage Buckets Southeast Asia (Singapore)Operational
  • Networking — Public Southeast Asia (Singapore)Operational
  • Networking — Private Southeast Asia (Singapore)Operational
  • Networking — Outbound Static IPs Southeast Asia (Singapore)Operational
  • Sandboxes Southeast Asia (Singapore)Operational
  • Storage Southeast Asia (Singapore)Operational
  • GitHub — Auto-Deploys External & Third-Party IntegrationsOperational
  • Image Registry — Dockerhub External & Third-Party IntegrationsOperational
  • Image Registry — GitHub (GHCR) External & Third-Party IntegrationsOperational
  • Package Registry — npm External & Third-Party IntegrationsOperational

Not working for me

Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.

Email me when Railway is down or back

One email when it goes down and one when it’s back. No account, and every email has a one-click unsubscribe.

We use your address only for these alerts. Privacy

Last 24 hours

2 h 50 min with problems in the last 24 hours, median response 228 ms, and 0 reports.

Status
Response time
500 ms0
Reports
4
06:0012:0018:0000:00UTC
  • Operational
  • Degraded
  • Partial outage
  • Major outage
  • No data
  • Reachability check (backboard.railway.com)
  • Official incident

By region

RegionRailway API backboard.railway.comrailway.com railway.com
N. Virginia us-east-1400 · 111 ms200 · 93 ms
Oregon us-west-2400 · 62 ms200 · 294 ms
Frankfurt eu-central-1400 · 183 ms200 · 200 ms
Singapore ap-southeast-1400 · 195 ms200 · 242 ms
Tokyo ap-northeast-1400 · 132 ms200 · 770 ms
São Paulo sa-east-1400 · 195 ms200 · 296 ms

Two regions check Railway every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check

Last 90 days

We have checked Railway ourselves since Oct 28, 2026. Earlier days come from its status page.

Jul 31, 2026Today

30 days with problems in the last 90 days.

Recent incidents

Incidents: 20 in the last 30 days and 34 in the last 90, lasting a median of 1 h 19 min.

  1. TLS certificates not generatingMajor outage44 min
  2. Railway Recovery after October 21 IncidentDegradedOngoing
  3. Degraded snapshot upload latencyDegraded12 h 18 min
  4. Some deployments failing in EU WestDegraded1 h 19 min
  5. Clarification: Recent Oct 24 API key revocations are precautionaryDegraded16 h 29 min
  6. station.railway.com is unavailableDegraded3 days
  7. Railway Platform OutageMajor outage2 days
  8. Builds paused for Free, Trial and Hobby workspacesDegraded1 min
  9. New builds are temporarily pausedMajor outage3 h 52 min
  10. Builds are taking longer than usualDegraded47 min

Full Railway outage history

If Railway isn’t working for you

Railway is a cloud platform for deploying apps, databases and background services from a repository or Docker image with little configuration.

Common Railway errors

ErrorWhat it meansUsuallyWhat to do
Application failed to respondRailway's proxy could not get a response from your app, usually because it is not listening on the right host or port.Your sideListen on 0.0.0.0 and the PORT variable, and check the domain's target port. Source
No start command could be foundRailway could not detect how to start your application.Your sideSet a start command in the service settings or add one to your project. Source
ENOTFOUND redis.railway.internalYour app could not resolve the private network hostname for Redis, most often because the ioredis client only does IPv4 lookups.Your sideConfigure ioredis (or BullMQ) for dual-stack lookups as Railway's docs describe. Source
405 Method Not AllowedYour request used HTTP; Railway redirects it to HTTPS with a 301, and clients typically change a POST into a GET when following it.Your sideCall your app over HTTPS. Source

Is it just you?

  1. Check the deploy logs first: most Railway errors name a build, start or port problem in your service.
  2. Make sure your app listens on 0.0.0.0 and the PORT variable Railway provides.
  3. If several services fail at once with no deploys, check status.railway.com.
  4. Try the service's railway.app domain as well as your custom domain to rule out DNS.

Alternatives to Railway

Questions

Railway's docs say the most common cause is the app not listening on the correct host or port, or a wrong target port on the domain. Heavy load can also cause it.

If the Railway dashboard works and other services respond, the issue is usually your service. Platform incidents are posted at status.railway.com.

Sources: docs.railway.com, docs.railway.com, status.railway.com

Do you depend on Railway?

Get alerted when Railway breaks your app.

If your product or your team depends on Railway, its outage is your outage, and your users will blame you, not Railway. Point a Site Qwality monitor at the Railway endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.

Monitor Railway free Free plan checks every 5 minutes · no credit card

Is something else down?

See every service How we check