Quote:
Originally Posted by bastyr
[You must be logged in to view images. Log in or Register.]
|
wow thanks for that. Just to check I ran a VPN through a Hong Kong server (the article stated that the Hong Kong conenction does not go via the damaged cable but rather the Australia-Japan cable). No packet loss (but even worse potato ping, as expected).
Apparently TPG is routing through Japan cable but doing a horrible job (hence the packet loss)
Hong Kong VPN:
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.4.0.1 - 0 | 133 | 133 | 225 | 229 | 253 | 229 |
| 103-10-197-185.pacswitch.com - 0 | 133 | 133 | 226 | 236 | 426 | 229 |
| 10ge6-4.core1.hkg1.he.net - 1 | 133 | 132 | 227 | 234 | 283 | 238 |
| 10ge1-1.core1.lax2.he.net - 1 | 133 | 132 | 386 | 410 | 483 | 411 |
| 100ge2-1.core1.lax1.he.net - 1 | 133 | 132 | 381 | 393 | 432 | 386 |
| 100ge15-2.core1.ash1.he.net - 1 | 133 | 132 | 440 | 458 | 580 | 446 |
| 100ge5-1.core1.nyc4.he.net - 1 | 133 | 132 | 447 | 457 | 494 | 455 |
| 10ge5-1.core1.nyc6.he.net - 1 | 133 | 132 | 447 | 460 | 501 | 479 |
| nyiix.gi3-6.cr1.nyc1.choopa.net - 2 | 133 | 131 | 448 | 458 | 490 | 452 |
| 108.61.244.201 - 0 | 132 | 132 | 445 | 455 | 488 | 476 |
| 108.61.244.50 - 0 | 132 | 132 | 445 | 456 | 579 | 452 |
| vl203-cr1.ewr3.choopa.net - 0 | 132 | 132 | 447 | 456 | 499 | 452 |
| 170.rogean.com - 0 | 132 | 132 | 449 | 455 | 518 | 451 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )
TPG (no VPN):
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 136 | 136 | 0 | 4 | 32 | 1 |
| 10.20.21.182 - 0 | 136 | 136 | 13 | 19 | 409 | 15 |
| 202.7.173.33 - 1 | 136 | 135 | 13 | 22 | 300 | 15 |
| syd-sot-ken-int2-be-10.tpgi.com.au - 0 | 136 | 136 | 14 | 22 | 360 | 16 |
| 10ge3-7.core1.sjc1.he.net - 1 | 136 | 135 | 159 | 172 | 419 | 161 |
| 10ge7-2.core1.sjc2.he.net - 1 | 136 | 135 | 160 | 178 | 370 | 197 |
| 100ge1-2.core1.nyc4.he.net - 12 | 136 | 121 | 240 | 253 | 400 | 249 |
| 10ge5-1.core1.nyc6.he.net - 8 | 136 | 126 | 240 | 259 | 497 | 260 |
| nyiix.gi3-6.cr1.nyc1.choopa.net - 10 | 136 | 123 | 245 | 259 | 486 | 250 |
| 108.61.244.201 - 6 | 136 | 129 | 223 | 254 | 415 | 248 |
| 108.61.244.50 - 8 | 135 | 125 | 238 | 256 | 364 | 249 |
| vl203-cr1.ewr3.choopa.net - 0 | 135 | 135 | 221 | 225 | 242 | 224 |
| 170.rogean.com - 9 | 135 | 124 | 225 | 254 | 390 | 238 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )
I can confirm that I can log in via Hong Kong VPN but not via the open TPG connection. It also looks like EQ can't handle packet loss approaching ~10% (but is ok upto ~5%).