an hour ago
Service in Southeast Asia (Singapore). Users on Telkom Indonesia (IndiHome, Kupang) reach our *.up.railway.app hostname at 153.52.255.65 through the Amsterdam edge: x-railway-edge: ams1 on every request, ping 236 ms. Forcing the same hostname to 69.46.46.46 returns x-railway-edge: sin1, ping 86 ms.
Trace: 180.240.192.233 > 80.81.195.147 (core-backbone fra30) > 81.95.2.138 (ams10) > 169.150.195.64 > 79.127.194.83 > 153.52.255.65.
Measured 5 Nov 2026, 15:11-16:15 UTC, while incident QBCLHG1V is open.
Can you check this prefix's routing for Telkom so this traffic enters sin1? I can share the hostname privately if needed.
1 Replies
an hour ago
153.52.255.65 is one of our addresses, and 69.46.46.46 is our anycast edge address, which is why forcing the hostname there lands on sin1. Your trace shows the Telkom path handing traffic off in Frankfurt and Amsterdam before it reaches us, so those users enter the Amsterdam edge before the request ever gets to Singapore. We can't promise a routing change for a single provider's network, and nothing in your service's configuration controls which edge an ISP's traffic enters.
This is also separate from incident QBCLHG1V, which covers networks blocking our IP addresses, not which edge traffic arrives at.
The data that best shows the path is a run of our Network Diagnostics tool from an affected Telkom machine, along with a traceroute to 69.46.46.46 from that same connection. Telkom can act on this too, since their network chooses where the traffic is handed off.
Status changed to Awaiting User Response Railway • about 1 hour ago