Railway - Notice history

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.

This incident has been resolved. We will be spinning up a secondary BGP Anycast route on metal to provide full dual redundancy, regardless of Google's failures.

Redeploying in any other region will resolve the issue for affected users

Metal interconnect seems to have been taken down by Google Cloud. This incident affects any edge traffic to metal instances in us-east

We have seen a full recovery, all connections are succeeding.

We are seeing connections recover, we are going to be monitoring closely.

We are experiencing elevated error rates and increased latency in our Asia region proxies. Users connecting to Railway-hosted workloads from Asia may experience some difficulties. We are investigating this incident.

All workloads on the host are now back online

We are actively monitoring workloads on this host as they come back online

All applications on the affected host have been restored.

Host is being recovered by the team.

This incident has been resolved. Railway was down for a total of ~10 minutes. We will publish a full retroactive on this incident shortly.

Services should be fully restored and we'll continue to monitor.

Issue has been identified.