We’re in the midst of a sprint to improve platform usability and reliability and we need your help.

 about any nits, papercuts, issues, or footguns with the platform. 

We’re going to challenge ourselves to fix every issue on the list — so please don’t be shy. Let us know what issues you’re running into no matter how small. 

We changed the default database connection type to private to prevent unwanted egress charges

Nobody likes surprise egress charges — that includes us. 

We’ve noticed a number of users running up unexpected bills because they were connecting to their Railway database via 

 whenever possible. To underline that recommendation, we made the Private Network connection string the default in the UI. (No egress charges if you’re using the private network.) 

All databases now expose the private URL by default

All databases now expose the public URL separately as 

We’ve also updated the connect modal within the 

Together we can stop unwanted egress charges!

Let us know what you think by dropping a comment in 

 we told you all about the new Edge Proxy that we (then) rolled out in beta.

 we told you that we made the Edge Proxy (then) generally available.

Today, we’re letting you know that we’re going to start force-migrating all service domains, regardless of user plan tier, to the new Edge Proxy. This will happen next week. 

As a reminder, these are the benefits of the new Edge Proxy:

You’ll experience near-instant deploy cutovers instead of waiting for a minute until it’s provisioned as currently happens today

You’ll get new detailed error pages with a traceable Request ID that you can forward to us when debugging an issue

And there are some benefits that this will unlock down the line:

We’ll be able to further improve service start time

We’ll be able to provide automatic port detection

We’ll be able to provide network logs and metrics

We’ll be able to add support for advanced routing rules and load balancing strategies

We’ll be able to improve service quality and DDoS attack mitigation options

Note that your custom domains will continue to use the legacy proxy if you haven’t already opted in … but what are you waiting for? The new Edge Proxy offers faster deploys, better networking troubleshooting with request IDs, and will have much more in the near future. 

At some point next week, we’ll make the existing proxy toggle in the dashboard change only the proxy in use for custom domains.

Later on this quarter, we will follow this same force opt-in migration for custom domains. (This means that our goal will be to deprecate the legacy proxy entirely sometime this quarter.)

If you have further questions or comments about the migration, please drop us a line in the 

As mentioned in the introduction, it’s a big month at Railway as we work to increase platform reliability and user experience. 

We’d love your feedback on what we can make better on the platform. 

 Help Station thread and let us know what we can do to improve your experience on the platform. 

We’ll strive to fix everything on the list. 

We fixed a bug where users were unable to edit service domains if more than one service was present

We fixed an issue where template health stats were not showing up for some templates

We fixed a bug where updating a team template would redirect you to your personal workspace rather than your team workspace

We made it published templates clickable from your account page

https://res.cloudinary.com/railway/image/upload/v1721420274/2024-0719_sfwa5k.png

Database Private Network Defaults, New Edge Proxy Migration, Request for Nits

Changelog #0195