Singapore and Japan realms have random high ping instances.

This is so fucked up that you go from Hong Kong to Europe, through Europe, to Mumbai, and only then end up at GGG Japan or Singapore. Even with different DNS setups, as if your ISP is overriding your DNS selection (Google/Cloudflare), if I am not mistaken (the hops are the same).

As Fitzy_GGG pointed out "The problem looks to start on hop #4:" with your ISP there: "wtsc3a022.netvigator.com [...] 63-218-231-41.static.pccwglobal.net"

Have you tried the DNS Benchmark Tool ( https://www.grc.com/dns/benchmark.htm Download is at the bottom Where to go from here? )? Does it give you any other public DNS that is 'performant' than Google or Cloudflare?

PS: I googled some, and could not find indications the Netvigator/PCCW reroute traffic through Europe and back on purpose ( ... ?Beijing? ...).

The only thing I could find was this from September 2018 "Hong Kong PCCW latency issue" ( https://www.lowendtalk.com/discussion/comment/2880163/#Comment_2880163 ) With the same thing you have 200ms lag introduction early on @ Netvigator/PCCW's part/"hops."

It's either a technical oversight on their side (routing you through Europe and back to get to Japan or Singapore). Or in a very convoluted way something to do with peering/transit cost: it's cheaper for them to route you and others through Europe and back through India than directly and shorter from Hong Kong to Singapore/Japan. https://blog.cloudflare.com/the-relative-cost-of-bandwidth-around-the-world/

"

There are three primary reasons transit is so much more expensive in Asia. First, there is less competition, and a greater number of large monopoly providers. Second, the market for Internet services is less mature. And finally, if you look at a map of Asia you’ll see a lot of one thing: water. Running undersea cabling is more expensive than running fiber optic cable across land so transit pricing offsets the cost of the infrastructure to move bytes.

I also doubt that changing to IPv6 would change anything, as it would be the same hardware and DNS protocol/index/routing.

As Fitzy_GGG said, you have to call technical support, give them this thread (eg via a bit.ly or Google short url) and let them escalate it automatically to a higher level (their infrastructure guys). And let them explain you (1) why 200ms ping is introduced on their part, (2) why the detour through Europe and India, and (3) why when using in your home network router Google or Cloudflare DNS, why their DNS still shows up.

i stopped playing POE after Incursion because of this problem

i am amazed it is still happening. -_-*

Many tell me this is an ISP routing problem but if this truthly is the ISP routing problem then i would have never have a chance to connect to the low latency server :thinking: ......
to be honest GGG need to look at the server issue in singapre and japan fast cause if this still have happen then kiss good bye to Synthesis ....

"

zWhiteKz a écrit :

Many tell me this is an ISP routing problem but if this truthly is the ISP routing problem then i would have never have a chance to connect to the low latency server :thinking: ......
to be honest GGG need to look at the server issue in singapre and japan fast cause if this still have happen then kiss good bye to Synthesis ....

remove the tinfoil from your head, this IS NOT the server, you can see that in the test that was run SHOWING you which routes the connection takes, THAT has nothing to do with GGG.

And you are wrong in you assumption of how a routing problem occurs and may persist.
Most of the time it is due to connection problems in one of the hops that you would normally take to your "low latency" server.
This generally works like a motorway, if there is a problem that reduces traffic to one lane and lowers the speed or even just causes it to be closed then the traffic needs to go elsewhere.
In this case the quickest way to the destination (due to the problem and the resulting havoc it causes in surrounding infrastructure) is to take a hop that is clear (the US) then come back from another direction

These issues are cleared up over time by the ISP's or by the people who manage the cables, for SG there are frequent undersea cable cuts which can take months to repair depending on the weather.

hey dont need to be triggered bruh, i know how routing work ... i mean it already explain in the thread. All i try to say is it is vexing to know that u can connect to low latency instance and it an RNG fest for that connect. Also this doesnt happen JUST NOW it have been like this since Breach league for me, around new league time, connnection smooth but when mid/late league it became a mess with RNG server connect EVERY LEAGUE. :thinking: