Railway - Notice history

All systems operational

Dashboard - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025
100% - uptime

Builders - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 99.83%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Image Registry - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Deploy - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Third-Party: npm Registry - Operational

Third-Party: Github Integrations - Operational

Third Party: Docker Hub - Operational

Third-Party: GitHub Container Registry - Operational

100% - uptime

EU West (europe-west4 / Amsterdam, Netherlands) - Operational

100% - uptime
Feb 2025 · 99.82%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

US East (us-east4 / Virginia, USA) - Operational

100% - uptime
Feb 2025 · 99.82%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

US West (us-west1 / Oregon, USA) - Operational

100% - uptime
Feb 2025 · 99.72%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Southeast Asia (asia-southeast1 / Singapore) - Operational

100% - uptime
Feb 2025 · 99.82%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

US West Metal (us-west2 / California, USA) - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Southeast Asia Metal (asia-southeast2 / SIngapore) - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025
100% - uptime

US West (us-west1 / Oregon, USA) - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 99.93%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

US East (us-east4 / Virginia, USA) - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 99.93%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

EU West (europe-west4 / Amsterdam, Netherlands) - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 99.93%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Southeast Asia (asia-southeast1 / Singapore) - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 99.93%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

TCP Proxy - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 99.98%Apr · 99.93%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025
100% - uptime

DNS - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 99.93%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Traffic - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 99.93%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025
100% - uptime

Logs - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Metrics - Operational

100% - uptime
Feb 2025 · 99.99%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025
100% - uptime

Payments - Operational

100% - uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Notice history

Apr 2025

A single host on Railway GCP US-West has rebooted
  • Resolved
    Resolved

    All applications are operational. A host was rebooted at 17:48 UTC. Most applications recovered by 18:06 UTC and ALL applications recovered by 18:13 UTC.

  • Monitoring
    Monitoring

    Most applications are operational. We're monitoring for ALL applications to become operational before resolving.

  • Identified
    Identified

    Affected deploys are coming back online. Impacted users may see their services re-deployed by Railway.

  • Investigating
    Investigating

    We are failing over deploys from the host to a different host. Impacted users may see their services re-deployed by Railway.

A single host on Railway GCP US-West has rebooted
  • Resolved
    Resolved

    All applications are operational. A host was rebooted at 13:53 UTC. Most applications recovered by 14:03 UTC and ALL applications recovered by 14:10 UTC.

  • Identified
    Identified

    Affected deploys are coming back online. Impacted users may see their services re-deployed by Railway.

  • Investigating
    Investigating

    We are failing over deploys from the host to a different host. Impacted users may see their services re-deployed by Railway.

Degraded Performance on Networking on ALL Regions
  • Resolved
    Resolved

    Our network control plane is fully recovered. Our network control plane experienced networking difficulties between 09:10 UTC and 09:28 UTC.

    A complete incident report is available here: https://blog.railway.com/p/incident-report-april-23-2025

  • Monitoring
    Monitoring

    We are seeing full recovery across the platform, and are closely monitoring the health of our networking control plane.

  • Identified
    Identified

    We've identified the issues with our networking control plane and have implemented a solution. Users should see recovering public and private networking.

  • Investigating
    Investigating

    We're investigating issues with our networking control plane. Users may experience public and private networking difficulties during this period.

Degraded Performance on Edge Network
  • Resolved
    Resolved

    Traffic to our Edge Network is restored and the issue is resolved. Our Edge Network in all Regions was hit with a DoS attack and experienced degraded performance from 22:32 UTC to 22:41 UTC.

  • Monitoring
    Monitoring

    We have implemented a fix and are monitoring the result.

  • Investigating
    Investigating

    We are currently investigating this incident. We are observing degraded performance for all regions on our edge network.

Unavailability of the metal edge network.
  • Resolved
    Resolved

    This incident has been resolved.

    We initially observed degradation at 2025-04-21 19:51:30 UTC.
    Degradation was resolved at 2025-04-21 20:52:30 UTC.

  • Monitoring
    Monitoring

    We have implemented a mitigation and are monitoring.

  • Investigating
    Investigating

    Users may see increased latency or user workloads may be unreachable.

Mar 2025

Some TCP proxy endpoints may be experiencing connectivity issues
  • Resolved
    Resolved

    This incident has been resolved and we're seeing full recovery and have successfully rolled out the revert.

  • Identified
    Identified

    We're reverting a change that has interrupted TCP proxy connectivity to a small subset of workloads still on Runtime V1. Workloads on Runtime V2 are unaffected.

  • Investigating
    Investigating
    Some TCP proxy endpoints may be experiencing connectivity issues
Potential upstream issue causing delayed login via Magic emails. Login via GitHub may be used as a workaround.
  • Resolved
    Resolved
    Login via Magic emails are being delivered timely
  • Investigating
    Investigating
    Potential upstream issue causing delayed login via Magic emails. Login via GitHub may be used as a workaround.
A singular google cloud host is failing over
  • Resolved
    Resolved
    Failover completed
  • Investigating
    Investigating
    A singular google cloud host is failing over
A single host in US West was rebooted due to a kernel failure
  • Resolved
    Resolved
    All workloads have now recovered
  • Monitoring
    Monitoring
    We are monitoring as workloads come back online
  • Investigating
    Investigating
    A single host in US West was rebooted due to a kernel failure
Potential upstream GitHub issue with "Failed to clone" for small subset of builds. We're looking into it
  • Resolved
    Resolved
    We've deployed a permanent fix and consider the issue resolved.
  • Monitoring
    Monitoring
    We have rolled out a temporary fix and are working on a permanent one.
  • Update
    Update
    We continue to investigate the incident. It occurs on a very small % of builds and retries resolve
  • Investigating
    Investigating
    Potential upstream GitHub issue with "Failed to clone" for small subset of builds. We're looking into it

Feb 2025

GitHub Single Sign-On Temporarily Unavailable
  • Resolved
    Resolved

    GitHub Single Sign-On is working as intended again.

  • Monitoring
    Monitoring

    We have merged a fix and are monitoring the result.

  • Identified
    Identified

    We have identified the issue and are working on getting a fix out.

    Loging in via GitHub may not work at this time.

  • Investigating
    Investigating

    We are currently investigating this incident.

    Loging in via GitHub may not work at this time.

All regions may be experiencing increased deploy times
  • Resolved
    Resolved

    We have resolved the incident and all deployments are going out on time.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

    New Trial and Hobby user deployments have been re-enabled.

  • Update
    Update

    We are continuing to work on a fix for this incident.

    We have paused deployments for customers on Trial and Hobby. We have a lot of new customers joining us and to protect the experience for Pro, we are pausing signups until we provision more resources.

  • Update
    Update
    We are continuing to work on a fix for this incident.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating

    We are currently investigating this incident.

We are seeing some deploys failing to go through in US-West Oregon
  • Resolved
    Resolved

    This specific incident for the US-West region has been resolved.

  • Update
    Update
    We are continuing to work on a fix for this incident.
  • Identified
    Identified

    We have identified the cause and we are working on a resolution.

  • Investigating
    Investigating

    We are currently investigating this incident.

    The US-West metal region is recommended for stateless workloads that do not communicate with stateful workloads.

A single host in US West has restarted
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating
    We are currently investigating this incident.
A single Google Cloud host in US West was rebooted
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating
    We are currently investigating this incident.

Feb 2025 to Apr 2025

Next