Skip to content
Russian ISP connectivity issue – 69.46.46.62
amnesia
OP

a month ago

Hello!

I’m experiencing a regional connectivity issue with one of my Railway-generated service domains:

bluester.up.railway.app → 69.46.46.62

Some users from Russian ISPs cannot reach this endpoint. The connection fails before the application responds.

What makes this interesting is that I have several other Railway-generated domains on different edge IPs, and one of them is reachable normally from the same Russian networks:

Affected:

bluester.up.railway.app → 69.46.46.62

https://check-host.net/check-ping?host=bluester.up.railway.app

Working Railway-generated domain:

bulka.up.railway.app → 69.46.46.41

https://check-host.net/check-ping?host=bulka.up.railway.app

Other services on my account:

jup-backend-production.up.railway.app → 69.46.46.51

https://check-host.net/check-ping?host=jup-backend-production.up.railway.app

blstrplbk.up.railway.app → 69.46.46.9

https://check-host.net/check-ping?host=blstrplbk.up.railway.app

So this does not appear to be a general issue with Railway-generated domains from Russia. The problem seems to be specific to the edge/IP assignment of bluester.up.railway.app.

There are also multiple Railway Station reports describing similar connectivity problems from Russian ISPs involving 69.46.46.x edge addresses:

https://station.railway.com/questions/russian-tls-timeouts-on-69-46-46-123-sa-72466846

https://station.railway.com/questions/custom-domain-resets-connections-from-ru-db75648d

https://station.railway.com/questions/regional-tcp-443-reachability-failure-f-262e4532

https://station.railway.com/questions/69-46-46-0-24-unroutable-from-a-russian-14b3ff76

https://station.railway.com/questions/custom-domain-fails-on-russian-mobile-ne-354c2352

https://station.railway.com/questions/subject-inbound-edge-ip-69-46-46-104-fo-33d1fa11

https://station.railway.com/questions/custom-domain-tls-timeout-on-hikari-edge-2f9e4652

The hostname bluester.up.railway.app is hardcoded into already-distributed client applications, so changing clients to a custom domain is currently not possible.

I understand that Railway cannot fix ISP-side routing globally. However, I would like to know whether there is any Railway-side option to change the edge/IP assignment for this specific service while keeping the exact same hostname.

Could a Railway engineer please check whether any of the following is possible?

  • move bluester.up.railway.app to another edge/IP;
  • reassign the generated domain to a different edge;
  • reprovision/migrate the service in a way that changes its public edge assignment without changing the hostname;
  • any other internal workaround that could make this specific hostname reachable from the affected Russian networks.

I would specifically appreciate a human engineer reviewing this case, since the automated response does not address whether there are any internal options for a specific service/domain.

Thank you!

Solved$10 Bounty

Pinned Solution

Unfortunately, there isn’t anything Railway can do about the block (including changing the host IP assignment). Your only option would be to use a VPN.

3 Replies

Railway
BOT

a month ago

We checked your service's domain, and it is reachable through our edge from outside Russia. The behavior you describe matches ISP-side filtering: some Russian ISPs drop specific edge IPs in that range. That filtering happens on the ISP's side, and we have no way to lift it.

We also cannot assign a specific edge IP to a service or keep one away from it. Redeploying or changing regions does not change the edge IP a generated domain resolves to.

The fix that lasts is a proxy or CDN in front of the service whose IPs those users can reach. That only works for a hostname whose DNS you control, though, so it means pointing the distributed clients at a custom domain. You don't need to send traceroutes for this, since they would not change what we can do on our side.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway

We checked your service's domain, and it is reachable through our edge from outside Russia. The behavior you describe matches ISP-side filtering: some Russian ISPs drop specific edge IPs in that range. That filtering happens on the ISP's side, and we have no way to lift it. We also cannot assign a specific edge IP to a service or keep one away from it. Redeploying or changing regions does not change the edge IP a generated domain resolves to. The fix that lasts is a proxy or CDN in front of the service whose IPs those users can reach. That only works for a hostname whose DNS you control, though, so it means pointing the distributed clients at a custom domain. You don't need to send traceroutes for this, since they would not change what we can do on our side.

amnesia
OP

a month ago

I still need help, please.

I understand the automated explanation about ISP-side filtering, but my question is specifically whether Railway has any internal way to change the edge/IP assignment of my existing generated domain while keeping the exact same hostname.

bluester.up.railway.app → 69.46.46.62

I have another Railway-generated domain:

bulka.up.railway.app → 69.46.46.41

which is reachable normally from the same Russian networks.

Since the affected hostname is hardcoded into already-distributed clients, a custom-domain/CDN solution is not currently usable for existing users.

Please escalate this to a human Railway engineer who can confirm whether there is any service-specific workaround, reprovisioning option, or edge reassignment available internally.

Thank you.


Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • about 1 month ago


Unfortunately, there isn’t anything Railway can do about the block (including changing the host IP assignment). Your only option would be to use a VPN.


Status changed to Solved 0x5b62656e5d • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...