2 hours ago
Hi Railway team,
Our Railway-hosted app is healthy and reachable worldwide, but users on Russian networks cannot connect. Their requests fail during the TLS handshake with a connection reset (curl: "Recv failure: Connection was reset"), before any HTTP response is returned.
Project / service: Rift (web service), environment: production
Railway service domain: riftscripts.up.railway.app
Current inbound edge IP (DNS): [INSERT HERE — run: nslookup riftscripts.up.railway.app]
Details:
- The app and health checks are healthy; the *.up.railway.app domain returns HTTP 200 from Germany, the US and other regions.
- Only clients on Russian ISPs are affected. The connection is reset at the TLS ClientHello, before it reaches our application.
- This matches the known pattern where certain edge IPs in 69.46.46.0/24 are blackholed / reset by Russian ISPs, while other IPs in the same range stay reachable from Russia.
Our service is accessed programmatically by installed clients over plain HTTPS GET, so a stable, Russia-reachable edge is important for us.
Could you please reassign our domain / service to an edge IP that is reachable from Russian networks, or advise how we can land on one? I'm happy to test any candidate IP from an affected Russian network.
Thanks a lot!
1 Reply
2 hours ago
We can't assign or exclude specific edge IPs for a service or domain. Our public domains use a shared anycast pool, so the IP a hostname resolves to can change at any time, and redeploying or changing regions won't move you onto a particular edge IP. We also can't lift filtering that Russian ISPs apply on their own networks.
To tell whether the filtering is by IP or by SNI, have an affected user force the hostname onto a different edge IP with curl --resolve. If another IP works, the ISP is filtering by IP. If every IP fails for this hostname, it is filtering by SNI.
The lasting fix is to put a proxy or CDN in front of your service, on a custom domain, using IPs your Russian users can reach. Your installed clients should connect by hostname, not a hardcoded IP.
Status changed to Awaiting User Response Railway • about 2 hours ago