Railway - Notice history

All systems operational

Dashboard (railway.com) - Operational

99.95% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 99.86%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025
99.98% uptime

DNS - Operational

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

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Traffic - Operational

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

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Central Station (station.railway.com) - Operational

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

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Railway Storage Buckets - Operational

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

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Notice history

View current status

Apr 2025

Elevated latency US East edge proxies
Resolved1 hour 15 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    We are seeing full recovery, and we are continuing to monitor.

  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.
Dashboard is experiencing degraded performance. You may notice occassional latency spikes or 503s
Resolved3 hours 32 minutes
  • Resolved
    UTC
    Resolved

    This incident has been resolved. A full incident report is available at https://blog.railway.com/p/incident-report-april-30-2025.

  • Update
    UTC
    Update

    We have implemented a fix and are monitoring the results.

  • Monitoring
    UTC
    Monitoring

    We have implemented a fix and are monitoring the results.

  • Identified
    UTC
    Identified

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

  • Investigating
    UTC
    Investigating

    The dashboard is experiencing degraded performance. You may notice occasional latency spikes or 503s.

  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    We have implemented a fix and are monitoring the results.

  • Update
    UTC
    Update

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

  • Update
    UTC
    Update

    The Dashboard is currently inaccessible. We are continuing to work on a fix for the issue.

  • Update
    UTC
    Update

    We are continuing to work on a fix for the issue.

  • Update
    UTC
    Update

    We are continuing to work on a fix for the issue.

  • Update
    UTC
    Update

    We are continuing to work on a fix for the issue.

  • Update
    UTC
    Update
    Dashboard may be inaccessible for some users
  • Identified
    UTC
    Identified

    We have identified the issue and are working on a fix

  • Investigating
    UTC
    Investigating
    Dashboard is experiencing degraded performance. You may notice occassional latency spikes or 503s
US-East delayed placements
Resolved3 hours 49 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    We have fixed a bug preventing new deployments from landing on the newly provisioned hosts.

  • Investigating
    UTC
    Investigating

    We are continuing to investigate a subset of deploys that are delayed in the creating container step.

  • Monitoring
    UTC
    Monitoring

    We have finished adding capacity and are monitoring the process of deployments that were stuck in the queue.

  • Identified
    UTC
    Identified

    We are scaling up capacity in US-East

A single host on Railway GCP US-West has rebooted
ResolvedDegraded performance33 minutes
  • Resolved
    UTC
    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
    UTC
    Monitoring

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

  • Identified
    UTC
    Identified

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

  • Investigating
    UTC
    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
ResolvedDegraded performance19 minutes
  • Resolved
    UTC
    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
    UTC
    Identified

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

  • Investigating
    UTC
    Investigating

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

Mar 2025

Some TCP proxy endpoints may be experiencing connectivity issues
ResolvedPartial outage25 minutes
  • Resolved
    UTC
    Resolved

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

  • Identified
    UTC
    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
    UTC
    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.
ResolvedDegraded performance27 minutes
  • Resolved
    UTC
    Resolved
    Login via Magic emails are being delivered timely
  • Investigating
    UTC
    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
ResolvedDegraded performance11 minutes
  • Resolved
    UTC
    Resolved
    Failover completed
  • Investigating
    UTC
    Investigating
    A singular google cloud host is failing over
A single host in US West was rebooted due to a kernel failure
Resolved34 minutes
  • Resolved
    UTC
    Resolved
    All workloads have now recovered
  • Monitoring
    UTC
    Monitoring
    We are monitoring as workloads come back online
  • Investigating
    UTC
    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
ResolvedPartial outage4 hours 7 minutes
  • Resolved
    UTC
    Resolved
    We've deployed a permanent fix and consider the issue resolved.
  • Monitoring
    UTC
    Monitoring
    We have rolled out a temporary fix and are working on a permanent one.
  • Update
    UTC
    Update
    We continue to investigate the incident. It occurs on a very small % of builds and retries resolve
  • Investigating
    UTC
    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
Resolved30 minutes
  • Resolved
    UTC
    Resolved

    GitHub Single Sign-On is working as intended again.

  • Monitoring
    UTC
    Monitoring

    We have merged a fix and are monitoring the result.

  • Identified
    UTC
    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
    UTC
    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
Resolved4 hours 53 minutes
  • Resolved
    UTC
    Resolved

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

  • Monitoring
    UTC
    Monitoring

    We implemented a fix and are currently monitoring the result.

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

  • Update
    UTC
    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
    UTC
    Update
    We are continuing to work on a fix for this incident.
  • Identified
    UTC
    Identified
    We are continuing to work on a fix for this incident.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating

    We are currently investigating this incident.

We are seeing some deploys failing to go through in US-West Oregon
Resolved3 hours 20 minutes
  • Resolved
    UTC
    Resolved

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

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

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

  • Investigating
    UTC
    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
Resolved45 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.
A single Google Cloud host in US West was rebooted
Resolved39 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.

Previous

Feb 2025 to Apr 2025

Next