Railway - Notice history

All systems operational

Dashboard (railway.com) - Operational

100% - uptime
Dec 2025 · 99.98%Jan 2026 · 100.0%Feb · 100.0%

Previous page

Next page

Dec 2025
Jan 2026
Feb 2026
100% - uptime

DNS - Operational

100% - uptime
Dec 2025 · 99.86%Jan 2026 · 100.0%Feb · 100.0%

Previous page

Next page

Dec 2025
Jan 2026
Feb 2026

Traffic - Operational

100% - uptime
Dec 2025 · 99.86%Jan 2026 · 100.0%Feb · 99.78%

Previous page

Next page

Dec 2025
Jan 2026
Feb 2026

Central Station (station.railway.com) - Operational

100% - uptime
Dec 2025 · 100.0%Jan 2026 · 100.0%Feb · 100.0%

Previous page

Next page

Dec 2025
Jan 2026
Feb 2026

Railway Storage Buckets - Operational

100% - uptime
Dec 2025 · 100.0%Jan 2026 · 100.0%Feb · 100.0%

Previous page

Next page

Dec 2025
Jan 2026
Feb 2026

Notice history

Feb 2026

We're investigating degraded performance on internal networking
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.
We're investigating issues impacting deployments
  • Postmortem
    Postmortem

    A postmortem of this incident has been published at https://blog.railway.com/p/incident-report-february-11-2026.

  • Resolved
    Resolved

    Automated recovery for all impacted deployments have been completed. This incident has been resolved. A postmortem of this incident will be published shortly.

  • Update
    Update

    We have started automated recovery for all impacted deployments.

  • Monitoring
    Monitoring

    A fix has been rolled out successfully and we are seeing partial recovery on impacted deployments. Automated recovery of all impacted deployments will begin shortly. We have confirmed that this incident impacts <3% of running deployments on Railway. If you are experiencing issues with your deployment, please attempt a re-deploy.

  • Identified
    Identified

    We have identified the incident. A fix is currently being rolled out.

  • Investigating
    Investigating
    We are currently investigating this incident.
GitHub is experiencing degraded performance issues
GitHub is experiencing degraded performance issues
Deploys may fail to go through
  • Resolved
    Resolved

    Our fix is live and customers report deploys working again!

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

    We're investigating this incident

Jan 2026

We're investigating reports of builds failing to complete. We'll provide updates as we learn more.
  • Resolved
    Resolved
    Builds are now running nominally, long running builds may need to be re-tried for them to go through.
  • Monitoring
    Monitoring
    We have updated the upstream provider URIs for images. Customers report recovery for new builds.
  • Investigating
    Investigating
    We're investigating reports of builds failing to complete. We'll provide updates as we learn more.
Storage Buckets Unavailable
  • Resolved
    Resolved

    This incident has been resolved. The issue affecting Railway Storage Buckets has been resolved. Bucket access and operations are functioning normally. Root cause was a DNS resolution issue that has been corrected upstream from Tigris. We apologize for the disruption. If you continue to experience issues, please contact support at https://station.railway.com.

  • Identified
    Identified

    We are aware of an issue affecting Railway Storage Buckets. Users may be unable to access bucket contents or perform read/write operations. Our team is actively investigating a suspected DNS resolution issue and will provide updates as we learn more.

NPM is having degraded performance Installing and Viewing Packages
GitHub operations are being rate-limited. Users may be unable to log-in or add GitHub repos. We are working on resolution for this issue.
  • Resolved
    Resolved
    Our monitors have shown that we have good effect on our changes, although we have improvement, we are still monitoring the impact for all customers.
  • Monitoring
    Monitoring
    We have observed no further GitHub rate limiting in the last 60 minutes and we are reanbling GitHub authentication.
  • Update
    Update
    We have rolled out additional fixes to improve GitHub callpath resiliency. We are monitoring their effectiveness and will issue an update once we finish monitoring.
  • Identified
    Identified
    We have disabled GitHub log in to reduce rate-limit pressure on the system.
  • Investigating
    Investigating
    GitHub operations are being rate-limited. Users may be unable to log-in or add GitHub repos. We are working on resolution for this issue.
Some workloads may have delayed or no logs. We are investigating the cause.
  • Resolved
    Resolved
    Logs are working nominally.
  • Investigating
    Investigating
    Some workloads may have delayed or no logs. We are investigating the cause.

Dec 2025

Canvas updates are slow
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    Identified

    We’ve identified a potential root cause and are currently evaluating a fix.

  • Investigating
    Investigating

    The Canvas is currently experiencing degraded performance. Updates to projects may take longer than usual to persist, which can result in increased loading times.

Failing builds for mise installs
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    Identified

    We have identified an issue with mise package installs affecting a portion of builds. We are actively working on a fix

We are investigating issues with elevated network latency and slow deploys
  • Postmortem
    Postmortem

    A post-mortem of this incident has been published at https://blog.railway.com/p/incident-report-december-16-2025.

  • Resolved
    Resolved
    This incident has been resolved.
  • Update
    Update

    We have seen widespread recovery and are continuing to monitor this incident.

  • Update
    Update

    We are still monitoring this incident.

  • Update
    Update

    We are seeing further degradation, particularly in EU regions. We are continuing to work on a permanent fix.

  • Update
    Update

    We have seen recovery in all regions. We are continuing to monitor this incident.

  • Monitoring
    Monitoring

    We are rolling out a fix and are seeing recovery in all regions. Deploys have been re-enabled

  • Identified
    Identified

    We continue to see degradation across all regions, and are working on a fix. We have paused new deploys as we investigate.

  • Investigating
    Investigating
    We are currently investigating this incident.
A single host has rebooted
  • Resolved
    Resolved

    At 03:19 UTC on December 12th a host rebooted in our GCP environment. Very few customer workloads were impacted. We implemented a fix and are currently monitoring the result. The host rebooted and came back up successfully.

[Retroactive] DNS Requests are slow
  • Update
    Update
    This incident has been resolved.
  • Resolved
    Resolved

    (This is a retroactive incident) On December 11th at 9:34pm UTC to Approx. 10:56pm we observed increased latency in DNS requests on our private networks. This was caused by upgrades to our backend infrastructure which moved traffic around on our network in a manner that caused increased latency for DNS requests. Once the upgrades were complete, DNS requests returned to normal.

Dec 2025 to Feb 2026

Next