Code:
1 * 5 ms 1 ms 10.0.0.1
2 13 ms 12 ms 10 ms 96.120.28.53
3 10 ms 10 ms 24 ms te-0-7-0-7-sur03.chicago301.il.chicago.comcast.net [68.85.180.37]
4 15 ms 12 ms 11 ms te-1-8-0-4-ar01.elmhurst.il.chicago.comcast.net [68.87.230.197]
5 * 15 ms 11 ms 4.68.70.45
6 72 ms 62 ms 62 ms ae-4-90.edge2.LosAngeles9.Level3.net [4.69.144.207]
7 69 ms 62 ms 60 ms ae-4-90.edge2.LosAngeles9.Level3.net [4.69.144.207]
8 64 ms 67 ms 60 ms ASIA-NETCOM.edge2.LosAngeles9.Level3.net [4.53.230.10]
9 232 ms * 228 ms te0-1-0-0.wr2.sin0.10026.telstraglobal.net [61.14.157.61]
10 226 ms 230 ms 227 ms xe0-2-0.gw1.sin2.pacnet.net [202.147.52.66]
11 238 ms 237 ms 237 ms LSW-0011.asianetcom.net [61.14.147.69]
12 235 ms 236 ms 231 ms et50.ce02.sin-11.leaseweb.net [103.254.152.203]
13 244 ms 245 ms 242 ms mirror.sin11.sg.leaseweb.net [103.254.153.18]
Not sure if this is useful at all because I live far from Asia but here's my pings.
(Apr 07 2016, 06:16 PM)Raga Wrote: [ -> ]Code:
Tracing route to mirror.sin11.sg.leaseweb.net [103.254.153.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1]
2 19 ms 24 ms 19 ms 172.18.216.3
3 20 ms 19 ms 19 ms 172.18.73.69
4 19 ms 19 ms 19 ms bundle-ether4.pie-edge902.perth.telstra.net [203.50.112.52]
5 22 ms 19 ms 19 ms bundle-ether7.pie-core1.perth.telstra.net [203.50.6.188]
6 18 ms 18 ms 20 ms tengige0-0-1-0.pthp-core01.perth.net.reach.com [203.50.13.250]
7 67 ms 67 ms 67 ms i-0-0-1-0.skdi-core01.bx.telstraglobal.net [202.84.143.2]
8 182 ms 182 ms 181 ms 202.84.244.46
9 182 ms 182 ms 181 ms pacnet-peer.istt03.pr.telstraglobal.net [202.126.128.189]
10 182 ms 183 ms 183 ms xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
11 187 ms 187 ms 187 ms LSW-0011.asianetcom.net [61.14.147.69]
12 184 ms 187 ms 187 ms et50.ce01.sin-11.leaseweb.net [103.254.152.201]
13 183 ms 183 ms 183 ms mirror.sin11.sg.leaseweb.net [103.254.153.18]
Trace complete.
Mine is taking the scenic route it seems lol...
Seems Telstra is going to Hong Kong for some reason instead of Singapore directly, might be something that can be fixed later by either Leaseweb or Telstra just changing the routing a bit.
Code:
Tracing route to mirror.sin11.sg.leaseweb.net [103.254.153.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [10.1.1.1]
2 1 ms 2 ms 2 ms lns20.per1.on.ii.net [150.101.0.206]
3 8 ms 1 ms 2 ms xe-0-0-1.cr1.per1.on.ii.net [150.101.33.94]
4 52 ms 52 ms 52 ms pos1-2-0.bdr1.sin1.on.ii.net [150.101.33.68]
5 52 ms 53 ms 52 ms tengige0-1-0-3.br02.sin-10.leaseweb.net [202.79.197.71]
6 52 ms 51 ms 58 ms xe-0-1-2.cr01.sin-11.leaseweb.net [103.254.152.209]
7 52 ms 52 ms 51 ms et49.ce01.sin-11.leaseweb.net [103.254.152.211]
8 51 ms 51 ms 51 ms mirror.sin11.sg.leaseweb.net [103.254.153.18]
Trace complete.
It should be pretty close to mine since you live in Perth as well.
(Apr 11 2016, 09:43 AM)Matt Wrote: [ -> ]Seems Telstra is going to Hong Kong for some reason instead of Singapore directly, might be something that can be fixed later by either Leaseweb or Telstra just changing the routing a bit.
Code:
Tracing route to mirror.sin11.sg.leaseweb.net [103.254.153.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [10.1.1.1]
2 1 ms 2 ms 2 ms lns20.per1.on.ii.net [150.101.0.206]
3 8 ms 1 ms 2 ms xe-0-0-1.cr1.per1.on.ii.net [150.101.33.94]
4 52 ms 52 ms 52 ms pos1-2-0.bdr1.sin1.on.ii.net [150.101.33.68]
5 52 ms 53 ms 52 ms tengige0-1-0-3.br02.sin-10.leaseweb.net [202.79.197.71]
6 52 ms 51 ms 58 ms xe-0-1-2.cr01.sin-11.leaseweb.net [103.254.152.209]
7 52 ms 52 ms 51 ms et49.ce01.sin-11.leaseweb.net [103.254.152.211]
8 51 ms 51 ms 51 ms mirror.sin11.sg.leaseweb.net [103.254.153.18]
Trace complete.
It should be pretty close to mine since you live in Perth as well.
Yep. Telstra has been really bad over the few months. The latency to Singapore changes between 70ms and 200ms atleast 2 or 3 times throughout the week. That's why i'm switching back to Internode or iinet soon...
This took out 10 more IQ of mine
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\kub47>tracert 103.254.153.18
Tracing route to mirror.sin11.sg.leaseweb.net [103.254.153.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms 112.203.32.1.pldt.net [112.203.32.1]
3 2 ms 2 ms 2 ms 122.2.175.178.static.pldt.net [122.2.175.178]
4 3 ms 3 ms 3 ms 210.213.131.62.static.pldt.net [210.213.131.62]
5 2 ms 2 ms 1 ms 210.213.131.77.static.pldt.net [210.213.131.77]
6 148 ms 148 ms 148 ms ix-pos-13-0.mcore5.LAA-Los-Angeles.as6453.net [2
09.58.33.57]
7 321 ms * 321 ms 209.58.33.142
8 333 ms 332 ms 332 ms 180.87.15.25
9 324 ms 324 ms 324 ms if-ae-20-2.tcore1.SVQ-Singapore.as6453.net [180.
87.96.21]
10 312 ms 311 ms 311 ms 180.87.96.34
11 312 ms 312 ms 312 ms 103.254.152.199
12 313 ms 311 ms 312 ms et50.ce01.sin-11.leaseweb.net [103.254.152.201]
13 312 ms 312 ms 312 ms mirror.sin11.sg.leaseweb.net [103.254.153.18]
Trace complete.
C:\Users\kub47>
(Apr 08 2016, 10:14 AM)Sibrox Wrote: [ -> ]Code:
Tracing route to mirror.sin11.sg.leaseweb.net [103.254.153.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms 112.203.0.1.pldt.net [112.203.0.1]
3 * * * Request timed out.
4 3 ms 2 ms 2 ms 210.213.131.66.static.pldt.net [210.213.131.66]
5 15 ms 2 ms 1 ms 210.213.131.73.static.pldt.net [210.213.131.73]
6 250 ms 250 ms 250 ms ix-pos-13-0.mcore5.LAA-Los-Angeles.as6453.net [2
09.58.33.57]
7 422 ms 421 ms 422 ms if-xe-10-3-1-14.tcore2.LVW-Los-Angeles.as6453.ne
t [209.58.33.142]
8 422 ms 422 ms 422 ms if-ae-7-2.tcore2.SVW-Singapore.as6453.net [180.8
7.15.25]
9 * 426 ms 425 ms if-ae-20-2.tcore1.SVQ-Singapore.as6453.net [180.
87.96.21]
10 309 ms 309 ms 309 ms 180.87.96.34
11 310 ms 309 ms 309 ms 103.254.152.199
12 309 ms 309 ms 309 ms et50.ce01.sin-11.leaseweb.net [103.254.152.201]
13 309 ms 309 ms 309 ms mirror.sin11.sg.leaseweb.net [103.254.153.18]
Trace complete.
Seems like PLDT's connection to the server sucks? Or is it just your connection?
Nope, it's to them. Nakakatamad na silang tawagan dahil alam kong wala akong makukha sa kanilang malaman.