QUOTE(yeapch01 @ Nov 2 2016, 09:46 PM)
Dear all
To justify the unusual routing problem , we are pledging those who face problem , kindly do test on other isp routing pattern also on similar ping and tracert.
Definitely we are helping , we need more supporting fact to support
Thanks
Is this the kind of information you need?To justify the unusual routing problem , we are pledging those who face problem , kindly do test on other isp routing pattern also on similar ping and tracert.
Definitely we are helping , we need more supporting fact to support
Thanks
With Time:
CODE
Tracing route to 103.4.115.248 over a maximum of 30 hops
1 2 ms 2 ms 1 ms ag-01-glsfb.ni.time.net.my [223.28.0.216]
2 2 ms 1 ms 1 ms ae2-er-01-glsfb.ni.time.net.my [223.28.26.41]
3 15 ms 14 ms 14 ms 223.28.2.1
4 8 ms 7 ms 8 ms Bundle-Ether1-br-01-mciwg.ni.time.net.my [223.28.26.82]
5 16 ms 8 ms 15 ms he.sgix.sg [103.16.102.81]
6 40 ms 40 ms 46 ms 10ge1-16.core1.hkg1.he.net [184.105.223.189]
7 201 ms 199 ms 201 ms 100ge8-2.core1.lax2.he.net [184.105.64.125]
8 209 ms 202 ms 202 ms 100ge8-2.core1.pao1.he.net [184.105.81.237]
9 275 ms 236 ms 217 ms 10ge4-1.core1.sjc1.he.net [72.52.92.114]
10 227 ms 226 ms 227 ms vocus.gigabitethernet2-13.core1.sjc1.he.net [64.71.184.46]
11 228 ms 228 ms 228 ms bundle-153.cor02.sjc01.ca.vocus.net [49.255.255.24]
12 224 ms 223 ms 224 ms ten-0-6-0-1.cor01.syd04.nsw.vocus.net.au [114.31.199.49]
13 226 ms 226 ms 226 ms ten-0-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.72.93]
14 227 ms 226 ms 227 ms as17819.cust.bdr03.syd04.nsw.VOCUS.net.au [175.45.73.194]
15 227 ms 226 ms 226 ms 27.111.251.106
16 223 ms 223 ms 223 ms 103.4.115.248
Trace complete.
1 2 ms 2 ms 1 ms ag-01-glsfb.ni.time.net.my [223.28.0.216]
2 2 ms 1 ms 1 ms ae2-er-01-glsfb.ni.time.net.my [223.28.26.41]
3 15 ms 14 ms 14 ms 223.28.2.1
4 8 ms 7 ms 8 ms Bundle-Ether1-br-01-mciwg.ni.time.net.my [223.28.26.82]
5 16 ms 8 ms 15 ms he.sgix.sg [103.16.102.81]
6 40 ms 40 ms 46 ms 10ge1-16.core1.hkg1.he.net [184.105.223.189]
7 201 ms 199 ms 201 ms 100ge8-2.core1.lax2.he.net [184.105.64.125]
8 209 ms 202 ms 202 ms 100ge8-2.core1.pao1.he.net [184.105.81.237]
9 275 ms 236 ms 217 ms 10ge4-1.core1.sjc1.he.net [72.52.92.114]
10 227 ms 226 ms 227 ms vocus.gigabitethernet2-13.core1.sjc1.he.net [64.71.184.46]
11 228 ms 228 ms 228 ms bundle-153.cor02.sjc01.ca.vocus.net [49.255.255.24]
12 224 ms 223 ms 224 ms ten-0-6-0-1.cor01.syd04.nsw.vocus.net.au [114.31.199.49]
13 226 ms 226 ms 226 ms ten-0-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.72.93]
14 227 ms 226 ms 227 ms as17819.cust.bdr03.syd04.nsw.VOCUS.net.au [175.45.73.194]
15 227 ms 226 ms 226 ms 27.111.251.106
16 223 ms 223 ms 223 ms 103.4.115.248
Trace complete.
With Digi mobile:
CODE
traceroute to 103.4.115.248 (103.4.115.248), 30 hops max
Hop 1: *
Hop 2: *
Hop 3: *
Hop 4: *
Hop 5: *
Hop 6: *
Hop 7: *
Hop 8: From 4826.sgw.equinix.com (27.111.228.74), 85 ms
Hop 9: From ge-0-1-0-15.cor02.per02.wa.VOCUS.net.au (114.31.206.98), 221 ms
Hop 10: From bundle-102.cor03.syd03.nsw.vocus.net.au (114.31.206.128), 221 ms
Hop 11: From ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au (175.45.72.73), 221 ms
Hop 12: From as17819.cust.bdr03.syd04.nsw.VOCUS.net.au (175.45.73.194), 220 ms
Hop 1: *
Hop 2: *
Hop 3: *
Hop 4: *
Hop 5: *
Hop 6: *
Hop 7: *
Hop 8: From 4826.sgw.equinix.com (27.111.228.74), 85 ms
Hop 9: From ge-0-1-0-15.cor02.per02.wa.VOCUS.net.au (114.31.206.98), 221 ms
Hop 10: From bundle-102.cor03.syd03.nsw.vocus.net.au (114.31.206.128), 221 ms
Hop 11: From ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au (175.45.72.73), 221 ms
Hop 12: From as17819.cust.bdr03.syd04.nsw.VOCUS.net.au (175.45.73.194), 220 ms
Now, Digi is just as slow response-wise, but it's because digi's mobile internet is rubbish and can't even get to a SG server without trouble. That said, it takes a direct route to Australia, via singapore, as TIME should!
Now, if I VPN to singapore and perform the same traceroute using TIME:
CODE
Tracing route to 103.4.115.248 over a maximum of 30 hops
1 8 ms 8 ms 8 ms 10.51.10.1
2 9 ms 8 ms 8 ms 43.7c.5177.ip4.static.sl-reverse.com [119.81.124.67]
3 9 ms 8 ms 8 ms 9a.76.85ae.ip4.static.sl-reverse.com [174.133.118.154]
4 9 ms 9 ms 9 ms ae9.bbr01.eq01.sng02.networklayer.com [50.97.18.198]
5 * * * Request timed out.
6 103 ms 102 ms 103 ms ge-0-1-0-15.cor02.per02.wa.VOCUS.net.au [114.31.206.98]
7 106 ms 106 ms 106 ms bundle-102.cor03.syd03.nsw.vocus.net.au [114.31.206.128]
8 105 ms 105 ms 105 ms ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.72.73]
9 106 ms 107 ms 106 ms as17819.cust.bdr03.syd04.nsw.VOCUS.net.au [175.45.73.194]
10 105 ms 105 ms 105 ms 27.111.251.106
11 106 ms 105 ms 105 ms 103.4.115.248
Trace complete.
1 8 ms 8 ms 8 ms 10.51.10.1
2 9 ms 8 ms 8 ms 43.7c.5177.ip4.static.sl-reverse.com [119.81.124.67]
3 9 ms 8 ms 8 ms 9a.76.85ae.ip4.static.sl-reverse.com [174.133.118.154]
4 9 ms 9 ms 9 ms ae9.bbr01.eq01.sng02.networklayer.com [50.97.18.198]
5 * * * Request timed out.
6 103 ms 102 ms 103 ms ge-0-1-0-15.cor02.per02.wa.VOCUS.net.au [114.31.206.98]
7 106 ms 106 ms 106 ms bundle-102.cor03.syd03.nsw.vocus.net.au [114.31.206.128]
8 105 ms 105 ms 105 ms ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.72.73]
9 106 ms 107 ms 106 ms as17819.cust.bdr03.syd04.nsw.VOCUS.net.au [175.45.73.194]
10 105 ms 105 ms 105 ms 27.111.251.106
11 106 ms 105 ms 105 ms 103.4.115.248
Trace complete.
Again, it takes the direct route that TIME already should be taking.
There's something very wrong going on with how TIME is handling its routing to Australia right now, especially when I can, using a simple, non-gaming / non-performance VPN, literally halve the ping and shorted the hops required to get to the same IP.
This post has been edited by Aelzen: Nov 8 2016, 07:18 PM
Nov 8 2016, 07:17 PM

Quote
0.0220sec
0.68
6 queries
GZIP Disabled