Railway Metal Upgrade
Railway is moving to self-hosted regions across the world called Railway Metal. This page provides information about the upgrade process to Railway Metal, what to expect, and how to manage the transition.
What is Railway Metal?
Railway Metal is Railway's next-generation infrastructure built on hardware that we own and operate in datacenters around the world. This move enables better performance, lower costs, and unlocks new features.
For a comprehensive overview of Railway Metal, its benefits, and our roadmap, please visit the Railway Metal documentation.
Automatic Upgrades
As part of our transition to Railway Metal, Railway will automatically migrate eligible services. When this happens:
- You'll see a new deploy initiated by Railway in your service
- A notification banner will appear informing you about the upgrade
- Your service will be redeployed on Railway Metal infrastructure
What to Expect During the Upgrade
When your service is upgraded to Railway Metal:
- Brief Downtime: There may be a short period of downtime as your service is redeployed. To minimize this, ensure you have Health Checks configured.
- Ephemeral Storage Reset: Any ephemeral storage (like
/tmp
directories) will be wiped. Use Volumes for persistent data storage. - Same Behavior: The upgrade behavior is identical to a manual redeploy of your service. Any effects you'd normally expect during a redeploy will apply here as well.
- Region Change: Your service may be moved to a different geographical location within the same region (e.g., from US West Oregon to US West California). This is normal and part of the migration to our own hardware.
Eligibility for Automatic Upgrades
Services will be upgraded based on our published timeline. Currently:
- Services without volumes are eligible for automatic upgrade
- Services with volumes will be eligible starting in March 2025
- Certain features like Static IPs for Pro users aren't yet available on Railway Metal regions
Managing the Upgrade
If You Experience Issues
If you encounter any problems after the upgrade, you can roll back to the previous infrastructure by:
- Clicking the Rollback button in the upgrade notification banner
Manual Rollback
You can also manually roll back by:
- Going to your service's Settings → Deploy → Regions
- Selecting regions without the Metal (New) tag
Opting In Early
If you'd like to upgrade to Railway Metal before your automatic migration:
- Go to your service's Settings → Deploy → Regions
- Select any region with the Metal (New) tag
- Deploy your service to apply the change
Cross-Region Considerations
If you have services that reference each other (particularly services with volumes), be aware that migrating only some services to Railway Metal may introduce latency if they end up in physically distant datacenters.
For example, if your application in US West (California) Railway Metal region communicates with a database in US West (Oregon), you may experience increased latency. In such cases, consider rolling back to the original region until all your services can migrate together.
Getting Help
If you need assistance with your Railway Metal upgrade:
- Submit feedback through our Central Station
- Pro and Enterprise customers can reach out via Slack
- See our FAQ on Railway Metal for answers to common questions
Remember, this is a free upgrade for all users and is designed to provide an improved experience across all aspects of the Railway platform.
Edit this file on GitHub