Anyone with TPG getting latency problems with AUSGAMERS servers
This post has been removed.
Reason: Not Relevant |
07:44pm 16/04/14 Permalink
I haven't heard anything today about TPG specific issues, but I'll check with Malth and make sure nothing strange is going on.
|
07:48pm 16/04/14 Permalink
I'm no network expert by any means, but according to that traceroute the problem appears to be within Telstra's network, not TPG's.
8 14 ms 13 ms 14 ms Bundle-Ether13.ken-edge902.sydney.telstra.net [1 39.130.214.101] You can see where the milliseconds increase from about 14 to 155 there. Both servers are in sydney.telstra.net. I get an increase of about 50ms within Telstra's network when I traceroute ga0306.gamearena.com.au: Tracing route to ga0306.gamearena.com.au [203.46.105.70] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 54 ms 53 ms 53 ms nexthop.qld.iinet.net.au [203.215.9.250] 3 47 ms 55 ms 51 ms ae7.cr1.bne4.on.ii.net [150.101.33.158] 4 51 ms 52 ms 54 ms ae0.cr1.bne7.on.ii.net [150.101.33.5] 5 46 ms 47 ms 51 ms 119.225.11.117 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 49 ms 45 ms 37 ms 59.154.57.188 10 46 ms 53 ms 54 ms bundle-ether13.cha45.brisbane.telstra.net [139.1 30.61.73] 11 60 ms 60 ms 59 ms bundle-ether2.cha-core4.brisbane.telstra.net [20 3.50.44.13] 12 88 ms 86 ms 78 ms bundle-ether11.ken-core4.sydney.telstra.net [203 .50.11.72] 13 * * * Request timed out. 14 * * * Request timed out. 15 97 ms 89 ms 90 ms ga0412b.gamearena.com.au [203.46.105.70] Trace complete. |
08:19pm 16/04/14 Permalink
Funny, because the other few people on my server had good latencys, I just can't work it out. All other PC's on the network are doing the exact same thing. There are no programs eating my bandwidth, and have done the usual restart of the modem etc. I'm sure the issue is with Telstra itself, but why would I get great latencys until the last hop?
Also all other games run fine in terms of latency. strange! Sorry here is the full Tracert. Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\Sal>tracert 203.46.105.70 Tracing route to ga0412b.gamearena.com.au [203.46.105.70] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192-168-1-1.tpgi.com.au [192.168.1.1] 2 13 ms 13 ms 12 ms 10.20.22-405.tpgi.com.au [10.20.22.115] 3 13 ms 12 ms 13 ms syd-gls-har-agr2-tg-1-3.tpgi.com.au [203.219.17. 65] 4 13 ms 15 ms 15 ms syd-gls-har-crt1-tg-0-0-0-18.tpgi.com.au [202.7. 162.249] 5 12 ms 12 ms 12 ms 203-26-22-162.static.tpgi.com.au [203.26.22.162] 6 13 ms 15 ms 18 ms 203-219-35-5.static.tpgi.com.au [203.219.35.5] 7 15 ms 13 ms 14 ms te-0-10-0-18.sclarbrdr11.nw.aapt.net.au [203.8.1 83.25] 8 16 ms 15 ms 16 ms Bundle-Ether13.ken-edge902.sydney.telstra.net [1 39.130.214.101] 9 152 ms 151 ms 152 ms bundle-ether14.ken-core4.sydney.telstra.net [203 .50.11.96] 10 * * * Request timed out. 11 * * * Request timed out. 12 157 ms 156 ms 156 ms ga0412b.gamearena.com.au [203.46.105.70] Trace complete. |
08:32pm 16/04/14 Permalink
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved. C:\Users\Sal>ping bundle-ether14.ken-core4.sydney.telstra.net Pinging bundle-ether14.ken-core4.sydney.telstra.net [203.50.11.96] with 32 bytes of data: Reply from 203.50.11.96: bytes=32 time=154ms TTL=244 Reply from 203.50.11.96: bytes=32 time=152ms TTL=244 Reply from 203.50.11.96: bytes=32 time=152ms TTL=244 Reply from 203.50.11.96: bytes=32 time=154ms TTL=244 Ping statistics for 203.50.11.96: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 152ms, Maximum = 154ms, Average = 153ms C:\Users\Sal> |
08:37pm 16/04/14 Permalink
there's not really much you can do about it. it's not like there's someone you can call to see what the peers behind the edge of a particular segment are doing to congest that particular core router
tcp/ip wasn't built with low latency sensitive gaming in mind but rather for fairly linear information delivery |
09:07pm 16/04/14 Permalink
I had no issues before today.
I work for Telstra IT operations, so I may be able to find out what's going on. But this is not part of my segment :( |
09:11pm 16/04/14 Permalink
Here are the results from 2 different bf4 servers. The top one being Ausgamers 28thIMBI Server No Hacking - AusGamers.com 56/56 203.46.105.21:24255 XP2_001 and the second being a different provider. Any more clues?
Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\Sal>ping 203.46.105.21 Pinging 203.46.105.21 with 32 bytes of data: Reply from 203.46.105.21: bytes=32 time=156ms TTL=113 Reply from 203.46.105.21: bytes=32 time=157ms TTL=113 Reply from 203.46.105.21: bytes=32 time=157ms TTL=113 Reply from 203.46.105.21: bytes=32 time=156ms TTL=113 Ping statistics for 203.46.105.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 156ms, Maximum = 157ms, Average = 156ms C:\Users\Sal>ping 108.61.227.192 Pinging 108.61.227.192 with 32 bytes of data: Reply from 108.61.227.192: bytes=32 time=14ms TTL=119 Reply from 108.61.227.192: bytes=32 time=14ms TTL=119 Reply from 108.61.227.192: bytes=32 time=13ms TTL=119 Reply from 108.61.227.192: bytes=32 time=14ms TTL=119 Ping statistics for 108.61.227.192: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 14ms, Average = 13ms C:\Users\Sal> |
09:23pm 16/04/14 Permalink
ahahaha AHAHAHAH ahhaha ahhhhhhhh
Ausgamers 28thIMBI Server No Hacking worst server on the face of the planet. I used to play there all the time but man the lag just go so terrible it was unplayable. Especially on the larger maps. It was ok with maybe 20 people but anything over that and nope, forget it. Rubber banding everywhere. |
10:11pm 16/04/14 Permalink
Yeah. It's something that will affect almost everyone and not just yourself.
|
08:45am 17/04/14 Permalink
do you have an updated traceroute?
|
10:02am 17/04/14 Permalink
Sure do. This is from this morning 10:07am EST
Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\Sal>tracert 203.46.105.70 Tracing route to ga0412b.gamearena.com.au [203.46.105.70] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192-168-1-1.tpgi.com.au [192.168.1.1] 2 12 ms 13 ms 12 ms 10.20.22-405.tpgi.com.au [10.20.22.115] 3 13 ms 12 ms 12 ms syd-gls-har-agr2-tg-1-3.tpgi.com.au [203.219.17. 65] 4 13 ms 15 ms 15 ms syd-gls-har-crt1-tg-0-0-0-18.tpgi.com.au [202.7. 162.249] 5 13 ms 13 ms 13 ms 203-26-22-162.static.tpgi.com.au [203.26.22.162] 6 14 ms 15 ms 15 ms 203-219-35-5.static.tpgi.com.au [203.219.35.5] 7 14 ms 14 ms 13 ms te-0-10-0-18.sclarbrdr11.nw.aapt.net.au [203.8.1 83.25] 8 13 ms 14 ms 14 ms Bundle-Ether13.ken-edge902.sydney.telstra.net [1 39.130.214.101] 9 153 ms 154 ms 154 ms bundle-ether14.ken-core4.sydney.telstra.net [203 .50.11.96] 10 151 ms 152 ms 152 ms tel1360900.lnk.telstra.net [139.130.59.38] 11 * * * Request timed out. 12 155 ms 156 ms 156 ms ga0412b.gamearena.com.au [203.46.105.70] Trace complete. Notice Lines- 10, 11 (Which wasn't even responding yesterday) and 12 Also all other servers are fine, my server is the bottom one.. WTF Can someone else with a different provider in BF4 please search for server http://i153.photobucket.com/albums/s207/elalis/Untitled.jpg |
10:18am 17/04/14 Permalink
can you give me your ip and ill traceroute the reverse path from the server.
also, lines 10/11 don't respond on purpose. |
10:29am 17/04/14 Permalink
1 <1 ms <1 ms <1 ms 172.20.140.1
2 3 ms 3 ms 3 ms 10.248.165.189 3 * * * Request timed out. 4 9 ms 8 ms 8 ms 10.248.166.230 5 18 ms 6 ms 9 ms 110-175-234-89.static.tpgi.com.au [110.175.234.89] 6 6 ms 6 ms 7 ms 203-29-138-173.static.tpgi.com.au [203.29.138.173] 7 8 ms 7 ms 7 ms 203-219-35-69.static.tpgi.com.au [203.219.35.69] 8 13 ms 10 ms 12 ms te-0-10-0-18.sclarbrdr11.nw.aapt.net.au [203.8.183.25] 9 51 ms 66 ms 97 ms bundle-ether13.ken-edge902.sydney.telstra.net [139.130.214.101] 10 29 ms 21 ms 21 ms bundle-ether14.ken-core4.sydney.telstra.net [203.50.11.96] 11 6 ms 6 ms 7 ms tel1360900.lnk.telstra.net [139.130.59.38] 12 * * * Request timed out. 13 6 ms 6 ms 6 ms ga0412b.gamearena.com.au [203.46.105.70] Server won't respond to pings on Blog. There has always been issues around lnk.telstra.net prior to the game servers. It used to be called lnk518 when it was having massive issues about 6 months ago but they've since changed the DNS. |
10:30am 17/04/14 Permalink
from TPG
$ traceroute 203.46.105.70 traceroute to 203.46.105.70 (203.46.105.70), 30 hops max, 40 byte packets 1 110.232.115.2 (110.232.115.2) 0.234 ms 0.206 ms 0.220 ms 2 gw-tpg.mammoth.net.au (203.220.0.225) 2.694 ms 2.683 ms 2.672 ms 3 203-29-138-169.static.tpgi.com.au (203.29.138.169) 0.820 ms 0.813 ms 0.881 ms 4 203-219-35-69.static.tpgi.com.au (203.219.35.69) 2.582 ms 2.577 ms 2.564 ms 5 te-0-10-0-18.sclarbrdr11.nw.aapt.net.au (203.8.183.25) 1.715 ms 1.907 ms 2.515 ms 6 Bundle-Ether13.ken-edge902.sydney.telstra.net (139.130.214.101) 1.406 ms 1.816 ms 1.439 ms 7 bundle-ether14.ken-core4.sydney.telstra.net (203.50.11.96) 4.095 ms 1.718 ms 4.267 ms 8 tel1360900.lnk.telstra.net (139.130.59.38) 1.169 ms 0.981 ms 0.950 ms 9 ga0412b.gamearena.com.au (203.46.105.70) 1.061 ms 1.248 ms 1.246 ms from BP Cable Sydney # traceroute 203.46.105.70 traceroute to 203.46.105.70 (203.46.105.70), 30 hops max, 60 byte packets 2 nexthop.bigpond (10.209.192.1) 7.715 ms 7.731 ms 7.722 ms 3 2ndhop.bigpond (58.160.15.8) 9.157 ms 9.211 ms 14.082 ms 4 3rdhop.bigpond (58.160.15.238) 14.370 ms 14.595 ms 14.703 ms 5 4thhop.bigpond (172.18.117.38) 13.882 ms 13.890 ms 13.881 ms 6 5thhop.bigpond (172.18.117.45) 14.057 ms 13.736 ms 13.922 ms 7 TenGigE0-5-0-0.chw-edge902.sydney.telstra.net (139.130.207.81) 13.994 ms 10.691 ms 10.756 ms 8 bundle-ether14.chw-core2.sydney.telstra.net (203.50.11.100) 11.988 ms 12.118 ms 12.161 ms 9 tel1360900.lnk.telstra.net (139.130.59.38) 8.338 ms 12.730 ms 12.785 ms 10 * * * 11 ga0412b.gamearena.com.au (203.46.105.70) 12.345 ms 12.234 ms 12.443 ms |
10:31am 17/04/14 Permalink
1 <1 ms <1 ms <1 ms 172.20.140.1
2 3 ms 3 ms 3 ms 10.248.165.189 3 * * * Request timed out. 4 * * * Request timed out. 5 7 ms 6 ms 6 ms 110-175-234-89.static.tpgi.com.au [110.175.234.89] 6 5 ms 5 ms 5 ms 203-29-138-173.static.tpgi.com.au [203.29.138.173] 7 5 ms 5 ms 5 ms syd-gls-har-bras1-tg-0-1-0.tpgi.com.au [203.219.17.66] 8 18 ms 18 ms 18 ms 123-243-82-219.static.tpgi.com.au [123.243.82.219] Trace complete. ------ Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 Reply from 123.243.82.219: bytes=32 time=19ms TTL=53 Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 Reply from 123.243.82.219: bytes=32 time=18ms TTL=53 ----------- It's not you man. Do a few traces to other RSP servers and see if this issue happens everywhere would be my suggestion. |
10:35am 17/04/14 Permalink
I'm on Telstra Cable, all Battlefield 4 servers are responding with 20-30ms.
http://i.imgur.com/BHA0wwkl.png Tracing route to ga0412b.gamearena.com.au [203.46.105.70] |
10:36am 17/04/14 Permalink
it would appear TPG isn't advertising your subnet correclty and Telstra has no route for it but via OS. only TPG can fix that.
I'm no network expert by any means, but according to that traceroute the problem appears to be within Telstra's network, not TPG's. And this is why you need to see a traceroute in both directions before jumping to that conclusion. # traceroute 123.243.82.219 traceroute to 123.243.82.219 (123.243.82.219), 30 hops max, 40 byte packets 3 gigabitethernet3-3.ult1.sydney.telstra.net (165.228.157.41) 0.549 ms 0.609 ms 0.664 ms 4 bundle-ether7.chw-core2.sydney.telstra.net (203.50.20.129) 0.817 ms 0.810 ms 0.799 ms 5 bundle-ether1.oxf-gw2.sydney.telstra.net (203.50.6.90) 2.442 ms 2.437 ms 2.426 ms 6 203.50.13.38 (203.50.13.38) 2.983 ms 1.934 ms 1.901 ms 7 i-0-0-2-0.siko-core04.bx.telstraglobal.net (202.84.140.138) 123.745 ms 123.776 ms 123.769 ms 8 180.87.180.6 (180.87.180.6) 123.336 ms 123.938 ms 123.930 ms 9 ix-8-2-2-0.tcore1.TV2-Tokyo.as6453.net (180.87.180.5) 142.276 ms 142.257 ms 142.295 ms 10 if-3-2.tcore1.HK2-Hong-Kong.as6453.net (180.87.112.5) 145.050 ms 142.467 ms 144.401 ms 11 116.0.67.34 (116.0.67.34) 143.511 ms 141.033 ms 141.017 ms 12 203-26-22-170.static.tpgi.com.au (203.26.22.170) 147.906 ms 143.904 ms 144.542 ms 13 syd-gls-har-agr2-tg-1-1.tpgi.com.au (202.7.162.250) 141.382 ms 143.561 ms 141.315 ms 14 syd-gls-har-bras1-tg-0-1-0.tpgi.com.au (203.219.17.66) 142.168 ms 142.259 ms 143.589 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * |
10:36am 17/04/14 Permalink
Yet on the same test above mine worked fine and doesn't go OS. I'm on 10/10 business fibre though.
|
10:41am 17/04/14 Permalink
10:43am 17/04/14 Permalink
it would appear TPG isn't advertising your subnet correclty and Telstra has no route for it but via OS. only TPG can fix that. How would I even begin to explain this to TPG LOL |
10:43am 17/04/14 Permalink
Yet on the same test above mine worked fine and doesn't go OS. I'm on 10/10 business fibre though. your ip is in a different subnet. ISPs advertise via BGP the subnets of ips in their AS (their network, keeping things simple). they can vary what they tell different isps they connect to to shape their routing/traffic flows different ways. ISPs can only send traffic to an IP via a path they are told about. in this case, TPG isn't advertising 10000RR's ip's subnet to Telstra for whatever reason, most likely due to mis configuration. if 10000RR tells TPG about it, im sure they will fix it, but he needs to call them up and tell them because no doubt TPG haven't noticed. |
10:46am 17/04/14 Permalink
C:\Users\Sal>ping ns1.telstra.net
Pinging ns1.telstra.net [139.130.4.5] with 32 bytes of data: Reply from 139.130.4.5: bytes=32 time=154ms TTL=51 Reply from 139.130.4.5: bytes=32 time=154ms TTL=51 Reply from 139.130.4.5: bytes=32 time=153ms TTL=51 Reply from 139.130.4.5: bytes=32 time=154ms TTL=51 Ping statistics for 139.130.4.5: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 153ms, Maximum = 154ms, Average = 153ms C:\Users\Sal> Seems like anything Telstra related is getting the high MS. AUSGAMERS have been fantastic, not complaining at all about them, I know the issue lies somewhere else. |
10:46am 17/04/14 Permalink
How would I even begin to explain this to TPG LOL i would try calling, but first i would email trouble@ whois 123.243.82.219 |
10:50am 17/04/14 Permalink
LOL. Yeah I tried calling no help at all, it just got escalated. I also emailed trouble.
Any other TPG users here? |
11:42am 17/04/14 Permalink
if it costs tpg $1/GB to go one way or 2c/GB to go another way, without taking into account latency, they're probably going to route more the 2c/GB way
it might not be the cost though. aren't tpg advertising xbox 360/one packages or is that dodo? if they change the routes to be more direct to xbox live servers in the US, how can they differentiate pc gaming packets and then route them across a possibly more expensive peering port? no wonder you got escalated to somewhere's never never |
12:33pm 17/04/14 Permalink
on tpg
Pinging ns1.telstra.net [139.130.4.5] with 32 bytes of data: Reply from 139.130.4.5: bytes=32 time=35ms TTL=51 Reply from 139.130.4.5: bytes=32 time=34ms TTL=51 Reply from 139.130.4.5: bytes=32 time=36ms TTL=51 Reply from 139.130.4.5: bytes=32 time=37ms TTL=51 Ping statistics for 139.130.4.5: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 34ms, Maximum = 37ms, Average = 35ms Tracing route to ga0412b.gamearena.com.au [203.46.105.70] over a maximum of 30 hops: 1 2 ms 2 ms 1 ms 192-168-1-1.tpgi.com.au [192.168.1.1] 2 19 ms 19 ms 19 ms 10.20.21.173 3 19 ms 20 ms 19 ms bri-sot-wic-crt1-tengi-0-0-0.tpgi.com.au [203.29 .142.89] 4 28 ms 21 ms 21 ms 203-174-129-33.bri.static-ipl.aapt.com.au [203.1 74.129.33] 5 21 ms 21 ms 20 ms te2-3.bforvdist02.aapt.net.au [203.131.62.32] 6 21 ms 20 ms 20 ms te0-3-1-0.bqueecore01.aapt.net.au [202.10.12.25] 7 21 ms 20 ms 21 ms te2-2.bqueedist01.aapt.net.au [202.10.12.18] 8 21 ms 21 ms 20 ms bu8.bqueebrdr11.aapt.net.au [202.10.14.39] 9 19 ms 20 ms 19 ms gigabitethernet1-7.cha30.brisbane.telstra.net [1 39.130.64.97] 10 22 ms 22 ms 21 ms tengige0-8-0-2.cha-core4.brisbane.telstra.net [2 03.50.51.1] 11 38 ms 35 ms 35 ms bundle-ether11.ken-core4.sydney.telstra.net [203 .50.11.72] 12 34 ms 35 ms 34 ms tel1360900.lnk.telstra.net [139.130.59.38] 13 * * * Request timed out. 14 35 ms 33 ms 34 ms ga0412b.gamearena.com.au [203.46.105.70] Trace complete. |
02:11pm 17/04/14 Permalink
At this stage you're better off emailing them the link to this page lol.
|
02:15pm 17/04/14 Permalink
As it happens I was in TPG's NOC this afternoon for another matter and brought up this routing issue.
I forwarded on all the details and they said they would look into it. No change as yet. |
07:44pm 20/04/14 Permalink
Okay cool, because the issue is still here :( Very frustrating. I am trying to get my IP changed through TPG because I have a static address. Did they say when they will look into it by any chance?
|
10:17am 21/04/14 Permalink
Okay cool, because the issue is still here :( Very frustrating. I am trying to get my IP changed through TPG because I have a static address. Did they say when they will look into it by any chance? looks fixed now.. going back via aapt. # traceroute -A 123.243.82.219 traceroute to 123.243.82.219 (123.243.82.219), 30 hops max, 40 byte packets 3 gigabitethernet3-3.ult1.sydney.telstra.net (165.228.157.41) [AS1221] 0.511 ms 0.575 ms 0.626 ms 4 bundle-ether7.chw-core2.sydney.telstra.net (203.50.20.129) [AS1221] 2.026 ms 2.013 ms 2.004 ms 5 bundle-ether1.chw-edge901.sydney.telstra.net (203.50.11.99) [AS1221] 1.184 ms 1.421 ms 1.457 ms 6 aap1135271.lnk.telstra.net (139.130.209.230) [AS1221] 1.498 ms 1.398 ms 1.494 ms 7 * * * 8 59-100-203-74.syd.static-ipl.aapt.com.au (59.100.203.74) [AS2764] 5.429 ms 5.421 ms 5.412 ms 9 syd-gls-har-agr2-tg-1-2.tpgi.com.au (202.7.162.178) [AS7545/AS10026] 1.024 ms 1.052 ms 1.077 ms 10 syd-gls-har-bras1-tg-0-1-0.tpgi.com.au (203.219.17.66) [AS7545/AS9837] 0.986 ms 0.970 ms 0.947 ms 11 * * * 12 * * * |
04:57pm 21/04/14 Permalink
YAYYYYY it's fixed wohooooo :) SOLVED! Thanks so much.. wth was the issue and was it only me?
Tracing route to ga0412b.gamearena.com.au [203.46.105.70] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192-168-1-1.tpgi.com.au [192.168.1.1] 2 13 ms 13 ms 12 ms 10.20.22-405.tpgi.com.au [10.20.22.115] 3 13 ms 12 ms 13 ms syd-gls-har-agr2-tg-1-3.tpgi.com.au [203.219.1 65] 4 15 ms 15 ms 15 ms syd-gls-har-crt1-tg-0-0-0-18.tpgi.com.au [202. 162.249] 5 13 ms 13 ms 12 ms 203-26-22-162.static.tpgi.com.au [203.26.22.16 6 15 ms 15 ms 15 ms 203-219-35-5.static.tpgi.com.au [203.219.35.5] 7 13 ms 12 ms 12 ms te-0-10-0-18.sclarbrdr11.nw.aapt.net.au [203.8 83.25] 8 13 ms 13 ms 14 ms Bundle-Ether13.ken-edge902.sydney.telstra.net 39.130.214.101] 9 16 ms 17 ms 13 ms bundle-ether14.ken-core4.sydney.telstra.net [2 .50.11.96] 10 13 ms 13 ms 12 ms tel1360900.lnk.telstra.net [139.130.59.38] 11 * * * Request timed out. 12 12 ms 13 ms 13 ms ga0412b.gamearena.com.au [203.46.105.70] Trace complete. |
10:56pm 21/04/14 Permalink
according to the email they sent back to ara, your subnet was being advertised to pipe instead of aapt, which they fixed
it would've affected anyone within the same subnet, not just you |
11:08pm 21/04/14 Permalink
I am on TPG and have some latency spikes late night. But really, TPG internet quality really depends on the area where you connected. NSW is generally the one experiencing network overloads.
|
01:57pm 18/09/14 Permalink
