Railway's infrastructure spans multiple regions across the globe. This allows you to deploy your applications closer to your users no matter where they are located. This feature is only available to Pro plan workspaces.
Consider factors like compliance needs and proximity to your users when choosing a region.
Railway has deploy regions in the Americas, Europe, and Asia-Pacific to provide broad coverage around the world.
Within the service settings, you can select one of the following regions:
Additional regions may be added in the future as Railway continues expanding its infrastructure footprint.
By default, Railway deploys to
us-west1 located in Portland, Oregon.
All regions provide the same experience, performance, and reliability you expect from Railway.
The region of a service can be changed at any time, without any changes to your domain, private networking, etc.
There will be no downtime when changing the region of a service, except if it has a volume attached to it (see below).
Volumes follow the region of the service to which they are attached.
If you change the region of a service with an attached volume, the volume will need to be migrated to the new region.
Note that this migration can take a while depending on the size of the volume, and will cause downtime of your service during that time.
The same is true if you attach a detached volume to a service in a different region. It will need to be migrated to the new region, which can take a while and cause downtime.
Edit this file on GitHub