Railway - Notice history

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.

We have implemented a mitigation and are monitoring.

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.

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.

application logs are loading as expected.

We are continuing to investigate issues with viewing application logs.

This incident has been resolved. All impacted workloads are successfully restored, and the faulty host has been removed from our fleet.

All impacted workloads have been successfully moved to a different host.

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

This incident has been resolved. We successfully mitigated a DDoS attack between 21:02 UTC ~ 21:09 UTC, largely impacting US East. A small subset of users connecting to Railway-hosted workloads from Europe or US East may have experienced dropped requests or increased latency during this period.

The DDoS attack has been mitigated. We are seeing full recovery across Europe West & US East, and are continuing to monitor the situation.

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

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.

GitHub Single Sign-On is working as intended again.

We have merged a fix and are monitoring the result.

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

Loging in via GitHub may not work at this time.

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

We implemented a fix and are currently monitoring the result.

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

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.

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

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