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
![]() ![]() ![]() |
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.
![]() ![]() ![]() |