Accessing a Worker from Indonesia served by LAX instead of the usual SIN edge location
Hi there -- I have a website (seniman.dev) that I deploy on Workers. The website would usually be served by the SIN edge location when accessing it from Indonesia at about 20ms latency, but as of yesterday the main website (and all the other Worker-deployed websites under the domain) would instead be served by the LAX edge location -- giving us 200ms latency.
Anything I can do from my side? The workload is very much latency-sensitive so accurate edge location routing is important.
Screenshot showing the edge location response headers is attached.
If it helps -- I'm using Telkom Indihome as my ISP.
3 Replies
unrelated to workers but might help drive the point of a more general routing misconfig: the same ISP gets SJC colocation center when connected to WARP.
the ISP is the largest in Indonesia.
I ran an MTR to your site from Global Ping (Global Ping link), which uses multiple probes. Most of them are routed to Singapore, while only one is routed to LAX, which belongs to PT Telekomunikasi Indonesia (AS7713) ISP (or any ISP using that ISP as an upstream). I believe this could indicate an issue on the ISP's side. If you can confirm the ASN of the ISP, I can share the NOC email where you can contact them regarding this routing issue.
I also ran an MTR on a Cloudflare WARP endpoint range (162.159.193.0/24), and all of them seem to be routed locally in Indonesia (162.159.193.5 MTR link). Cloudflare also uses two other endpoint ranges: 162.159.192.0/24 and 162.159.195.0/24. When I ran an MTR to both, they appeared to be routed to either Singapore or LAX if PT Telekomunikasi Indonesia (AS7713) is used as an upstream (162.159.192.5 MTR link and 162.159.195.5 MTR link).
It seems Cloudflare does not advertise these endpoints locally, resulting in routes going through either Singapore or LAX if an ISP uses PT Telekomunikasi Indonesia (AS7713) as an upstream. This points to a possible routing issue on your ISP's side.
thanks @Powerful845tiger -- fixed by signing up for Argo Smart Routing