What is Railway's uptime?

Over the last 90 days, Railway reported 99.43% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.railway.com, each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Railway's uptime history rolling forward in real time.

Has Railway had outages in 2026?

Yes, Railway has had 32 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

When was the last Railway outage?

The most recent Railway incident was "Elevated Build Failure Rate", which started on October 31, 2026 and was resolved on October 31, 2026. Pingoru captured this directly from https://status.railway.com. See the full incident card above for affected components and the update timeline.

How often does Railway have outages?

Based on the last 90 days, Railway averages 10.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components: so you can see the pattern at a glance instead of digging through the vendor's archive.

Where is Railway's status page?

Railway's official status page is https://status.railway.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on, so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Is Railway down right now?

Railway has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment Railway reports a change. Current status is based on 91 tracked services.

How does Pingoru know if Railway is down?

We read https://status.railway.com directly, using Railway's own status page. If the vendor reports an incident, you see it within one check cycle, not after someone manually marks the page as down.

Where can I get notified when Railway has an outage?

Create a free Pingoru account and add Railway as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Railway's status page says the service is up, but I'm having issues. What's wrong?

Three common reasons: • A real Railway incident that hasn't been acknowledged on their public status page yet, vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers. These rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Railway issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Where does Pingoru get the official Railway status?

We use Railway's own status page at https://status.railway.com and cross-reference their homepage (https://www.railway.com). Nothing is read in a way the vendor hasn't explicitly made public. We use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

What does "Degraded" mean?

Railway is reporting degraded performance. Services are up but slower than usual, or a subset of requests is failing.

Is Railway down?

Last checked just now

Current status

Railway has degraded performance

Active incident: Railway Recovery after October 21 Incident

Get alerts when Railway breaks → View Railway outage history →

Free, no credit card

Official status page: status.railway.com
Checked every 5 minutes
91 components tracked

Railway is reporting degraded performance right now (last checked just now). Services are up but slower or partially failing.

Real-time Railway status, recent outages, and incident history: pulled directly from Railway's official status page at status.railway.com every 5 minutes. Pingoru tracks 91 Railway services and has captured 33 incidents in the last 90 days (99.43% uptime). Get email, Slack, Discord, or webhook alerts the moment Railway reports a new incident, free for 3 monitors, no credit card.

Users who monitor Railway also follow these Cloud Infrastructure services:

Genesys Cloud View all 8,000+ providers

Railway uptime 99.43% uptime · past 90 days

Mon Wed Fri

AugSepOctNov

Less More

Active incident 1

Railway Recovery after October 21 Incident

Ongoing ● 6d 10h

Started Oct 26, 2026, 07:12 PM UTC

Support & Community — station.railway.com
Timeline · 5 updates
- monitoring · Oct 26, 2026, 07:12 PM UTC
  
  Note: this is not an announcement of an additional incident. As we work to recover all of our systems after the October 21 Security Incident (https://blog.railway.com/p/preliminary-report-october-security-incident), we will be using this Status Page incident to provide updated information. If you subscribe at the top of page at status.railway.com, you can get new updates as they are posted. We expect to post at least twice a day during the week until all parts of Railway are fully operational or if we decide on an alternate channel for such communication. We have updated our original post with an addendum at https://blog.railway.com/p/preliminary-report-october-security-incident#continuous-updates, and will notify you here of any additional addendums.
- monitoring · Oct 27, 2026, 03:22 AM UTC
  
  Note: this is not an announcement of an additional incident. There is no change since our last update. New signups remain paused while we prioritize reliability for existing customers during recovery. We do not have a date to share yet for re-enabling signups. The latest information remains in our addendum at https://blog.railway.com/p/preliminary-report-october-security-incident#continuous-updates. We will post our next update around 15:00 UTC on October 27.
- monitoring · Oct 27, 2026, 03:19 PM UTC
  
  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 available. Our next scheduled update will be around 16:00 UTC on Wednesday October 28. The latest recovery information is available in the addendum to our incident report on our blog.
- monitoring · Oct 28, 2026, 03:27 PM UTC
  
  Note: This is a recovery update for the October 21 incident, not an announcement of a new incident. We continue to work on restoring new signups while prioritizing reliability for existing customers. New signups remain paused. We’ll continue to post daily recovery and service-status updates here until normal operations are fully restored. For product announcements, please follow our website, blog, and social channels. We’ll post our next update by 16:00 UTC on Thursday, October 29, or sooner if there are meaningful changes.
- monitoring · Oct 29, 2026, 03:45 PM UTC
  
  Note: This is a recovery update for the October 21 incident, not an announcement of a new incident. Work to restore new signups is ongoing, with reliability for existing customers remaining our priority. Signups are still paused, and we do not yet have a reopening date to share. We’ll keep posting daily recovery updates here. Product announcements will be shared through our website, blog, and social channels. Our next update will be posted by 16:00 UTC on Friday, October 30, or sooner if there are meaningful changes.
Latest: Note: This is a recovery update for the October 21 incident, not an announcement of a new incident. Work to restore new signups is ongoing, with reliability for existing customers …

Recent outages & incidents

Past 90 days

Elevated Build Failure Rate

Resolved 39m

Started Oct 31, 2026, 07:53 PM UTC · Resolved Oct 31, 2026, 08:32 PM UTC

Builds (US East)Builds (US West)Builds (EU West)Builds (Southeast Asia)
Timeline · 4 updates
- investigating · Oct 31, 2026, 07:53 PM UTC
  
  We are aware of an issue causing elevated build failure rates across our regions. Users may experience builds failing unexpectedly. We are actively investigating and will provide updates as we learn more. Note: This issue is unrelated to the security incident from October 21st, which has been resolved.
- identified · Oct 31, 2026, 08:12 PM UTC
  
  We have identified the cause of the elevated build failure rate. An upstream storage provider that our build infrastructure depends on is experiencing elevated request timeouts, which is preventing some builds from starting. This affects builds in all regions. We are working with the provider to restore normal service. Builds that failed can be retried; retries may succeed but may also fail until the issue is resolved. We will provide another update as we learn more.
- monitoring · Oct 31, 2026, 08:19 PM UTC
  
  The upstream storage provider has applied a fix, and build failure rates are back to normal as of 20:10 UTC. Builds that failed during this incident can be retried. We are monitoring to confirm full recovery.
- resolved · Oct 31, 2026, 08:32 PM UTC
  
  The elevated build failure rate has been resolved. Builds are processing normally across all regions. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com. Note: This issue is unrelated to the security incident from October 21st, which has been resolved.
Latest: The elevated build failure rate has been resolved. Builds are processing normally across all regions. We apologize for any inconvenience. If you continue to experience issues, plea…
Deployments stuck in initializing

Resolved 1h 27m

Started Oct 28, 2026, 05:49 PM UTC · Resolved Oct 28, 2026, 07:17 PM UTC

Deployments (US East)Deployments (US West)Deployments (EU West)Deployments (Southeast Asia)
Timeline · 2 updates
- identified · Oct 28, 2026, 05:49 PM UTC
  
  We have identified the cause of an issue that causes deployments to become stuck in an initializing state. Users attempting to deploy may experience delays with builds and deployments not progressing. We are actively fixing and will provide updates.
- resolved · Oct 28, 2026, 07:17 PM UTC
  
  Builds and deployments are back to normal. An issue in the system that processes builds caused delays, so we briefly paused new deployments to clear the backlog. Everything queued has now been processed. If a deployment failed during this time, please trigger a redeploy. Still seeing issues? Reach us at https://station.railway.com. Note: This issue is unrelated to the security incident from October 21st, which has been resolved.
Latest: Builds and deployments are back to normal. An issue in the system that processes builds caused delays, so we briefly paused new deployments to clear the backlog. Everything queued …
Builds failing intermittently in US East and EU West

Resolved 2h 15m

Started Oct 28, 2026, 02:56 PM UTC · Resolved Oct 28, 2026, 05:12 PM UTC

Builds (US East)Builds (EU West)
Timeline · 3 updates
- identified · Oct 28, 2026, 02:56 PM UTC
  
  We are aware of an issue causing some builds to fail in EU West and US East. Users may experience build failures or builds not completing successfully. We have identified the cause and will provide updates as we talk to upstream providers to fix. Running services are not affected.
- resolved · Oct 28, 2026, 05:12 PM UTC
  
  The latency issue has abated and things have improved. We are monitoring closely and will update if there's a recurrence.
- postmortem · Oct 28, 2026, 05:15 PM UTC
  
  Build latency occurred due to issues with our upstream storage provider, we have been in touch and this is now resolved.
Latest: Build latency occurred due to issues with our upstream storage provider, we have been in touch and this is now resolved.
Builds failing in US West

Resolved 32m

Started Oct 28, 2026, 10:07 AM UTC · Resolved Oct 28, 2026, 10:40 AM UTC

Builds (US West)
Timeline · 3 updates
- investigating · Oct 28, 2026, 10:07 AM UTC
  
  Builds failing in US West We have identified an issue with our build infrastructure in US West that is causing some builds to fail before any build steps run. Affected builds fail with a "build daemon returned an error" message. We are working on a fix. Running services are not affected. Users in other regions are not affected. If a build fails, redeploying may succeed in the meantime. Note: This issue is unrelated to the security incident from October 21st. No action is needed on your part.
- monitoring · Oct 28, 2026, 10:36 AM UTC
  
  We have identified the cause of the build failures in US West and have applied a fix. Builds should be recovering now. We are monitoring to confirm full recovery. Running services are not affected. If you continue to see build failures, retrying the deployment may succeed in the meantime.
- resolved · Oct 28, 2026, 10:40 AM UTC
  
  The issue causing builds to fail in US West has been resolved. Builds are now completing normally. If a build failed during this incident, redeploying it should now succeed. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.
Latest: The issue causing builds to fail in US West has been resolved. Builds are now completing normally. If a build failed during this incident, redeploying it should now succeed. We apo…
TLS certificates not generating

Resolved 44m

Started Oct 26, 2026, 07:18 PM UTC · Resolved Oct 26, 2026, 08:02 PM UTC

Provisioning
Timeline · 2 updates
- identified · Oct 26, 2026, 07:18 PM UTC
  
  We have received reports and identified the cause of TLS certs not generating for new or changed domains. We are talking to our upstream provider Lets Encrypt about this and will update shortly.
- resolved · Oct 26, 2026, 08:02 PM UTC
  
  We have deployed a fix for the issue and TLS are generating again.
Latest: We have deployed a fix for the issue and TLS are generating again.

See the full Railway outage history

28 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Railway outage history →

Or sign up free to get alerts when Railway breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Railway Status · 91 components checked every 5 minutes

317incidents recorded

143last 12 months

33last 90 days

3 hourstypical duration, 12 months

The longest incident in the last year, Railway Platform Outage on October 21, 2026, ran for 3 days. 3 maintenance windows announced in the same period.

Most affected components, last 12 months

Deployments (EU West)33
Deployments (US East)31
Deployments (US West)30
Deployments (Southeast Asia)28
Dashboard — railway.com24

Latest incidents

Elevated Build Failure Rate October 31, 2026 · 39 minutes · major outage
We are aware of an issue causing elevated build failure rates across our regions. Users may experience builds failing unexpectedly. We are actively…
Deployments stuck in initializing October 28, 2026 · 87 minutes · major outage
We have identified the cause of an issue that causes deployments to become stuck in an initializing state. Users attempting to deploy may experience delays…
Builds failing intermittently in US East and EU West October 28, 2026 · 2 hours · degraded service
We are aware of an issue causing some builds to fail in EU West and US East. Users may experience build failures or builds not completing successfully. We have…

Outage history

Past 90 days · 33 incidents View full outage history →

Elevated Build Failure Rate Resolved

Started Oct 31, 2026, 07:53 PM UTC · Resolved Oct 31, 2026, 08:32 PM UTC · 39m
Deployments stuck in initializing Resolved

Started Oct 28, 2026, 05:49 PM UTC · Resolved Oct 28, 2026, 07:17 PM UTC · 1h 27m
Builds failing intermittently in US East and EU West Resolved

Started Oct 28, 2026, 02:56 PM UTC · Resolved Oct 28, 2026, 05:12 PM UTC · 2h 15m
Builds failing in US West Resolved

Started Oct 28, 2026, 10:07 AM UTC · Resolved Oct 28, 2026, 10:40 AM UTC · 32m
TLS certificates not generating Resolved

Started Oct 26, 2026, 07:18 PM UTC · Resolved Oct 26, 2026, 08:02 PM UTC · 44m
Railway Recovery after October 21 Incident Ongoing

Started Oct 26, 2026, 07:12 PM UTC · ● 6d 10h
Degraded snapshot upload latency Resolved

Started Oct 26, 2026, 11:05 AM UTC · Resolved Oct 26, 2026, 11:43 PM UTC · 12h 38m
Some deployments failing in EU West Resolved

Started Oct 25, 2026, 10:04 PM UTC · Resolved Oct 25, 2026, 11:24 PM UTC · 1h 19m