N/A

According to this thread, Railway services should have no problem connecting to IPV6 databases

Though something to note, on Railway you are charged for network egress, so we don’t recommend communicating with external databases. Railway’s database templates are wide ranging and cover most use cases, so if you’re using Railway I’d recommend you use their databases as well

In that message, I am talking about connecting to Railway services from an IPv6 only network, not connecting out to an IPv6 only network from a Railway service.

So, to clarify, we do not support outbound IPv6, that is, connecting to an external IPv6-only service from a Railway service.

Out of curiosity is it due to a technical limitation or is it planned to be supported in the future ?

Purely just haven't implemented it yet because the need has not shown to be great enough at this time.

I think an important use is being able to connect to a supabase database from railway. i'm building an app where my customers input the db connection info and I connect to their DB.
seems like I can't communicate with DBs on supabase because of this ipv6 limitation. Now I must consider moving out of Railway because obviously asking my clients to move from supabase is not an option

Supabase does provide database connections that use IPv4.

It does but you got to upgrade to Pro Plan. 25$/month + 4$/month for the address location

So it's minimum 29$/month

Hey, as you have highlighted in the screenshot you have sent, Supabase offers a total of three options to connect to your Postgres database. The only option that is IPv6 only without add-ons is the direct connection. The other two pooler connection options are IPv4 compatible, with one of them being the suggested alternative to the direct connection when using IPv4.