Australian Test Gateway Feedback (Updated)
|
so to compare, here's my tracert from when the gateway first came online. note the difference between hops 6 and 7 in these two.
old tracert 50ms
Tracing route to 119.252.190.195 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.1.1 2 * * * Request timed out. 3 11 ms 11 ms 12 ms lo0.internet.ivpn.pe19.telstraclear.net (218.101.61.100) 4 19 ms 23 ms 21 ms ie2-g-0-0-0.telstraclear.net (203.98.50.2) 5 19 ms 18 ms 20 ms ge-0-2-0-1.xcore1.acld.telstraclear.net (203.98.50.251) 6 20 ms 20 ms 21 ms unknown.telstraglobal.net (134.159.174.37) 7 18 ms 36 ms 21 ms i-9-0-0.tauc-core01.bi.telstraglobal.net (202.84.219.126) 8 61 ms 47 ms 48 ms i-0-1-4-1.sydo-core02.bx.telstraglobal.net (202.84.140.181) 9 48 ms 49 ms 44 ms tengige0-1-0-13.oxf-gw1.sydney.telstra.net (203.50.13.121) 10 60 ms 49 ms 66 ms bundle-ether1.ken-core4.sydney.telstra.net (203.50.6.5) 11 44 ms 46 ms 50 ms tengigabitethernet8-1.ken17.sydney.telstra.net (203.50.20.27) 12 45 ms 47 ms 53 ms aaptli4.lnk.telstra.net (110.142.0.198) 13 51 ms 46 ms 46 ms lag40.sclarinte01.aapt.net.au (202.10.14.195) 14 56 ms 46 ms 49 ms border2.wtl.sisgroup.com.au (203.174.185.162) 15 46 ms 50 ms 46 ms bdr.mx1.eqx.sis.net.au (122.252.0.193) 16 45 ms 46 ms 46 ms 122.252.3.233 17 55 ms 45 ms 46 ms 119.252.190.195
current tracert 200ms
Tracing route to 119.252.190.195 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.1.1 2 * * * Request timed out. 3 12 ms 18 ms 10 ms lo0.internet.ivpn.pe19.telstraclear.net [218.101.61.100] 4 18 ms 20 ms 21 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2] 5 19 ms 19 ms 21 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 6 19 ms 19 ms 20 ms unknown.telstraglobal.net [134.159.174.37] 7 148 ms 147 ms 147 ms i-0-6-1-0.tlot-core01.bx.telstraglobal.net [202.84.142.157] 8 146 ms 147 ms 143 ms i-0-0-0-4.eqla01.bi.telstraglobal.net [202.40.149.206] 9 148 ms 146 ms 149 ms nlayer-peer.eqla01.pr.telstraglobal.net [134.159.61.42] 10 168 ms 153 ms 151 ms as32421.xe-9-0-2.ar1.lax1.us.nlayer.net [69.31.127.122] 11 151 ms 151 ms 149 ms 199.59.167.122 12 150 ms 150 ms 155 ms 208.64.127.133 13 * * * Request timed out. 14 196 ms 195 ms 198 ms 119.252.190.195 in the good one the telstraglobal host routes to sydney and then through to the gateway fine, the current one routes goodness knows where but definitely not through the same path. hop 10 on that slow trace hits an US host in LA so something is definitely not correct. looks like a configuration/dns issue with telstraglobal on our side of the ditch (hop 6 has to be in nz for that ping) the timeouts usually arent an issue, can just be an indicator that the host isn't set to respond to packets that tracert issues. tbh im not sure why your trace looks like that. are you in NZ? most of those hops appear to be US networks. |
|
|
yes i'm in NZ. also using Telstra Clear(Vodafone). i live south-east of Auckland in Te Aroha. yes you are right our tracert look completely different. if it matters i'm using adsl2.
1 0 0 0 ***.***.**.** - 2 0 0 0 64.124.196.225 xe-4-2-0.er2.dfw2.us.above.net 3 3 3 3 77.67.71.165 ae2-109.dal33.ip4.tinet.net 4 42 41 41 89.149.184.169 xe-9-2-0.lax20.ip4.tinet.net 5 43 49 48 199.229.230.62 giglinx-gw.ip4.tinet.net 6 45 46 45 199.59.167.122 - 7 42 41 41 208.64.127.133 - 8 Timed out Timed out Timed out - 9 231 231 231 119.252.190.195 - Trace complete very strange i'm not getting any US addresses in my tracert. seems to be going straight to AUS somehow gaining close to 200ms in the final hop |
|
|
are you sure? you're not remote logged into a terminal on a VPN or something weird?
that first address in your tracert (hop 2) goes to 64.124.196.225 and you can use this site to confim that above.net is in the US, specifically in New York. http://www.iplocation.net/index.php so I am completely confused how your trace is originating from there if you're in Te Aroha :D if i ping that address i get ~193ms result so yeah. it's in the US. and the tinet ones i believe are on the west coast US. Last edited by ualac#0162 on May 31, 2013, 10:11:35 PM
|
|
|
what the heck indeed you are right. maybe im infected with some sort of trojan or something. i'm not on any vpn that i am aware of. ill try a tracert to the aue poe server from a different terminal
|
|
|
ok it seems the tracert program i was using was messing with my results. here is a windows cmd tracert. hop 6 to 8 is taking me to Hong Kong, hop 8 to 13 are all US locations.
Spoiler
1 2 ms 2 ms 2 ms RTA1025W.home [192.168.1.1] 2 18 ms 18 ms 14 ms 121-75-0-1.telstraclear.net [121.75.0.1] 3 109 ms 14 ms 38 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2] 4 15 ms 15 ms 17 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 5 17 ms 15 ms 14 ms unknown.telstraglobal.net [134.159.174.41] 6 141 ms 143 ms 140 ms i-0-0-4-0.tlot-core01.bx.telstraglobal.net [202.84.142.118] 7 139 ms 139 ms 139 ms i-0-0-0-5.eqla01.bi.telstraglobal.net [202.40.149.210] 8 145 ms 149 ms 150 ms gblx-peer.eqla01.pr.telstraglobal.net [134.159.63.202] 9 152 ms 146 ms 145 ms PCCW.te6-2.1140.ar4.LAX1.gblx.net [64.211.206.226] 10 147 ms 147 ms 147 ms 63-218-72-142.static.pccwglobal.net [63.218.72.142] 11 146 ms 144 ms 144 ms 63-218-212-22.static.pccwglobal.net [63.218.212.22] 12 148 ms 146 ms 144 ms 199.59.167.122 13 145 ms 149 ms 144 ms 208.64.127.133 14 * * * Request timed out. 15 192 ms 190 ms 191 ms au.login.pathofexile.com [119.252.190.195] Last edited by stickyhuna#7761 on May 31, 2013, 10:55:00 PM
|
|
|
haha :) okay thats much better. at least the trace results look damn close to mine.
so something in the DNS/routes is bumping both of us north through asia rather than directly across to sydney. not sure how often the routes refresh, possibly overnight but other than hope i'm not sure what else we can do. i might try google's DNS when i get a chance to see if that helps any. |
|
|
yer hopefully they refresh soon. i noticed last night about 10pm my latency was sitting around 200ms rather than 50ms. A few minutes later i had my 50 latency back, then i looked this morning and again i was at 200ms.
|
|
|
Got pretty much exactly the same results using the google public dns.
Spoiler
1 2 ms 2 ms 2 ms 192.168.1.1 2 25 ms 25 ms 27 ms 121-75-0-1.telstraclear.net [121.75.0.1] 3 27 ms 16 ms 19 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2] 4 16 ms 53 ms 41 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 5 43 ms 46 ms 46 ms unknown.telstraglobal.net [134.159.174.41] 6 143 ms 156 ms 143 ms i-0-0-4-0.tlot-core01.bx.telstraglobal.net [202.84.142.118] 7 159 ms 189 ms 144 ms i-0-0-0-5.eqla01.bi.telstraglobal.net [202.40.149.210] 8 147 ms 148 ms 152 ms gblx-peer.eqla01.pr.telstraglobal.net [134.159.63.202] 9 153 ms 147 ms 148 ms PCCW.te6-2.1140.ar4.LAX1.gblx.net [64.211.206.226] 10 191 ms 200 ms 173 ms 63-218-72-142.static.pccwglobal.net [63.218.72.142] 11 153 ms 166 ms 152 ms 63-218-212-22.static.pccwglobal.net [63.218.212.22] 12 157 ms 175 ms 194 ms 199.59.167.122 13 146 ms 145 ms 149 ms 208.64.127.133 14 * * * Request timed out. 15 195 ms 192 ms 197 ms 119.252.190.195 C:\Users\Playtech> |
|
|
Just moved into a new apartment in Brisbane with an NBN connection. Average ~30ms. Very stable.
Any ETA on when we will be able to race using this gateway? |
|
|
there is one thing i can think of why my ping has gone from 50ms up to 200ms to the aus server. i changed from the telstra 150gig adsl2 plan to the vodafone 150gig plan. vodafone say they change plans on the first of the month. Thats the first time i noticed my ping going up.
|
|
