Can someone from Spark please explain to me why Singapore traffic is suddenly being route via Hong Kong and not Perth?
Sick of waiting on the phone for support only to get someone who has no idea what I am talking about.
Regards
![]() ![]() ![]() ![]() |
|
I wouldn't expect call centre staff to be trained in international routing. Although being able to answer one such call every two years might be helpful...
45 minute wait followed by no joy.
Tried live chat and given a number to phone - will see what happen.
Also paste the traceroute here (presumably that's how you are determining it is going via Hong Kong?).
There could be many reasons not related to Spark e.g. DDoS of game servers requiring traffic scrubbing, change of upstream network provider and associated peering at the server end etc..
Spark sold their capacity on the SEA-ME-WE3 cable system about 3 years ago so I would not be expecting traffic to go via that cable system unless the remote party i.e. game server you are trying to reach has specifically purchased a route on the cable back to say peering in Sydney. As you may know they have instead invested in the Tasman Global Access cable system between Sydney and Auckland which has recently gone live, and presumably along with partners now have routes that reach Hong Kong via Guam.
Maybe you should post a trace route
Connection has always been routed via Perth and have had no issues for the last few years except for when the cable was cut.
Target Name: login.worldoftanks.asia
IP: 92.223.16.66
Date/Time: 10/05/2017 7:05:18 PM - 10/05/2017 7:15:18 PM
Hop Sent PL% Min Max Avg Host Name / [IP]
1 10 0 0.28 1.68 0.45 RT-N66U-ROUTER [192.168.1.1]
2 10 0 2.82 8.02 5.17 122-58-248-1.jetstream.xtra.co.nz [122.58.248.1]
3 5 80 2.26 2.26 2.26 mdr-ip24-int.msc.global-gateway.net.nz [122.56.116.6]
4 10 0 2.70 4.46 3.84 ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 10 0 1.82 5.62 2.88 ae2-6.tkbr12.global-gateway.net.nz [122.56.127.17]
6 10 0 25.59 28.40 26.82 xe1-0-2.sebr3.global-gateway.net.nz [202.50.232.114]
7 10 0 24.54 28.32 26.03 122.56.119.86 [122.56.119.86]
8 10 0 28.48 31.26 29.87 i-0-4-0-0.sydp01.bi.telstraglobal.net [202.84.223.10]
9 10 0 37.85 56.62 48.98 i-0-1-0-7.sydp-core03.bi.telstraglobal.net [202.84.223.9]
10 10 0 141.79 148.17 143.29 i-0-0-0-1.hkhh-core02.bx.telstraglobal.net [202.84.249.125]
11 10 0 185.13 207.84 197.29 i-0-2-0-1.istt-core02.bx.telstraglobal.net [202.84.249.162]
12 10 0 172.73 177.91 174.13 i-0-0-1-0.istt03.bi.telstraglobal.net [202.84.243.94]
13 10 10 148.89 152.81 150.74 unknown.telstraglobal.net [202.127.73.118]
14 10 0 150.40 159.57 152.87 sg2-n5596-fe-1-vl231.fe.core.pw [92.223.116.163]
15 9 0 148.87 153.39 151.77 login.worldoftanks.asia [92.223.16.66]
Is this actually a fault? ISP's do not always take the most direct path with routing and can change due to cost and many other reasons
You can't expect a call centre staff member to able to treat this as a fault as the packets are still going from A to Z and back
Snapdegrees, Central Otago
Tracing route to sg2-sl-a66.fe.core.pw [92.223.16.66]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 18 ms 17 ms 17 ms 194.67.69.111.dynamic.snap.net.nz [111.69.67.194]
3 * * * Request timed out.
4 62 ms 62 ms 61 ms 4.56.69.111.static.snap.net.nz [111.69.56.4]
5 62 ms 61 ms 61 ms 5.56.69.111.static.snap.net.nz [111.69.56.5]
6 62 ms 61 ms 61 ms ten-0-1-1-5.cor01.syd04.nsw.vocus.net.au [114.31.192.54]
7 63 ms 63 ms 63 ms bundle-101.bdr01.syd03.nsw.vocus.net.au [114.31.192.87]
8 62 ms 62 ms 61 ms 220.101.73.81
9 * * * Request timed out.
10 64 ms 63 ms 63 ms 59.154.142.134
11 87 ms 90 ms 81 ms bundle-ether32.chw-edge901.sydney.telstra.net [139.130.40.49]
12 101 ms 86 ms 83 ms bundle-ether13.chw-core10.sydney.telstra.net [203.50.11.98]
13 78 ms 82 ms 84 ms bundle-ether8.exi-core10.melbourne.telstra.net [203.50.11.125]
14 90 ms 92 ms 93 ms bundle-ether5.way-core4.adelaide.telstra.net [203.50.11.92]
15 120 ms 137 ms 129 ms bundle-ether5.pie-core1.perth.telstra.net [203.50.11.17]
16 135 ms 131 ms 135 ms gigabitethernet0-7-0-0.pthp-core01.perth.net.reach.com [203.50.13.246]
17 174 ms 173 ms 179 ms i-0-1-3-0.sgpl-core01.bx.telstraglobal.net [202.84.143.181]
18 195 ms 189 ms 194 ms unknown.telstraglobal.net [202.84.224.194]
19 192 ms 204 ms 203 ms i-0-0-2-2.istt03.bi.telstraglobal.net [202.84.219.182]
20 163 ms 161 ms 160 ms unknown.telstraglobal.net [202.127.73.118]
21 170 ms 162 ms 159 ms sg2-n5596-fe-1-vl231.fe.core.pw [92.223.116.163]
22 165 ms 162 ms 161 ms sg2-sl-a66.fe.core.pw [92.223.16.66]
Trace complete.
C:\Users\Mexican>
thecatsgoolies:
Is this actually a fault? ISP's do not always take the most direct path with routing and can change due to cost and many other reasons
You can't expect a call centre staff member to able to treat this as a fault as the packets are still going from A to Z and back
As I have said previously the only issues I have had was when the cable was cut, otherwise peering has always been good.
I don't expect them to treat it as a fault but as a network issue as the packet loss I am currently experiencing is horrendous.
If their upstream provider has changed routing they can let me know so I can make arrangements.
Regards
Mark has unrealistic expectations on how the internet works and what to expect from an ISP's helpdesk.
Maybe you should have mentioned the pack loss in the first post
Linux
The ping isn't as high as in the past when the Perth/Singapore cable was out so my guess is there is some asymmetric routing happening somewhere. I would just give it time and it will sort itself out.
I'm seeing the same slightly higher ping on BigPipe and Inspire, both use Global Gateway.
Play heavy tanks or (forgive me) arty if it's a huge problem for you :)
So it works fine for years and today it goes wrong - so my expectations in finding out what has occurred from my ISP is unrealistic?
So I suck it up, accept the packet loss and carry on as normal? Would you?
I also asked the helpdesk to escalate me to a higher tier which they did, but so far I have had no response from them.
If WoT cared about their users in Australasia, they'd peer in Sydney, not Singapore... In my personal opinion, this is not really an ISP problem.
Even if ISPs choose good routes to Singapore, the return route might be rubbish, they have literally no control over that.
Mark that is simply the internet working as designed.
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
I'm pretty sure that Telstra Global route to Singapore is by special arrangement (rather than being some random shared transit path through the Internet). It is offered through Equinix Singapore and is purchased by multiple gaming and application service providers. So tell Wargaming they are not getting what they paying for.
|
![]() ![]() ![]() ![]() |