Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 
Mr Snotty
8764 posts

Uber Geek

Moderator
Trusted
Lifetime subscriber

  # 1779344 10-May-2017 20:58
Send private message

The pings are looking pretty crap though however this isn't Spark either (see Smokeping), it is another ISP that also uses Global Gateway. I am also seeing rubbish pings and (some) packet loss on another connection in NZ that goes by a complete different route and uses different upstream providers so guess there is a cable cut or something.

 

Nothing that Spark can do, nothing that any other ISP can do. You've just got to note that unless if you own the complete fibre running from your PC right to the end destination that anything can go wrong and even if this was the case a cable cut can still occur or problems can still arise which would cause traffic to get routed elsewhere (if you had backup routes that was).

 

This is simply how the internet works. I've seen on your previous posts that you've complained multiple times about WOT on different ISP's but changing ISP's may fix things for a while however the problem will also eventually arise with them too. This isn't just WOT, this is happening with a VPS that I personally have hosted in Singapore which was seeing some packet loss to another VPS I also have in Australia and also Paris however due to the way TCP and Routing works this isn't an issue for what I need it for.

 

Afterall, you should still be able to play WOT fine. Your internet connection, the routing etc is simply working as designed.





334 posts

Ultimate Geek


  # 1779361 10-May-2017 21:50
One person supports this post
Send private message

 I don't see any issue with the trace route?

 

 

 

Heres mine on Spark UFB.

 

 

 

Tracing route to login.worldoftanks.asia [92.223.16.65]
over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms unknown [10.0.1.1]
2 1 ms 1 ms 1 ms 122-58-248-1.jetstream.xtra.co.nz [122.58.248.1]
3 2 ms 1 ms 1 ms mdr-ip24-int.msc.global-gateway.net.nz [122.56.116.6]
4 3 ms 2 ms 2 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 3 ms 2 ms 2 ms ae2-6.tkbr12.global-gateway.net.nz [122.56.127.17]
6 26 ms 25 ms 25 ms xe0-0-0.sebr3.global-gateway.net.nz [202.50.232.194]
7 26 ms 25 ms 25 ms 122.56.119.86
8 32 ms 30 ms 28 ms i-0-4-0-0.sydp01.bi.telstraglobal.net [202.84.223.10]
9 27 ms 28 ms 27 ms i-0-1-0-7.sydp-core03.bi.telstraglobal.net [202.84.223.9]
10 84 ms 86 ms 97 ms i-0-7-1-0.pthw-core01.bi.telstraglobal.net [202.84.143.146]
11 135 ms 132 ms 135 ms i-0-0-1-0.istt-core02.bx.telstraglobal.net [202.84.141.158]
12 132 ms 138 ms 133 ms i-0-0-0-0.istt03.bi.telstraglobal.net [202.84.243.74]
13 149 ms 130 ms 131 ms unknown.telstraglobal.net [202.127.73.118]
14 148 ms 155 ms 158 ms sg2-n5596-fe-1-vl231.fe.core.pw [92.223.116.163]
15 133 ms 130 ms 130 ms sg2-sl-a65.fe.core.pw [92.223.16.65]

 

Trace complete.


 
 
 
 


'That VDSL Cat'
10648 posts

Uber Geek

Trusted
Spark
Subscriber

  # 1779374 10-May-2017 22:46
Send private message

my apologizes for missing this one, i was off celebrating growing old this evening.. other have covered my position however.

 

 

 

from a technical side, i am not aware of any confirmed raised network outages, i do note there was mention earlier about the SG Perth cable being broken again though.

 

Assuming this is still looking like a problem tomorrow, i'll raise this with the tech teams.

 

 

 

however, routing appears to be via perth already.

 

1 * * *
2 * * *
3 ae8-10.akbr6.global-gateway.net.nz (122.56.116.5) 27.087 ms 27.498 ms 26.023 ms
4 ae2-6.tkbr12.global-gateway.net.nz (122.56.127.17) 25.673 ms
ae7-2.akbr7.global-gateway.net.nz (122.56.119.53) 67.346 ms
ae2-6.tkbr12.global-gateway.net.nz (122.56.127.17) 27.030 ms
5 xe0-0-4.sgbr3.global-gateway.net.nz (122.56.127.94) 51.673 ms
122.56.119.82 (122.56.119.82) 49.878 ms
ae1-10.tkbr12.global-gateway.net.nz (202.50.232.37) 30.209 ms
6 122.56.119.86 (122.56.119.86) 50.883 ms
ae7-10.sebr4.global-gateway.net.nz (122.56.127.214) 64.493 ms
122.56.119.86 (122.56.119.86) 64.251 ms
7 i-0-11-0-0.sydp01.bi.telstraglobal.net (202.84.220.210) 80.052 ms
i-0-4-0-0.sydp01.bi.telstraglobal.net (202.84.223.10) 53.231 ms 54.680 ms
8 i-0-1-0-7.sydp-core03.bi.telstraglobal.net (202.84.223.9) 52.484 ms
i-0-1-0-6.sydp-core03.bi.telstraglobal.net (202.84.220.209) 53.398 ms
i-0-11-0-0.sydp01.bi.telstraglobal.net (202.84.220.210) 53.621 ms
9 i-0-1-0-7.sydp-core03.bi.telstraglobal.net (202.84.223.9) 59.489 ms
i-0-7-1-0.pthw-core01.bi.telstraglobal.net (202.84.143.146) 106.768 ms
i-0-4-0-0.pthw-core01.bi.telstraglobal.net (202.84.137.122) 100.364 ms
10 i-0-1-4-0.istt-core02.bx.telstraglobal.net (202.84.141.154) 184.860 ms
i-0-3-0-0.istt-core02.bx.telstraglobal.net (202.84.137.30) 152.273 ms
i-0-1-4-0.istt-core02.bx.telstraglobal.net (202.84.141.154) 154.983 ms
11 i-0-0-1-0.istt03.bi.telstraglobal.net (202.84.243.94) 159.739 ms
i-0-0-0-0.istt03.bi.telstraglobal.net (202.84.243.74) 152.897 ms 152.315 ms
12 unknown.telstraglobal.net (202.127.73.118) 153.174 ms 150.367 ms 150.206 ms
13 sg2-n5596-fe-1-vl231.fe.core.pw (92.223.116.163) 150.254 ms 153.746 ms 153.196 ms

 

 

 

This route is near identical to my VF link

 

traceroute to 92.223.16.65 (92.223.16.65), 64 hops max, 40 byte packets
1 * 47-72-147-254.dsl.dyn.ihug.co.nz (47.72.147.254) 26.133 ms 20.973 ms
2 10.123.80.4 (10.123.80.4) 7.871 ms 7.318 ms 8.168 ms
3 10.123.80.9 (10.123.80.9) 38.705 ms 41.716 ms 43.768 ms
4 ten-0-0-2-2.bdr05.syd03.nsw.vocus.net.au (114.31.200.221) 47.377 ms 48.540 ms 37.343 ms
5 bundle-103.cor01.syd04.nsw.vocus.net.au (114.31.192.58) 39.672 ms
bundle-103.cor03.syd03.nsw.vocus.net.au (114.31.192.56) 33.255 ms 32.616 ms
6 bundle-100.bdr01.syd03.nsw.vocus.net.au (114.31.192.85) 50.481 ms
bundle-101.bdr01.syd03.nsw.vocus.net.au (114.31.192.87) 48.367 ms 56.488 ms
7 220.101.73.81 (220.101.73.81) 55.277 ms 47.328 ms 33.650 ms
8 * * *
9 59.154.142.28 (59.154.142.28) 61.627 ms
59.154.142.30 (59.154.142.30) 61.996 ms *
10 Bundle-Ether16.ken-edge901.sydney.telstra.net (139.130.28.253) 56.579 ms
Bundle-Ether32.chw-edge901.sydney.telstra.net (139.130.40.49) 47.769 ms 33.595 ms
11 bundle-ether13.chw-core10.sydney.telstra.net (203.50.11.98) 48.278 ms
bundle-ether2.chw-edge901.sydney.telstra.net (203.50.11.103) 50.962 ms 57.655 ms
12 bundle-ether8.exi-core10.melbourne.telstra.net (203.50.11.125) 62.075 ms 50.965 ms
bundle-ether13.chw-core10.sydney.telstra.net (203.50.11.98) 42.458 ms
13 bundle-ether8.exi-core10.melbourne.telstra.net (203.50.11.125) 67.062 ms
bundle-ether5.way-core4.adelaide.telstra.net (203.50.11.92) 113.618 ms 102.617 ms
14 bundle-ether5.way-core4.adelaide.telstra.net (203.50.11.92) 97.466 ms 109.294 ms *
15 tengige0-5-1-0.pthp-core01.perth.net.reach.com (203.50.13.254) 153.375 ms
bundle-ether5.pie-core1.perth.telstra.net (203.50.11.17) 121.469 ms 129.667 ms
16 tengige0-5-1-0.pthp-core01.perth.net.reach.com (203.50.13.254) 112.919 ms 164.254 ms
i-0-4-2-0.sgpl-core01.bx.telstraglobal.net (202.84.143.94) 187.985 ms
17 i-0-0-0-19.istt04.bi.telstraglobal.net (202.84.224.213) 216.035 ms
unknown.telstraglobal.net (202.84.224.198) 171.935 ms
unknown.telstraglobal.net (202.84.224.194) 183.384 ms
18 unknown.telstraglobal.net (202.84.224.190) 178.946 ms
unknown.telstraglobal.net (202.84.224.186) 237.974 ms *
19 i-0-0-2-2.istt03.bi.telstraglobal.net (202.84.219.182) 162.980 ms
unknown.telstraglobal.net (202.127.73.118) 138.698 ms 153.606 ms
20 unknown.telstraglobal.net (202.127.73.118) 132.253 ms 135.269 ms
sg2-n5596-fe-1-vl231.fe.core.pw (92.223.116.163) 134.306 ms

 

 

 

can you confirm for me a previous traceroute to prove this is any different to how it should be in your mind? 130ms-ish is about where i'd expect for sg off the top of my head, assuming its via the direct path.

 

 

 

take for example the sg steam content server, spark sits at 150ms while vf is sitting at 300ms. in terms of gaming traffic seems to be preforming as per normal.

 

i don't smoke WoT directly, but @michaelmurfy does go out the same routing so would be identical. - Apart from a slight blip earlier today i don't see anything out of the normal.

 

 

 

 

 

When i left the office, Queues i watch over had no wait times at all. i will agree with others, you are highly unlikely to get a csr who understands your issue enough to raise it to the correct places.





#include <std_disclaimer>

 

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.




43 posts

Geek


  # 1779418 11-May-2017 08:55
Send private message

Hi just checked with Pingplotter and it is now being routed via Perth again. Ping is 125ms with no packet loss.

 

If you check my traceroute that I previously posted it was hitting 200ms at some hops with a lot of packet loss.

 

Thanks for the response will mark your post as the answer.

 

 

 

Regards


19 posts

Geek


  # 1783960 18-May-2017 00:50
Send private message

Slightly off topic but since today my routing to the WoWs NA server appears to be via NZ -> Sydney -> Tokyo -> Hong Kong -> Tokyo (again lol) -> USA. Can any other Spark users share their traceroutes to worldofwarships.com?

 

Tracing route to worldofwarships.com [162.213.61.115]
over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    17 ms    11 ms     4 ms  125-239-xxx-x.jetstream.xtra.co.nz [125.239.xxx.x]
  3     *        *        *     Request timed out.
  4     3 ms     2 ms     3 ms  ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
  5     3 ms     1 ms     3 ms  ae7-2.akbr7.global-gateway.net.nz [122.56.119.53]
  6    28 ms    26 ms    27 ms  xe0-0-1.sgbr3.global-gateway.net.nz [202.50.232.110]
  7    27 ms    26 ms    26 ms  ae2-10.sgbr4.global-gateway.net.nz [202.50.232.246]
  8    26 ms    26 ms    27 ms  ae-3.a04.sydnau03.au.ra.gin.ntt.net [103.13.80.125]
  9    37 ms    29 ms    26 ms  ae-4.r21.sydnau03.au.bb.gin.ntt.net [202.68.64.124]
 10   145 ms     *      139 ms  ae-11.r31.tokyjp05.jp.bb.gin.ntt.net [129.250.5.34]
 11   142 ms   141 ms   142 ms  ae-2.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.5.23]
 12   236 ms     *      196 ms  ae-4.r24.tkokhk01.hk.bb.gin.ntt.net [129.250.2.51]
 13   218 ms   228 ms   241 ms  ae-1.r00.tkokhk01.hk.bb.gin.ntt.net [129.250.2.125]
 14   251 ms   239 ms   240 ms  ae-0.a00.tkokhk01.hk.bb.gin.ntt.net [129.250.2.128]
 15   298 ms   298 ms   299 ms  ix-ae-24-0.tcore1.HK2-Hong-Kong.as6453.net [180.87.112.153]
 16     *      324 ms   327 ms  if-ae-5-2.tcore1.TV2-Tokyo.as6453.net [180.87.112.206]
 17   318 ms   316 ms     *     if-et-21-2.hcore1.KV8-Chiba.as6453.net [120.29.217.67]
 18   316 ms   313 ms   316 ms  if-ae-24-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.144.56]
 19   291 ms   292 ms   289 ms  if-ae-5-2.tcore2.SQN-San-Jose.as6453.net [64.86.21.1]
 20   286 ms     *      237 ms  if-ae-1-2.tcore1.SQN-San-Jose.as6453.net [63.243.205.1]
 21   263 ms   271 ms   281 ms  216.6.33.122
 22   305 ms   304 ms   311 ms  92.223.120.163
 23   271 ms   282 ms   296 ms  sv4-sl-b115.fe.core.pw [162.213.61.115]


7 posts

Wannabe Geek


  # 1785307 20-May-2017 19:26
Send private message

Linkzor:

 

Slightly off topic but since today my routing to the WoWs NA server appears to be via NZ -> Sydney -> Tokyo -> Hong Kong -> Tokyo (again lol) -> USA. Can any other Spark users share their traceroutes to worldofwarships.com?

 

Tracing route to worldofwarships.com [162.213.61.115]
over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    17 ms    11 ms     4 ms  125-239-xxx-x.jetstream.xtra.co.nz [125.239.xxx.x]
  3     *        *        *     Request timed out.
  4     3 ms     2 ms     3 ms  ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
  5     3 ms     1 ms     3 ms  ae7-2.akbr7.global-gateway.net.nz [122.56.119.53]
  6    28 ms    26 ms    27 ms  xe0-0-1.sgbr3.global-gateway.net.nz [202.50.232.110]
  7    27 ms    26 ms    26 ms  ae2-10.sgbr4.global-gateway.net.nz [202.50.232.246]
  8    26 ms    26 ms    27 ms  ae-3.a04.sydnau03.au.ra.gin.ntt.net [103.13.80.125]
  9    37 ms    29 ms    26 ms  ae-4.r21.sydnau03.au.bb.gin.ntt.net [202.68.64.124]
 10   145 ms     *      139 ms  ae-11.r31.tokyjp05.jp.bb.gin.ntt.net [129.250.5.34]
 11   142 ms   141 ms   142 ms  ae-2.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.5.23]
 12   236 ms     *      196 ms  ae-4.r24.tkokhk01.hk.bb.gin.ntt.net [129.250.2.51]
 13   218 ms   228 ms   241 ms  ae-1.r00.tkokhk01.hk.bb.gin.ntt.net [129.250.2.125]
 14   251 ms   239 ms   240 ms  ae-0.a00.tkokhk01.hk.bb.gin.ntt.net [129.250.2.128]
 15   298 ms   298 ms   299 ms  ix-ae-24-0.tcore1.HK2-Hong-Kong.as6453.net [180.87.112.153]
 16     *      324 ms   327 ms  if-ae-5-2.tcore1.TV2-Tokyo.as6453.net [180.87.112.206]
 17   318 ms   316 ms     *     if-et-21-2.hcore1.KV8-Chiba.as6453.net [120.29.217.67]
 18   316 ms   313 ms   316 ms  if-ae-24-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.144.56]
 19   291 ms   292 ms   289 ms  if-ae-5-2.tcore2.SQN-San-Jose.as6453.net [64.86.21.1]
 20   286 ms     *      237 ms  if-ae-1-2.tcore1.SQN-San-Jose.as6453.net [63.243.205.1]
 21   263 ms   271 ms   281 ms  216.6.33.122
 22   305 ms   304 ms   311 ms  92.223.120.163
 23   271 ms   282 ms   296 ms  sv4-sl-b115.fe.core.pw [162.213.61.115]

 

 

Yup. I'm having similar problems (with WOT NA though). My ping times have gone from 160, down to 140 - then in the past week or so, jumped to 260-320. This seems to be a Spark (my ISP, though others may also be having problems) specific thing, as I can ping the login server (login-p2.worldoftanks.com) from my phone (Vodofone) at 180. I get a similar change in ping times to the WOT NA East servers also - about 100ms or more increase in lag. Makes the game pretty much unplayable. frown For some reason, Spark appears to be routing traffic away from the Southern Cross cable.


7 posts

Wannabe Geek


  # 1786239 22-May-2017 20:41
Send private message

It all seems to be good now. Pings are back to the 150-160 level to NA West.


1 | 2 
Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic



Twitter and LinkedIn »



Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:





News »

Intel expands 10th Gen Intel Core Mobile processor family
Posted 23-Aug-2019 10:22


Digital innovation drives new investment provider
Posted 23-Aug-2019 08:29


Catalyst Cloud becomes a Kubernetes Certified Service Provider (KCSP)
Posted 23-Aug-2019 08:21


New AI legaltech product launched in New Zealand
Posted 21-Aug-2019 17:01


Yubico launches first Lightning-compatible security key, the YubiKey 5Ci
Posted 21-Aug-2019 16:46


Disney+ streaming service confirmed launch in New Zealand
Posted 20-Aug-2019 09:29


Industry plan could create a billion dollar interactive games sector
Posted 19-Aug-2019 20:41


Personal cyber insurance a New Zealand first
Posted 19-Aug-2019 20:26


University of Waikato launches space for esports
Posted 19-Aug-2019 20:20


D-Link ANZ expands mydlink ecosystem with new mydlink Mini Wi-Fi Smart Plug
Posted 19-Aug-2019 20:14


Kiwi workers still falling victim to old cyber tricks
Posted 12-Aug-2019 20:47


Lightning Lab GovTech launches 2019 programme
Posted 12-Aug-2019 20:41


Epson launches portable laser projector
Posted 12-Aug-2019 20:27


Huawei launches new distributed HarmonyOS
Posted 12-Aug-2019 20:20


Lenovo introduces single-socket servers for edge and data-intensive workloads
Posted 9-Aug-2019 21:26



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.