Hi team,

Our frontend service is served through your edge network, and one of the edge IPs assigned to our custom domain is unreachable from a large part of our audience.

Affected domain: www.fibra-ai.com → CNAME 6cgv5xyy.up.railway.app → resolves to 69.46.46.104

The problem: 69.46.46.104 is dropped (100% packet loss) from multiple Russian mobile ISPs. Users on those networks get ERR_CONNECTION_TIMED_OUT. This is not a DNS, TLS, or SNI issue, and the domain is not in any Russian block registry — it's an IP-level blackhole of this specific shared edge IP (most likely collateral from another tenant on the same shared IP).

Evidence (all tests run from an affected Russian mobile network, same /24, all your edge IPs):

IP Our host ICMP ping Result

69.46.46.104 www.fibra-ai.com (6cgv5xyy.up.railway.app) 100% loss site times out

69.46.46.97 fibra-ai.com (yd6c1pnh.up.railway.app) replies reachable

69.46.46.115 fibra-ai-production.up.railway.app replies site loads fine

So only 69.46.46.104 is blackholed on these networks, while your neighboring edge IPs .97 and .115 respond normally. Switching Private DNS to dns.google did not help (rules out DNS), and ICMP carries no SNI/port, so the difference is purely at the IP level — not the domain name.

Request:

Please reassign a different inbound edge IP for our custom domain www.fibra-ai.com (a dedicated inbound IP would be ideal), so it no longer maps to the blocked 69.46.46.104.

Note: this is about the inbound edge IP that users connect to — not egress/static outbound IPs.