Railway Outage History
Railway degraded · 1 active incident View live status →Pingoru has recorded 314 incidents for Railway: 145 in the last 12 months and 32 in the last 90 days.
Incidents, newest first
Major September 13, 2025 A single host in US West has failed 5m US West (California, USA) (Deployments (US West))
Started Sep 13, 2025, 11:00 AM UTC· resolved Sep 13, 2025, 11:06 AM UTC
- investigating Sep 13, 2025, 11:00 AM UTC
The host has been rebooted
- resolved Sep 13, 2025, 11:06 AM UTC
This incident has been resolved.
Minor August 24, 2025 New deploys in US East and EU West are delayed and may take longer to progress 49m US East (Virginia, USA) (Deployments (US East)), EU West (Amsterdam, Netherlands) (Deployments (EU West))
Started Aug 24, 2025, 02:32 PM UTC· resolved Aug 24, 2025, 03:21 PM UTC
- investigating Aug 24, 2025, 02:32 PM UTC
We are currently investigating this incident.
- identified Aug 24, 2025, 02:58 PM UTC
We identified the cause
- monitoring Aug 24, 2025, 02:59 PM UTC
The issue has been resolved and we are monitoring
- resolved Aug 24, 2025, 03:21 PM UTC
This incident has been resolved.
Major August 20, 2025 Deploys May Be Slow To Initialize in US-East 42m US East (Virginia, USA) (Deployments (US East))
Started Aug 20, 2025, 03:01 PM UTC· resolved Aug 20, 2025, 03:44 PM UTC
- identified Aug 20, 2025, 03:01 PM UTC
We have received multiple reports that deployments are taking longer to schedule to a host in US-East. We're provisioning additional capacity.
- monitoring Aug 20, 2025, 03:28 PM UTC
We implemented a fix and are currently monitoring the result.
- resolved Aug 20, 2025, 03:44 PM UTC
This incident has been resolved.
Major August 11, 2025 A single host in US East has failed 24m US East (Virginia, USA) (Deployments (US East))
Started Aug 11, 2025, 03:22 PM UTC· resolved Aug 11, 2025, 03:46 PM UTC
- investigating Aug 11, 2025, 03:22 PM UTC
A single host in US East has been rebooted
- identified Aug 11, 2025, 03:33 PM UTC
Host is back online and we are continuing to ensure all applications are resumed.
- resolved Aug 11, 2025, 03:46 PM UTC
This incident has been resolved.
Major August 5, 2025 GitHub is currently experiencing an outage 17m External & Third-Party Integrations (GitHub — Auto-Deploys)
Started Aug 05, 2025, 04:03 PM UTC· resolved Aug 05, 2025, 04:21 PM UTC
- monitoring Aug 05, 2025, 04:03 PM UTC
Builds and deployments on Railway may be delayed as a result of an incident on GitHub's API () impacting Railway's integration with GitHub.
- resolved Aug 05, 2025, 04:21 PM UTC
This incident has been resolved.
Minor July 29, 2025 Canvas might be taking longer than normal to load. We are rolling out a fix 9h 18m Railway (Dashboard — railway.com)
Started Jul 29, 2025, 10:50 AM UTC· resolved Jul 29, 2025, 08:09 PM UTC
- investigating Jul 29, 2025, 10:50 AM UTC
Canvas might be taking longer than normal to load. We are rolling out a fix
- identified Jul 29, 2025, 11:49 AM UTC
We are continuing to work on a fix
- identified Jul 29, 2025, 02:06 PM UTC
We are rolling out a fix to improve canvas loading speed
- monitoring Jul 29, 2025, 07:22 PM UTC
The canvas is loading normally. We are monitoring the fix
- resolved Jul 29, 2025, 08:09 PM UTC
the canvas is back to normal
Minor July 28, 2025 Canvas may be delayed to show up and function. We are investigating 5h 16m Railway (Dashboard — railway.com)
Started Jul 28, 2025, 04:20 PM UTC· resolved Jul 28, 2025, 09:37 PM UTC
- investigating Jul 28, 2025, 04:20 PM UTC
Canvas may be delayed to show up and function. We are investigating
- investigating Jul 28, 2025, 05:08 PM UTC
We are still investigating. Builds and deploys are working normally, only the visual canvas in the dashboard is slow to load.
- monitoring Jul 28, 2025, 07:00 PM UTC
The canvas is back to normal. We are monitoring the rollout
- identified Jul 28, 2025, 07:24 PM UTC
We are noticing some issues with the stability of the canvas. We are continuing with the fix
- monitoring Jul 28, 2025, 09:20 PM UTC
We are seeing recovery as we continue to monitor the system.
- resolved Jul 28, 2025, 09:37 PM UTC
The incident has been resolved and we are seeing performance back to normal levels.
Major July 15, 2025 Elevated deployment latency 1h 29m US East (Virginia, USA) (Deployments (US East)), US West (California, USA) (Deployments (US West)), EU West (Amsterdam, Netherlands) (Deployments (EU West)), Southeast Asia (Singapore) (Deployments (Southeast Asia))
Started Jul 15, 2025, 04:26 PM UTC· resolved Jul 15, 2025, 05:55 PM UTC
- investigating Jul 15, 2025, 04:26 PM UTC
We are investigating a number of deploys that are stuck initializing. Non-Pro deployments have been temporarily paused.
- investigating Jul 15, 2025, 05:00 PM UTC
We continue to investigate the issue and have halted some active background operations to relieve the deployment delays
- identified Jul 15, 2025, 05:15 PM UTC
Deployments are now processing as we're reducing the queue backpressure. We have halted some background operations to relieve deployment delays.
- monitoring Jul 15, 2025, 05:42 PM UTC
Queue backpresssure has significantly reduced, we have re-enabled non-pro deployments and are monitoring
- resolved Jul 15, 2025, 05:55 PM UTC
Our deployment pipeline throughput was impacted by a resource constraint on the database backing our Temporal cluster. We have increased cluster resources and upgraded the database; we have seen deployment throughput restored.
Minor July 13, 2025 A single host in EU West is failing over 40m EU West (Amsterdam, Netherlands) (Deployments (EU West))
Started Jul 13, 2025, 03:49 PM UTC· resolved Jul 13, 2025, 04:30 PM UTC
- investigating Jul 13, 2025, 03:49 PM UTC
We are currently investigating this incident. Workloads located on that host may be unavailable during that time.
- monitoring Jul 13, 2025, 04:04 PM UTC
We implemented a fix and are currently monitoring the result.
- resolved Jul 13, 2025, 04:30 PM UTC
This incident has been resolved. All workloads have been successfully restored.
Minor June 26, 2025 Degraded read/write performance on Railway Volumes 46m US West (California, USA) (Deployments (US West))
Started Jun 26, 2025, 02:59 PM UTC· resolved Jun 26, 2025, 03:45 PM UTC
- investigating Jun 26, 2025, 02:59 PM UTC
We are currently investigating this incident.
- investigating Jun 26, 2025, 03:00 PM UTC
Users may experience higher read/write latency on Railway Volumes. We are investigating this incident.
- monitoring Jun 26, 2025, 03:06 PM UTC
We're seeing recovery across the fleet. We are continuing to monitor this incident.
- resolved Jun 26, 2025, 03:11 PM UTC
This incident has been resolved.
- monitoring Jun 26, 2025, 03:12 PM UTC
We are continuing to monitor, but have seen recovery.
- resolved Jun 26, 2025, 03:45 PM UTC
This incident has been resolved.
Critical June 17, 2025 GitHub Access is Down 37m External & Third-Party Integrations (GitHub — Auto-Deploys)
Started Jun 17, 2025, 07:46 PM UTC· resolved Jun 17, 2025, 08:24 PM UTC
- identified Jun 17, 2025, 07:46 PM UTC
We have found that GitHub access is down. Deployments with GH as a source will not deploy. We are continuing to work on a fix for this incident.
- resolved Jun 17, 2025, 08:24 PM UTC
This incident has been resolved.
Minor June 12, 2025 Degraded performance on Central Station 59m Railway (Support & Community — station.railway.com)
Started Jun 12, 2025, 08:19 AM UTC· resolved Jun 12, 2025, 09:19 AM UTC
- investigating Jun 12, 2025, 08:19 AM UTC
Users may experience issues creating tickets. Please email us at [[email protected]](mailto:[email protected]) as an alternative.
- identified Jun 12, 2025, 08:39 AM UTC
We have identified the issue as cross regional latency due to an errant deploy. We are working on a fix.
- monitoring Jun 12, 2025, 09:11 AM UTC
We implemented a fix and are currently monitoring the result.
- resolved Jun 12, 2025, 09:19 AM UTC
This incident has been resolved.
Minor June 10, 2025 GitHub OAuth 18m Authentication (Login — GitHub)
Started Jun 10, 2025, 05:30 PM UTC· resolved Jun 10, 2025, 05:48 PM UTC
- investigating Jun 10, 2025, 05:30 PM UTC
We are currently investigating this incident. New logins may fail for a subset of users.
- resolved Jun 10, 2025, 05:48 PM UTC
We have added concurrency to our Github authentication. The incident is now resolved. If your Github login failed, please retry.
Minor June 6, 2025 Some users are failing to login. We're looking into it 5h 49m Railway (Dashboard — railway.com)
Started Jun 06, 2025, 04:08 PM UTC· resolved Jun 06, 2025, 09:58 PM UTC
- investigating Jun 06, 2025, 04:08 PM UTC
Some users are failing to login. We're looking into it
- identified Jun 06, 2025, 05:26 PM UTC
GitHub is rate limiting some secondary sign ins. We're rolling out mitigation strategies and escalating upstream
- monitoring Jun 06, 2025, 05:49 PM UTC
Logins should be recovered. We are monitoring.
- resolved Jun 06, 2025, 05:58 PM UTC
Looking good after monitoring. Resolved
- identified Jun 06, 2025, 06:41 PM UTC
It appears GitHub has rate limited initial logins again. We have re-escalated.
- identified Jun 06, 2025, 08:00 PM UTC
We are still working on this issue.
- monitoring Jun 06, 2025, 08:16 PM UTC
Logins should be recovered. We are monitoring.
- resolved Jun 06, 2025, 08:57 PM UTC
We've resolved the issue and put mitigation in place. We will issue a post mortem today.
- investigating Jun 06, 2025, 09:58 PM UTC
Incident Report:
Minor June 5, 2025 404 flashing observed for some users. We're rolling out a fix 9m Railway (Dashboard — railway.com)
Started Jun 05, 2025, 01:08 AM UTC· resolved Jun 05, 2025, 01:17 AM UTC
- investigating Jun 05, 2025, 01:08 AM UTC
404 flashing observed for some users. We're rolling out a fix
- monitoring Jun 05, 2025, 01:12 AM UTC
Fix rolled out. Issue should be resolved. Monitoring
- resolved Jun 05, 2025, 01:17 AM UTC
Resolved
Minor May 6, 2025 Small % of Project 404's 5m Railway (Dashboard — railway.com)
Started May 06, 2025, 07:35 PM UTC· resolved May 06, 2025, 07:40 PM UTC
- identified May 06, 2025, 07:35 PM UTC
We rolled out a change where we dropped a column unsafely. While the new deploy was rolling out (\~5 minutes), old deploys, the ORM we used automatically queried the old field. As a result, some small % of users who hard refreshed (and had to load project state) may have seen a 404 briefly. We're rolling out a lint rule to catch this in the future. Apologies
- resolved May 06, 2025, 07:40 PM UTC
This incident has been resolved.
Minor May 4, 2025 Single host on Railway Metal (us-west2) is offline 42m US West (California, USA) (Deployments (US West)), Southeast Asia (Singapore) (Deployments (Southeast Asia))
Started May 04, 2025, 09:33 PM UTC· resolved May 04, 2025, 10:15 PM UTC
- investigating May 04, 2025, 09:33 PM UTC
We are currently investigating this incident. A small subset of impacted users on us-west2 region may notice their deployments are unresponsive during this period. You can re-deploy your service to mitigate this.
- identified May 04, 2025, 09:53 PM UTC
We have identified an issue with the offline host, and confirmed that full recovery is in progress.
- monitoring May 04, 2025, 10:01 PM UTC
All deployments on the offline host have successfully recovered.
- resolved May 04, 2025, 10:15 PM UTC
This incident has been resolved.
Minor May 2, 2025 Dashboard timeouts 2m Railway (Dashboard — railway.com)
Started May 02, 2025, 06:23 PM UTC· resolved May 02, 2025, 06:25 PM UTC
- identified May 02, 2025, 06:23 PM UTC
A small subset of users may have noticed a dashboard timeout for up to 2 minutes.
- resolved May 02, 2025, 06:25 PM UTC
This incident has been resolved.
Minor May 2, 2025 Dashboard Timeouts 1m Railway (Dashboard — railway.com)
Started May 02, 2025, 02:26 AM UTC· resolved May 02, 2025, 02:28 AM UTC
- identified May 02, 2025, 02:26 AM UTC
Some users may notice dashboard timeouts. We are rolling out a fix for this
- monitoring May 02, 2025, 02:26 AM UTC
We implemented a fix and are currently monitoring the result.
- resolved May 02, 2025, 02:28 AM UTC
This incident has been resolved.
Minor April 30, 2025 Dashboard is experiencing degraded performance. You may notice occassional latency spikes or 503s 3h 32m Railway (Dashboard — railway.com)
Started Apr 30, 2025, 08:07 PM UTC· resolved Apr 30, 2025, 11:40 PM UTC
- investigating Apr 30, 2025, 08:07 PM UTC
Dashboard is experiencing degraded performance. You may notice occassional latency spikes or 503s
- identified Apr 30, 2025, 08:36 PM UTC
We have identified the issue and are working on a fix
- identified Apr 30, 2025, 08:58 PM UTC
Dashboard may be inaccessible for some users
- identified Apr 30, 2025, 09:20 PM UTC
We are continuing to work on a fix for the issue.
- identified Apr 30, 2025, 09:33 PM UTC
We are continuing to work on a fix for the issue.
- identified Apr 30, 2025, 09:46 PM UTC
We are continuing to work on a fix for the issue.
- identified Apr 30, 2025, 09:48 PM UTC
The Dashboard is currently inaccessible. We are continuing to work on a fix for the issue.
- identified Apr 30, 2025, 10:02 PM UTC
We are continuing to work on a fix for this Issue.
- monitoring Apr 30, 2025, 10:11 PM UTC
We have implemented a fix and are monitoring the results.
- resolved Apr 30, 2025, 10:20 PM UTC
This incident has been resolved.
- investigating Apr 30, 2025, 10:24 PM UTC
The dashboard is experiencing degraded performance. You may notice occasional latency spikes or 503s.
- identified Apr 30, 2025, 10:49 PM UTC
We are continuing to work on a fix for this Issue.
- monitoring Apr 30, 2025, 10:57 PM UTC
We have implemented a fix and are monitoring the results.
- monitoring Apr 30, 2025, 11:23 PM UTC
We have implemented a fix and are monitoring the results.
- resolved Apr 30, 2025, 11:40 PM UTC
This incident has been resolved. A full incident report is available at .
Minor April 18, 2025 Elevated error rates for deployments with volumes on Southeast Asia (Singapore) Metal region 2h 16m Southeast Asia (Singapore) (Deployments (Southeast Asia))
Started Apr 18, 2025, 11:42 AM UTC· resolved Apr 18, 2025, 01:58 PM UTC
- investigating Apr 18, 2025, 11:42 AM UTC
We are currently investigating elevated error rates of deployments in Southeast Asia (Singapore) Metal. A small subset of services with volumes may be failing to deploy with the error message "Container failed to start"
- identified Apr 18, 2025, 12:01 PM UTC
We have identified a single degraded host on Southeast Asia (Singapore) Metal. We are currently restoring active deployments without a volume on the host to a different host. Workloads with a volume located on the host may be unavailable during this period. Impacted users will see a deployment initiated by Railway as part of this restoration process.
- monitoring Apr 18, 2025, 01:17 PM UTC
All workloads with a volume on the impacted host is back online. All other workloads have been successfully moved to a different host. We are actively monitoring the recovery. If your deployment failed due to “Container failed to start" error, please attempt a re-deploy.
- resolved Apr 18, 2025, 01:58 PM UTC
This incident has been resolved.
Minor April 12, 2025 application logs may not be loading 1h 6m Observability (Logs)
Started Apr 12, 2025, 03:26 PM UTC· resolved Apr 12, 2025, 04:33 PM UTC
- investigating Apr 12, 2025, 03:26 PM UTC
application logs may not be loading
- investigating Apr 12, 2025, 03:54 PM UTC
We are continuing to investigate issues with viewing application logs.
- monitoring Apr 12, 2025, 04:15 PM UTC
We implemented a fix and are currently monitoring the result.
- resolved Apr 12, 2025, 04:33 PM UTC
application logs are loading as expected.
Minor April 10, 2025 Single host on Railway Metal is offline 2h 16m US West (California, USA) (Deployments (US West))
Started Apr 10, 2025, 05:01 PM UTC· resolved Apr 10, 2025, 07:18 PM UTC
- investigating Apr 10, 2025, 05:01 PM UTC
A single host in us-west2 region on Railway Metal is currently offline. Deployments on the host may be unresponsive at this time. If you are experiencing a deploy that is unresponsive, please re-deploy your last active deployment.
- identified Apr 10, 2025, 05:10 PM UTC
We are failing over deploys on the host to a different host. Impacted users may see their services re-deployed by Railway.
- monitoring Apr 10, 2025, 07:03 PM UTC
``` All impacted workloads have been successfully moved to a different host. ```
- resolved Apr 10, 2025, 07:18 PM UTC
This incident has been resolved. All impacted workloads are successfully restored, and the faulty host has been removed from our fleet.
Minor April 6, 2025 Logs appear to be slower to load and in rare occasions time out. We’re looking into this 52m Observability (Logs)
Started Apr 06, 2025, 02:41 AM UTC· resolved Apr 06, 2025, 03:34 AM UTC
- investigating Apr 06, 2025, 02:41 AM UTC
Logs appear to be slower to load and in rare occasions time out. We’re looking into this
- monitoring Apr 06, 2025, 03:32 AM UTC
We've rolled out a fix and latency should be recovered. Will monitor and then close out
- resolved Apr 06, 2025, 03:34 AM UTC
Recovered
Minor March 27, 2025 Potential upstream issue causing delayed login via Magic emails. Login via GitHub may be used as a workaround. 27m Railway (Dashboard — railway.com)
Started Mar 27, 2025, 06:54 PM UTC· resolved Mar 27, 2025, 07:21 PM UTC
- investigating Mar 27, 2025, 06:54 PM UTC
Potential upstream issue causing delayed login via Magic emails. Login via GitHub may be used as a workaround.
- resolved Mar 27, 2025, 07:21 PM UTC
Login via Magic emails are being delivered timely