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.
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.
