We're sorry for the trouble. There is an ongoing incident, Connectivity issues in US West, affecting deployments and public networking in the US West region. This is the cause of the errors you're seeing. We'd recommend holding off on a region migration right now, as new deployments in US West are also affected by the incident and may stall. You can follow updates on the resolution at that link.

Weigh between how long it'll take you to migrate compared to how willing you are to risk the incident taking a while. I'd say it's worth a shot. One thing to note, migrations of stateful services could get stuck

What would getting stuck cause?

For stateful services, the migration of the data in the volume could get stuck

if you have no stateful services then it's safe to migrate though

Great! Thanks for your help

Where did you see this communication?

3 minutes ago

Happy to help 🙂

I was thinking about migrating too, but I’d probably wait for now. The incident is already recovering and moving stateful services during this could cause another problem.

The incident should be resolved now

i wonder how many folks is going to migrate away from railway after the two most recent incidents?