I noticed a huge impact to the ping when the undergound fibre cable linking Perth and Singapore was damaged around Sept last year, this is to be expected as all international traffic out of perth was now being routed out via Sydney. You can find some information on the fibre link here: https://en.wikipedia...iki/SEA-ME-WE_3
The latency prior to this was around 60-70ms to 101.100.201.86 (singapore) and 300-350 to 192.99.40.107 (Canada)
Since then however I have always been 220 ish to Oceanic and 470+ms to the NA servers, which makes Community Warfare almost unplayable..
Here is an example of the path taken by the traffic from the Telstra Network.
Firstly to 101.100.201.86 (singapore) AVG 211!!!
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dsldevice.gateway - 0 | 19 | 19 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| 144.130.216.210 - 0 | 19 | 19 | 18 | 20 | 26 | 20 |
|bundle-ether7.wel-core3.perth.telstra.net - 0 | 19 | 19 | 20 | 24 | 27 | 24 |
|tengige0-8-0-5-1.pie-core1.perth.telstra.net - 0 | 19 | 19 | 18 | 20 | 24 | 19 |
| 203.50.9.2 - 0 | 19 | 19 | 18 | 20 | 25 | 21 |
|i-0-5-4-0.skdi-core01.bx.telstraglobal.net - 0 | 19 | 19 | 66 | 71 | 76 | 69 |
| i-0-3-0-0.6ntp02.bi.telstraglobal.net - 0 | 19 | 19 | 72 | 73 | 77 | 73 |
| 203.116.5.157 - 0 | 19 | 19 | 66 | 69 | 78 | 67 |
| 203.118.15.186 - 0 | 19 | 19 | 66 | 70 | 76 | 69 |
| an-ats-int11.starhub.net.sg - 0 | 19 | 19 | 67 | 71 | 77 | 70 |
| sh2.nc1.sg.vodien.com - 0 | 19 | 19 | 66 | 69 | 81 | 68 |
| 86.201.100.101.in-addr.arpa - 7 | 15 | 14 | 207 | 211 | 222 | 214 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Now this is the interesting part - the traffic to sh2.nc1.sg.vodien.com looks fine! its 69ms round trip average. But the next hop is over 200ms! Either that hop is oversubscribed or perhaps the return traffic is routing A-symmetrically.
I will now compare this with another Perth Western Australian based ISP - AMCOM.
To compare with AMCOMS routing I connect via a high speed local VPN to an AMCOM internet connection, I get the following:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 116.212.203.38 - 0 | 14 | 14 | 20 | 23 | 27 | 25 |
| 116.212.211.237 - 0 | 14 | 14 | 21 | 33 | 47 | 29 |
| te7-4.cr01.wa.amcom.net.au - 0 | 14 | 14 | 27 | 63 | 333 | 27 |
| te3-2.br02.wa.amcom.net.au - 0 | 14 | 14 | 20 | 43 | 171 | 21 |
|ten-0-0-0-823.bdr01.per02.wa.VOCUS.net.au - 0 | 14 | 14 | 21 | 24 | 28 | 23 |
| ten-0-2-0-1.cor01.per02.wa.VOCUS.net.au - 0 | 14 | 14 | 68 | 71 | 76 | 74 |
| so-0-0-0-0.bdr01.sin01.sin.VOCUS.net - 67 | 3 | 1 | 0 | 68 | 68 | 68 |
| 27.111.228.136 - 0 | 14 | 14 | 72 | 75 | 80 | 73 |
| sh2.nc1.sg.vodien.com - 0 | 14 | 14 | 68 | 73 | 81 | 70 |
| 86.201.100.101.in-addr.arpa - 0 | 14 | 14 | 69 | 75 | 83 | 71 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
This is only 75 ms!! This is 150ms better! We can also see that the link between sh2.nc1.sg.vodien.com and 101.100.201.86 is NOT oversubscribed so it must be the return path that is incorrect..
Can you please have the ISP hosting your game servers check their routing tables to the Perth WA Telstra network?
Edited by 1 21 Giggawatts, 08 March 2016 - 10:48 PM.