Hello,
I have checked this case. It seems that connection between pccw and hinet is saturated in one direction. I have modified outbound routing towards your provider via PCCW and I have noticed packet loss. As you can see latency was similar to current one via PCCW. I have rolled back changes in routing. It seems that path via NTT is currently the best from all available paths.
root@sgp1:~# mtr 36.234.138.131 βreport-wide -c 10
Start: Fri Nov 4 09:34:38 2016
HOST: sgp1 Loss% Snt Last Avg Best Wrst StDev
1.|β 128.199.191.254 0.0% 10 0.5 0.4 0.3 0.5 0.0
2.|β 138.197.250.210 0.0% 10 0.4 0.3 0.2 0.4 0.0
3.|β 138.197.250.199 0.0% 10 0.4 3.1 0.3 27.5 8.5
4.|β te0-0-0-13.br03.sin02.pccwbtn.net 0.0% 10 3.4 2.3 1.9 3.4 0.3
5.|β TenGE0-1-0-0.br04.hkg05.pccwbtn.net 0.0% 10 42.7 41.9 41.5 42.8 0.0
6.|β 211-22-33-78.HINET-IP.hinet.net 30.0% 10 131.6 143.4 131.6 155.3 10.5
7.|β r4103-s2.tp.hinet.net 50.0% 10 128.6 140.1 128.6 158.1 11.0
8.|β 220-128-13-22.HINET-IP.hinet.net 20.0% 10 131.1 141.3 131.1 158.0 10.3
9.|β r4101-s2.tp.hinet.net 20.0% 10 140.5 142.1 134.7 155.1 6.6
10.|β 220-128-17-85.HINET-IP.hinet.net 30.0% 10 136.3 142.0 136.3 149.3 5.4
11.|β tchn-3302.hinet.net 10.0% 10 131.0 137.6 129.8 151.5 6.7
12.|β h33.s145.ts.hinet.net 20.0% 10 133.5 138.9 128.1 153.2 8.5
13.|β 36-234-138-131.dynamic-ip.hinet.net 20.0% 10 128.7 134.8 128.7 144.1 5.6
β
Best regards,
Kamil Derynski