a month ago
Hi Railway team,
Symptom: Users in Colombia and Finland report our site https://moatdip.com won't load on their normal connections. One user in Colombia confirmed it loads fine with a US-based VPN. The site works everywhere else we test (we checked from Bogotá, Medellín, Helsinki, and 20+ locations worldwide — all HTTP 200).
Setup:
- Custom domain: moatdip.com → zdizgifl.up.railway.app → 69.46.46.79 (anycast)
- Service runs in us-east4 (response header: x-railway-upstream-zone: railway/us-east4-eqdc4a)
- No Cloudflare/CDN in front of Railway
- Our domain is IPv4-only (no AAAA record) — both Colombia and Finland have heavy IPv6 adoption, so IPv6-only mobile clients may be affected too
What we observed:
- Colombia traffic enters at x-railway-edge: mia1 (Miami) / lax1
- Finland traffic enters at x-railway-edge: ams1 (Amsterdam)
- One test node in Bucharest consistently times out connecting to 69.46.46.79:443 (all other global nodes connect fine)
Questions:
- Are there known routing/peering problems between Railway's anycast range and Colombian (Claro/Tigo/Movistar) or Finnish (Elisa/DNA/Telia) ISPs?
- Does Railway support IPv6 (AAAA) on custom domains? Ours has none, and both countries have high IPv6 adoption.
Happy to provide deployment ID and traceroutes from the affected networks on request.
1 Reply
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
a month ago
Unfortunately, your only options would be to use Cloudflare's proxy (though you will need to migrate to Cloudflare DNS for this), or to use a VPN to access the site.
And to your questions, no and no.