Anyone on 1 gbps Singtel Fibre notice its laggy and unstable?

anarchy89

Junior Member
Joined
Nov 13, 2013
Messages
21
Reaction score
0
Anyone on 1 gbps Singtel Fibre notice its laggy and unstable? (traceroute for proof)

Since last week, ive noticed that singtel 1gbps fibre has been lagging. i think that when they came up with the 1+1 gbps fibre plan they started re-routing the 1gbps traffic to hongkong instead of singapore.

I dont know if anyone else is having this issue or its just me.

I traced my connection to a singaporean server (13.76.159.75), it should connect in less than 10 but its connecting me to hongkong first and then back to the server which is going over 20 pings.

Is anyone else on singtel 1gbps having this issue?

i want to post an image of the trace but i cant as this is my first post.

Here is the text output of my traceroute. i have removed my IP address.

Tracing route to 13.76.159.75 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.x
2 1 ms 1 ms 1 ms bbxxx-xx-xxx-xxx.singnet.com.sg [xxx.xx.xxx.xxx]
3 4 ms 1 ms 1 ms 202.166.123.130
4 1 ms 1 ms 1 ms 202.166.123.129
5 1 ms 1 ms 1 ms ae8-0.qt-cr03.singnet.com.sg [202.166.121.101]
6 2 ms 1 ms 1 ms ae12-0.qt-er05.singnet.com.sg [202.166.120.221]
7 1 ms 1 ms 1 ms 202.166.126.114
8 10 ms 13 ms 2 ms ip-202-147-32-136.asianetcom.net [202.147.32.136]
9 5 ms 3 ms 3 ms be3.wr2.sin0.10026.telstraglobal.net [61.14.157.164]
10 4 ms 2 ms 2 ms xe0-2-0.gw1.sin2.pacnet.net [202.147.52.66]
11 4 ms 3 ms 3 ms po11-0-0.gw5.sin1.10026.telstraglobal.net [202.147.48.101]
12 4 ms 6 ms 6 ms i-92.sgpl-core02.telstraglobal.net [202.84.224.193]
13 6 ms 5 ms 6 ms i-15150.sgcn-core01.telstraglobal.net [202.84.140.165]
14 36 ms 35 ms 35 ms i-15251.hkth-core02.telstraglobal.net [202.84.141.110]
15 32 ms 32 ms 32 ms i-99.hkth12.telstraglobal.net [202.84.153.150]
16 37 ms 37 ms 36 ms unknown.telstraglobal.net [202.127.78.62]
17 33 ms 33 ms 34 ms ae0-0.hkg-96cbe-1b.ntwk.msn.net [104.44.226.173]
18 35 ms 35 ms 35 ms ae31-0.sg1-96cbe-1b.ntwk.msn.net [104.44.239.214]
19 40 ms 36 ms 37 ms ae21-0.sg1-96cbe-1a.ntwk.msn.net [104.44.239.195]
20 35 ms 35 ms 47 ms ae23-0.icr01.sg2.ntwk.msn.net [104.44.239.57]
21 * * * Request timed out.
22 * * * Request timed out.

as you can see, right before it times out (reaches the firewalled server), it has gone to hong kong before connecting back to a singaporean server.

i have run this trace on a myrepublic connection and a starhub connection (both less than 500mbps by the way) both connect straight to the singapore server in less than 6-10 hops before timing out.

i have yet to test it on another 1gbps singtel fibre connection.
 
Last edited:

renfred89

Arch-Supremacy Member
Joined
Nov 11, 2007
Messages
17,520
Reaction score
17
Since last week, ive noticed that singtel 1gbps fibre has been lagging. i think that when they came up with the 1+1 gbps fibre plan they started re-routing the 1gbps traffic to hongkong instead of singapore.

I dont know if anyone else is having this issue or its just me.

I traced my connection to a singaporean server, it should connect in less than 10 but its connecting me to hongkong first and then back to the server which is going over 20 pings.

Is anyone else on singtel 1gbps having this issue?

i want to post an image of the trace but i cant as this is my first post.

What’s the IP address you’re tracing to?

Maybe we can help you and you compare?
 

anarchy89

Junior Member
Joined
Nov 13, 2013
Messages
21
Reaction score
0
trace to 13.76.159.75

i also edited my original post to include the ip.

thanks.
 
Last edited:

wolnavi

Senior Member
Joined
May 5, 2013
Messages
697
Reaction score
1
singtel 1gbps at 10kkj
tried 5 times cos idk is it i using wifi or busy traffic or singtel side issue... (high ping)
1st try
tracert 13.76.159.75

Tracing route to 13.76.159.75 over a maximum of 30 hops

1 1 ms 1 ms 1 ms Singtel-ACPlus [192.168.1.x]
2 4 ms 4 ms 5 ms bbx-x-x-x.singnet.com.sg [x.x.x.x]
3 250 ms 3 ms 7 ms 202.166.123.134
4 2 ms 2 ms 2 ms 202.166.123.133
5 1435 ms 2 ms 2 ms ae8-0.tp-cr03.singnet.com.sg [202.166.122.50]
6 86 ms 2 ms 5 ms ae4-0.tp-er03.singnet.com.sg [202.166.123.70]
7 1716 ms 2 ms 3 ms 202.166.124.190
8 3 ms 3 ms 3 ms 165.21.12.22
9 4 ms 11 ms 4 ms ip-202-147-32-136.asianetcom.net [202.147.32.136
]
10 275 ms 6 ms 7 ms be3.wr1.sin0.10026.telstraglobal.net [61.14.157.
166]
11 1413 ms 5 ms 4 ms xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
12 2437 ms 5 ms 6 ms po11-0-0.gw5.sin1.10026.telstraglobal.net [202.1
47.48.101]
13 1415 ms 6 ms 5 ms i-92.sgpl-core02.telstraglobal.net [202.84.224.1
93]
14 37 ms 36 ms 37 ms i-25250.hkth-core02.telstraglobal.net [202.84.14
0.94]
15 318 ms 35 ms 36 ms i-92.hkth12.telstraglobal.net [202.84.153.38]
16 35 ms 35 ms 34 ms unknown.telstraglobal.net [202.127.78.62]
17 35 ms 35 ms 35 ms ae0-0.hkg-96cbe-1b.ntwk.msn.net [104.44.226.173]

18 172 ms 34 ms 35 ms ae26-0.icr02.hkg31.ntwk.msn.net [104.44.236.209]

19 1473 ms 35 ms 35 ms ae25-0.hkb-96cbe-1b.ntwk.msn.net [104.44.236.206
]
20 38 ms 36 ms 35 ms ae36-0.sge-96cbe-1b.ntwk.msn.net [104.44.224.255
]
21 35 ms 45 ms 35 ms ae38-0.icr02.sg2.ntwk.msn.net [104.44.236.146]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

2
tracert 13.76.159.75

Tracing route to 13.76.159.75 over a maximum of 30 hops

1 1 ms 1 ms 1 ms Singtel-ACPlus [192.168.1.x]
2 2064 ms 4 ms 4 ms bbx-x-x-x.singnet.com.sg [x.x.x.x]
3 2506 ms 3 ms 3 ms 202.166.123.134
4 * * * Request timed out.
5 * * 361 ms ae8-0.tp-cr03.singnet.com.sg [202.166.122.50]
6 485 ms 2 ms 3 ms ae4-0.tp-er03.singnet.com.sg [202.166.123.70]
7 190 ms 2 ms 2 ms 202.166.124.190
8 3 ms 70 ms 3 ms 165.21.12.22
9 4 ms 3 ms 4 ms ip-202-147-32-136.asianetcom.net [202.147.32.136
]
10 7 ms 7 ms 7 ms be3.wr1.sin0.10026.telstraglobal.net [61.14.157.
166]
11 5 ms 5 ms 4 ms xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
12 5 ms 5 ms 5 ms po11-0-0.gw5.sin1.10026.telstraglobal.net [202.1
47.48.101]
13 6 ms 5 ms 5 ms i-92.sgpl-core02.telstraglobal.net [202.84.224.1
93]
14 36 ms 38 ms 37 ms i-25250.hkth-core02.telstraglobal.net [202.84.14
0.94]
15 481 ms 35 ms 35 ms i-92.hkth12.telstraglobal.net [202.84.153.38]
16 2591 ms 35 ms 35 ms unknown.telstraglobal.net [202.127.78.62]
17 1889 ms 35 ms 35 ms ae0-0.hkg-96cbe-1b.ntwk.msn.net [104.44.226.173]

18 1031 ms 39 ms 37 ms ae26-0.icr02.hkg31.ntwk.msn.net [104.44.236.209]

19 177 ms 35 ms 35 ms ae25-0.hkb-96cbe-1b.ntwk.msn.net [104.44.236.206
]
20 494 ms 35 ms 35 ms ae36-0.sge-96cbe-1b.ntwk.msn.net [104.44.224.255
]
21 * * 1507 ms ae38-0.icr02.sg2.ntwk.msn.net [104.44.236.146]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

3
tracert 13.76.159.75

Tracing route to 13.76.159.75 over a maximum of 30 hops

1 2 ms 1 ms 1 ms Singtel-ACPlus [192.168.1.x]
2 5 ms 4 ms 3 ms bbx-x-x-x.singnet.com.sg [x.x.x.x]
3 5 ms 3 ms 3 ms 202.166.123.134
4 729 ms 2 ms 2 ms 202.166.123.133
5 40 ms 7 ms 3 ms ae8-0.tp-cr03.singnet.com.sg [202.166.122.50]
6 3 ms 3 ms 2 ms ae4-0.tp-er03.singnet.com.sg [202.166.123.70]
7 108 ms 3 ms 3 ms 202.166.124.190
8 3 ms 2 ms 3 ms 165.21.12.22
9 4 ms 4 ms 4 ms ip-202-147-32-136.asianetcom.net [202.147.32.136
]
10 7 ms 7 ms 7 ms be3.wr1.sin0.10026.telstraglobal.net [61.14.157.
166]
11 5 ms 5 ms 5 ms xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
12 6 ms 5 ms 5 ms po11-0-0.gw5.sin1.10026.telstraglobal.net [202.1
47.48.101]
13 6 ms 5 ms 6 ms i-92.sgpl-core02.telstraglobal.net [202.84.224.1
93]
14 37 ms 38 ms 36 ms i-25250.hkth-core02.telstraglobal.net [202.84.14
0.94]
15 35 ms 34 ms 34 ms i-92.hkth12.telstraglobal.net [202.84.153.38]
16 76 ms 34 ms 35 ms unknown.telstraglobal.net [202.127.78.62]
17 1017 ms 40 ms 36 ms ae26-0.icr01.hkg20.ntwk.msn.net [104.44.236.217]

18 40 ms 44 ms 47 ms ae22-0.hkb-96cbe-1a.ntwk.msn.net [104.44.236.214
]
19 35 ms 35 ms 35 ms ae0-0.hkb-96cbe-1b.ntwk.msn.net [104.44.226.55]

20 36 ms 37 ms 36 ms ae36-0.sge-96cbe-1b.ntwk.msn.net [104.44.224.255
]
21 35 ms 40 ms 41 ms ae38-0.icr02.sg2.ntwk.msn.net [104.44.236.146]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

4
tracert 13.76.159.75

Tracing route to 13.76.159.75 over a maximum of 30 hops

1 1 ms 1 ms 1 ms Singtel-ACPlus [192.168.1.x]
2 4 ms 4 ms 3 ms bbx-x-x-x.singnet.com.sg [x.x.x.x]
3 13 ms 8 ms 15 ms 202.166.123.134
4 2 ms 3 ms 2 ms 202.166.123.133
5 3 ms 3 ms 3 ms ae8-0.tp-cr03.singnet.com.sg [202.166.122.50]
6 3 ms 9 ms 4 ms ae4-0.tp-er03.singnet.com.sg [202.166.123.70]
7 3 ms 3 ms 3 ms 202.166.124.190
8 280 ms 3 ms 3 ms 165.21.12.22
9 4 ms 4 ms 4 ms ip-202-147-32-136.asianetcom.net [202.147.32.136
]
10 8 ms 7 ms 7 ms be3.wr1.sin0.10026.telstraglobal.net [61.14.157.
166]
11 5 ms 4 ms 4 ms xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
12 5 ms 5 ms 5 ms po11-0-0.gw5.sin1.10026.telstraglobal.net [202.1
47.48.101]
13 5 ms 6 ms 9 ms i-92.sgpl-core02.telstraglobal.net [202.84.224.1
93]
14 38 ms 38 ms 36 ms 202.84.140.94
15 36 ms 34 ms 34 ms i-92.hkth12.telstraglobal.net [202.84.153.38]
16 35 ms 35 ms 35 ms unknown.telstraglobal.net [202.127.78.62]
17 35 ms 36 ms 40 ms ae26-0.icr01.hkg20.ntwk.msn.net [104.44.236.217]

18 40 ms 39 ms 39 ms ae22-0.hkb-96cbe-1a.ntwk.msn.net [104.44.236.214
]
19 35 ms 35 ms 35 ms ae0-0.hkb-96cbe-1b.ntwk.msn.net [104.44.226.55]

20 37 ms 36 ms 36 ms ae36-0.sge-96cbe-1b.ntwk.msn.net [104.44.224.255
]
21 36 ms 35 ms 37 ms ae38-0.icr02.sg2.ntwk.msn.net [104.44.236.146]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

5
tracert 13.76.159.75

Tracing route to 13.76.159.75 over a maximum of 30 hops

1 1 ms 1 ms 1 ms Singtel-ACPlus [192.168.1.x]
2 4 ms 4 ms 5 ms bbx-x-x-x.singnet.com.sg [x.x.x.x]
3 5 ms 3 ms 3 ms 202.166.123.134
4 5 ms 2 ms 3 ms 202.166.123.133
5 3 ms 2 ms 2 ms ae8-0.tp-cr03.singnet.com.sg [202.166.122.50]
6 2 ms 4 ms 2 ms ae4-0.tp-er03.singnet.com.sg [202.166.123.70]
7 3 ms 3 ms 3 ms 202.166.124.190
8 3 ms 3 ms 4 ms 165.21.12.22
9 4 ms 4 ms 4 ms ip-202-147-32-136.asianetcom.net [202.147.32.136
]
10 6 ms 7 ms 7 ms be3.wr1.sin0.10026.telstraglobal.net [61.14.157.
166]
11 5 ms 5 ms 6 ms xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
12 5 ms 5 ms 5 ms po11-0-0.gw5.sin1.10026.telstraglobal.net [202.1
47.48.101]
13 7 ms 5 ms 5 ms i-92.sgpl-core02.telstraglobal.net [202.84.224.1
93]
14 38 ms 36 ms 38 ms i-25250.hkth-core02.telstraglobal.net [202.84.14
0.94]
15 35 ms 34 ms 35 ms i-92.hkth12.telstraglobal.net [202.84.153.38]
16 35 ms 35 ms 35 ms unknown.telstraglobal.net [202.127.78.62]
17 39 ms 39 ms 39 ms ae26-0.icr01.hkg20.ntwk.msn.net [104.44.236.217]

18 41 ms 39 ms 40 ms ae22-0.hkb-96cbe-1a.ntwk.msn.net [104.44.236.214
]
19 35 ms 36 ms 35 ms ae0-0.hkb-96cbe-1b.ntwk.msn.net [104.44.226.55]

20 35 ms 36 ms 37 ms ae36-0.sge-96cbe-1b.ntwk.msn.net [104.44.224.255
]
21 35 ms 35 ms 35 ms ae38-0.icr02.sg2.ntwk.msn.net [104.44.236.146]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
Last edited:

Groudon

Member
Joined
May 4, 2013
Messages
305
Reaction score
51
That was 3 years ago so what is today?

Still valid to this day. Singtel, being one of the large ISPs, still refuses to peer with content providers with local presence (unless maybe you're big enough that you cause issues when people's stuff don't work properly i.e. to say CloudFlare), unless you pay them for direct access.

Therefore, the way Singtel routes allows most content providers direct access into their network, but Singtel's outbound routing will never use a local route and will always prefer a HK/LAX route towards your network.
 

cloudangel

Member
Joined
Feb 25, 2008
Messages
363
Reaction score
26
Have been experiencing it since last week or the week before... and i thought it was because i switched over to Mesh

Ping shot up to few hundreds
 

anarchy89

Junior Member
Joined
Nov 13, 2013
Messages
21
Reaction score
0
yeah man im getting pretty annoyed, they sent the technician over to my house to check the modem and router and when i called them they were like lets send another, i kept telling them theres no point theres nothing wrong with the hardware and i wanted to speak to an engineer or something, they just keep brushing me off.

i dont care if it routed me thru somewhere else if it was connecting to an overseas server, but what the hell this server is located in singapore.

im thinking of contacting imda but i doubt they will do anything unless they get a lot of complaints
 
Last edited:

miloaisdino

Senior Member
Joined
Mar 25, 2016
Messages
955
Reaction score
53
Still valid to this day. Singtel, being one of the large ISPs, still refuses to peer with content providers with local presence (unless maybe you're big enough that you cause issues when people's stuff don't work properly i.e. to say CloudFlare), unless you pay them for direct access.

Therefore, the way Singtel routes allows most content providers direct access into their network, but Singtel's outbound routing will never use a local route and will always prefer a HK/LAX route towards your network.
Yes. But there's a workaround. If u notice carefully, connection to digitalocean will be either through telstra global or starhub internet exchange and then equinix or sgix. U wont be able to see the whole route on traceroute due to blackholing. But the latency is <10ms, from there if u rent a cheap $5/mth vps u can make your own tunnel to anywhere u want from equinix sg exchange. :)

But of course the best way is just to use m1. No ******** peering. But ppl like me have singtel tv :( ... what to do? :x
 
Last edited:

Henry Ng

Arch-Supremacy Member
Joined
Aug 9, 2011
Messages
14,009
Reaction score
219
yeah man im getting pretty annoyed, they sent the technician over to my house to check the modem and router and when i called them they were like lets send another, i kept telling them theres no point theres nothing wrong with the hardware and i wanted to speak to an engineer or something, they just keep brushing me off.

i dont care if it routed me thru somewhere else if it was connecting to an overseas server, but what the hell this server is located in singapore.

im thinking of contacting imda but i doubt they will do anything unless they get a lot of complaints
You are not the only user so you can not be the only one having the issue.
Email IMDA to complaint.
 

squarepipe

Senior Member
Joined
Jun 30, 2018
Messages
1,218
Reaction score
1
Aiya the tech can only check simple stuff like see if cables connected etc. Asking them about routing is out of their League. Singtel also won't entertain you because if they do they will have to fix their underlying problem which is their **** routing
 

dryteletubby

Senior Member
Joined
Aug 25, 2017
Messages
2,303
Reaction score
1
Yes. But there's a workaround. If u notice carefully, connection to digitalocean will be either through telstra global or starhub internet exchange and then equinix or sgix. U wont be able to see the whole route on traceroute due to blackholing. But the latency is <10ms, from there if u rent a cheap $5/mth vps u can make your own tunnel to anywhere u want from equinix sg exchange. :)

But of course the best way is just to use m1. No ******** peering. But ppl like me have singtel tv :( ... what to do? :x


Cut the cord & switch to streaming services or self hosted ones via PleX ;)
 

Groudon

Member
Joined
May 4, 2013
Messages
305
Reaction score
51
Yes. But there's a workaround. If u notice carefully, connection to digitalocean will be either through telstra global or starhub internet exchange and then equinix or sgix. U wont be able to see the whole route on traceroute due to blackholing. But the latency is <10ms, from there if u rent a cheap $5/mth vps u can make your own tunnel to anywhere u want from equinix sg exchange. :)

But of course the best way is just to use m1. No ******** peering. But ppl like me have singtel tv :( ... what to do? :x

Yep, certain networks Singtel decide not to practice their policy (i.e. DO, SoftLayer) at the moment [in the past DO and SL used to suffer this]. But for the other networks that suffer this issue it's not a practical solution for everyone, unfortunately.
 

miloaisdino

Senior Member
Joined
Mar 25, 2016
Messages
955
Reaction score
53
Yep, certain networks Singtel decide not to practice their policy (i.e. DO, SoftLayer) at the moment [in the past DO and SL used to suffer this]. But for the other networks that suffer this issue it's not a practical solution for everyone, unfortunately.

It is more obvious with their routes to china unicom. To first landing site (somewhere near nanjing) for china unicom, ping can be between 50ms (yes ikr) to 200ms. Connection to china telecom and others is routed randomly, with latency ranging from 300-800ms.

And even for their gaming plan, their faq states
8. Is there bit throttling on the 1+1Gbps Fibre Pro Gamer Bundle?
The 1+1Gbps Fibre Pro Gamer Bundle is on a managed network, hence there is bit
throttling. This means that the fibre plan comes with Internet traffic management of Bit
Torrent or peer-to-peer (P2P) file-sharing activities. This is necessary to ensure that there
is ample network bandwidth for all other Internet activities.

"Uncapped International Bandwidth" == Assured min. 25Mbps during heavy surfing times


Contention ratio ~~ 1:40? Thats bad
Go to hell singtel.
 
Last edited:

anarchy89

Junior Member
Joined
Nov 13, 2013
Messages
21
Reaction score
0
well i emailed singtel complaints department the traceroute with a few different connections, if they dont do anything first ill email imda
 

anarchy89

Junior Member
Joined
Nov 13, 2013
Messages
21
Reaction score
0
I just ran the traceroute again on 13.76.159.75 & another new connection 13.67.39.144. both located in singapore. the lag has gotten worse, im getting a constant ping of 120 ms in game and check out the bounces now.

Tracing route to 13.67.39.144 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.254
2 3 ms 3 ms 2 ms bbxxx-xx-xxx-xxx.singnet.com.sg [xxx.xx.xxx.xxx]
3 3 ms 2 ms 1 ms 202.166.123.130
4 1 ms 1 ms 1 ms 202.166.123.129
5 2 ms 1 ms 1 ms ae8-0.qt-cr03.singnet.com.sg [202.166.121.101]
6 6 ms 3 ms 1 ms ae12-0.qt-er05.singnet.com.sg [202.166.120.221]
7 1 ms 1 ms 1 ms 202.166.126.114
8 86 ms 87 ms 90 ms ip-202-147-32-136.asianetcom.net [202.147.32.136]
9 98 ms 95 ms 94 ms be3.wr1.sin0.10026.telstraglobal.net [61.14.157.166]
10 91 ms 92 ms 94 ms xe-0-1-1.gw1.sin2.pacnet.net [202.147.52.64]
11 96 ms 94 ms 94 ms po11-0-0.gw5.sin1.10026.telstraglobal.net [202.147.48.101]
12 94 ms 95 ms 95 ms i-92.sgpl-core02.telstraglobal.net [202.84.224.193]
13 124 ms 122 ms 124 ms i-25250.hkth-core02.telstraglobal.net [202.84.140.94]
14 127 ms 127 ms 125 ms i-92.hkth12.telstraglobal.net [202.84.153.38]
15 129 ms 129 ms 127 ms unknown.telstraglobal.net [202.127.78.62]
16 124 ms 123 ms 125 ms ae0-0.hkg-96cbe-1b.ntwk.msn.net [104.44.226.173]
17 126 ms 132 ms 152 ms ae31-0.sg1-96cbe-1b.ntwk.msn.net [104.44.239.214]
18 125 ms 127 ms 125 ms ae21-0.sg1-96cbe-1a.ntwk.msn.net [104.44.239.195]
19 140 ms 134 ms 128 ms ae23-0.icr01.sg2.ntwk.msn.net [104.44.239.57]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ. Forum members and moderators are responsible for their own posts.

Please refer to our Community Guidelines and Standards, Terms of Service and Member T&Cs for more information.
Top