--- title: "New Edge Proxy, Static IPs, New Railway Merch Shop" date: 2024-05-17 number: 0186 url: https://railway.com/changelog/2024-05-17-new-edge-proxy-beta --- # New Edge Proxy, Static IPs, New Railway Merch Shop At Railway we’re working at [the intersection of distributed systems engineering and interface design](https://railway.app/careers). That’s what we’re all about — bringing you a new and better way to build software through great engineering and design. In this week’s changelog, we’re going to be talking all about a pair of infrastructure-side improvements that we’re really excited about. We’ve got an all-new edge proxy in beta, we’ve got static IPs in alpha, and (on a completely different note) we’ve also revamped our merch shop! There’s a lot to get into so get comfortable — we’ll wait a sec for you to refill your cup. . .. … .. . Ready? Ready. Off we go! ## Introducing the New Edge Proxy (Beta) [Video: Try out the new edge proxy by selecting the toggle in the service settings] Let’s talk about Railway’s edge or network proxies. These are the proxies that route all external traffic to your application’s server. Before we get into the big news (v3 of our Edge Proxy is now available in beta), let’s cover a little bit of history. In [March of last year](https://railway.app/changelog/2023-03-03-template-marketplace#network-proxy-revamp), we announced that we were transitioning our edge proxy from [Traefik](https://github.com/traefik/traefik) to [Envoy](https://github.com/envoyproxy/envoy). This was Edge Proxy v2 and the benefit at the time was enormous. Since Envoy provided us with real-time configuration mechanisms, it allowed us to change where requests should go seamlessly whenever you made a deploy. Importantly, this allowed us to lower the time-to-live for user app traffic down from 10 seconds to near-instant. But over the past year, as our deployed application base has been growing massively, this mechanism slowly began to creak and cause deployment times to take upwards of 45 seconds for traffic cutover in some cases. That’s unacceptable but there’s a reason for it. Envoy prioritizes some things more than others ... fast update times for example is not as much of a priority for a company like Lyft (creators of Envoy) but is a huge priority for our multi-tenant environment where we have large configs for hundreds of thousands of internet properties. Because of Envoy’s threading model, rolling out diffs to every proxy requires creating a lot copies of the state to avoid having locks … and this all started to come at the cost of update time. So although Envoy worked great at first with the scale we had at the time, we’ve outgrown it massively since then. Hence we set out late last year to start building an entirely new service discovery protocol that would provide instant deploys regardless of how many services we’re handling traffic for. This is how we arrived at the the new Edge Proxy we’re releasing today in Beta. It’s an entirely home-rolled piece of custom software and we’re really excited what it unlocks for you and your users. Let’s talk about what it unlocks for you today if you choose to try out the new 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 now let’s talk about what else the new proxy will soon unlock: - We’ll be able to further improve service start time - We’ll be able to provide automatic port detection - We’ll be able to support [multiple ports per service](https://help.railway.app/feedback/expose-multiple-ports-9c904897) - 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 As mentioned, the new Edge Proxy is in Beta, but we’d love you to try it now. If you’d like to get started upgrading to the new proxy, you’ll need to first visit your service settings page and activate the `Enable new proxy` toggle under `Edge Proxy` in the Networking section. Toggling the new proxy can take up to 1 minute for the change to take effect (due to DNS). You can confirm you're using the new proxy when you see `server: railway-edge` header in your responses. Later on we’ll be rolling out the new proxy *with zero service disruption *and we’ll have a full plan and timeline in place to keep you informed on that progress. No action will be required on your end at any point. We’ve written in more detail about the new Edge Proxy in a [Help Station post](https://help.railway.app/feedback/introducing-railway-s-new-edge-proxy-e6c7d6cf). Please head over there to read more and to [drop us any comments](https://help.railway.app/feedback/introducing-railway-s-new-edge-proxy-e6c7d6cf) as you get started. Onward! ## Introducing Static IPs (Alpha) [Video: You can now assign a static IP to a service through the service settings panel (Pro users only)] By default, Railway egress IPs are dynamic since our orchestrator may schedule workloads on different machines depending on availability when a service is redeployed. This is a problem for users who need a pre-defined set of IP addresses for their services — think something like [MongoDB Atlas](https://www.mongodb.com/products/platform/atlas-database) as an example, which requires customers to add IPs to an allowlist before connecting. Today we’re introducing an alpha version of Static IPs. We’re excited about this release because Static IPs have been [on the roadmap](https://help.railway.app/feedback/static-dedicated-i-ps-de0b680b) for a long time and because this will unblock a large number of users from allowlisting their IPs. Before we show you how to enable Static IPs, a couple things to note: - Static IPs are only available in the `us-west1` region - Static IPs are only available to Pro plan and above users To get started, you’ll simply need to activate the `Enable Static IPs` toggle in the new `Static Outbound IPs` section of your service settings. If you have comments please drop us a line in a [Help Station](https://help.railway.app/) post. We hope you like it. ## New Railway Merch Shop [Image: Get yourself some new Railway swag today!] We’ve updated the [Railway Merch Shop](https://shop.railway.app/)! Thanks to our friend [Taylor](https://x.com/Tealor_Lee) we’ve added a number of all-new Railway-branded items to the shop — we’re talking bags, socks, magnets, you name it. (*Fleece sweatpants, anyone?*) As always, we sell these items at-cost. Check out the [Merch Shop](https://shop.railway.app/) and have a look around. See ya next week! 👋 ## Fixes and Improvements - We upgraded [Nixpacks to v1.23.0](https://github.com/railwayapp/nixpacks/releases/tag/v1.23.0) with support for the latest [Bun and Node.js](https://github.com/railwayapp/nixpacks/pull/1106) runtimes - We upgraded the dashboard to load incremental project data so it appears much faster