Skip to content
🌐 Support IPv4 Private Networks
chandrika
EMPLOYEEOP

a year ago

This quarter, we’re working bringing you support for IPv4 in our private networks!

Railway private networks are currently IPv6 only. Your containers get assigned an IPv6 address and there’s no way to talk to your other containers over IPv4.

Lots of applications, services, and frameworks are IPv4-first and sometimes IPv4-only. It can be confusing to run into the networking issues that are caused by private networks being v6 only.

In Progress

0 Threads mention this feature

25 Replies

Status changed to Planned chandrika • over 1 year ago


0xpaperhead

a year ago

I'm curious about the reason behind the decision to only support IPv6. Can you elaborate?


a year ago

At a high level, It was easier to implement because we can encode information into the IPv6 address such as the destination container, source container, and a few other things.

But with that said, we now have IPv4 private networking in beta:

https://railway.com/changelog/2025-09-19-railpack-default#ipv4-private-networks-to-priority-boarding-


Status changed to In Progress brody • about 1 year ago


epether

a year ago

Awesome! This was pushing back our migration from Heroku to Railway as it required us to swap for libraries that support ipv6.

Nice to see IPv4 finally coming, nice work.


velaris

a year ago

Will this be available in legacy IPv4 environments? Currently, I have to create a new project and migrate all the services there, and I have a lot of them. I'd like this feature to be available in legacy projects as well. When will this feature be available in legacy environments?


velaris

Will this be available in legacy IPv4 environments? Currently, I have to create a new project and migrate all the services there, and I have a lot of them. I'd like this feature to be available in legacy projects as well. When will this feature be available in legacy environments?

a year ago

When this feature is GA'd IPv4 will be available in pre-existing environments.


Anonymous

a year ago

Is there an ETA for the GA ?


a year ago

No ETA yet unfortunately.


a year ago

Have just put this feature into GA 🙂

We will be enabling it on all pre-existing environments next week.


0xpaperhead

a year ago

awesome! thank you


team-regulis

a year ago

I can't wait to try this out, what do i need to do to enable in my existing (legacy) production environment so that traffic between my services is private? Please link to docs on how. Thank you!

Also, many announcements refer to "Private Boarding" but for the life of me I can't figure out what Railway is referring to by this term.


a year ago

You mean priority boarding, a train term that in the context of Railway simply means the beta testers program.

https://railway.com/account/feature-flags

As phin mentioned above, the feature is already generally available for new environments, and we will be enabling it on already existing environments in the next week, nothing you need to do on your end, we will update this thread one we have enabled it on all environments.

Additionally, given the wording you used, I need to mention that we already have private networking that has been generally available for well over a year now, but that has been IPv6 only.


team-regulis

a year ago

Thank you, now I see what you mean about Priority Boarding, I didn't know those feature flags existed.

I was aware of the IPV6 option but it is a pain to migrate our services to IPV6... some things didn't seem to work right. So looking forward to IPv4 support (as backwards as that sounds!)


brody

You mean priority boarding, a train term that in the context of Railway simply means the beta testers program. <https://railway.com/account/feature-flags> As phin mentioned above, the feature is already generally available for new environments, and we will be enabling it on already existing environments in the next week, nothing you need to do on your end, we will update this thread one we have enabled it on all environments. Additionally, given the wording you used, I need to mention that we already have private networking that has been generally available for well over a year now, but that has been IPv6 only.

Anonymous

a year ago

Hello 👋 from the next week. Is it enabled in existing environments yet?

Also, is there any change to the DNS in tailscale ? See attached


Hello 👋 from the next week. Is it enabled in existing environments yet? Also, is there any change to the DNS in tailscale ? See attached

a year ago

Not yet, unfortunately, other stuff came up that needed the engineer's attention.

Rest assured, we will update here once it is enabled on existing environments.

And if your Tailscale subnet router works now, then no changes will be needed to your DNS configurations.


teinemaa

a year ago

Any updates on when can we expect this on existing environments?


a year ago

No updates, sorry. The previous message I sent would still be the status quo.


abdallahadel667

a year ago

What is the status on this feature ? When is it going to be shipped?


a year ago

IPv4 private networking is GA for all new environments.


paddyfink

10 months ago

Hi team, is there a timeline for extending this feature to existing environments? Understanding the ETA would help us plan accordingly, as recreating our environments from scratch would require significant effort.


10 months ago

We are not able to offer an ETA at this time, apologies.


gunni

10 months ago

Note that I would prefer not having IPv4 anywhere so have Legacy IP be optional please 🙂


Anonymous

8 months ago

ETA?


martinuhe

8 months ago

Any rough indication of a timeline? This soon becoming a dealbreaker for a good chunk of our infrastructure.


brody

We are not able to offer an ETA at this time, apologies.

paddyfink

5 months ago

It's been 6 months now. If it is not coming, let's just be clear about it so that we can explore alternatives.

Is it a way to duplicate an environment and copy the volume attached to services, or do we have to do it manually?


handofgod94

2 months ago

+1 on this. Any ETA? Many popular tools have known limitation with ipv6 e.g. Dagster (a data pipeline orchestrator, uses uvicorn, and uvicorn has known issues with ipv6. I can't swap it out either to hyepercorn (which supports ipv6 + ipv4 binding), because the tool doesn't expose this. )


Welcome!

Sign in to your Railway account to join the conversation.

Loading...