Railway - Notice history

This incident has been resolved. If you have a build stuck in "Initializing" step, please re-deploy.

We have identified the issue with GCP running out of instance capacity for our configuration. We are currently routing all US East builds to a different region. All builds should return to normal within 30 minutes.

Builds are progressing faster now. We are continuing to monitor.

Builds are progressing faster now. We are continuing to monitor.

We are continuing to monitor, but have seen recovery.

We're seeing recovery across the fleet. We are continuing to monitor this incident.

Users may experience higher read/write latency on Railway Volumes. We are investigating this incident.

All volumes should be seeing recovery back to nominal latency. We are continuing to monitor the fleet latency.

Most volumes have recovered to nominal latency. We are continuing to investigate any remaining ones that have not recovered yet.

Some hosts are showing signs of recovery. We are continuing to investigate.

We have shipped a remedy for network discovery. We have re-enabled deployments. We implemented a fix and are currently monitoring the result.

During a routine update to BGP configuration for Railway's Anycast network 66.33.22.0/23, a small proportion (approximately 8%) of upstream ISPs failed to propagate a routing update - this led to a small amount of traffic to be dropped for a period less than 5 mins.

Once routes propagated, some ISPs were routed in a suboptimal manner leading to elevated latency for some users. We have reverted the routing configuration and are liaising with our vendors to root cause the issue. We will also be creating maintenance windows for future routing config changes and staging their rollout to minimize risk.

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

This incident has been resolved.

We are seeing recovery and continuing to monitor the situation.

Attack targeting EU edge identified. Mitigation efforts underway.