Can anyone from TIME explain howis TIME routing to softlayer data centers in SG giving 200+ ms response to Singapore which used to give relatively 10-30ms in the past.

1 3 ms 3 ms 3 ms 192.168.1.1
2 6 ms 6 ms 7 ms cgw-211-24-64-1.bbrtl.time.net.my [211.24.64.1]

3 6 ms 7 ms 6 ms xe-5-3-0-0.er-01-majjw.ni.time.net.my [223.28.2.
41]
4 19 ms 15 ms 15 ms xe-5-3-0-0.er-01-glsfb.ni.time.net.my [223.28.2.
37]
5 13 ms 15 ms 16 ms xe-0-1-0-1.cr-02-glsfb.ni.time.net.my [223.28.2.
9]
6 14 ms 13 ms 13 ms ae-0-0.br-01-mciwg.ni.time.net.my [223.28.2.122]

7 13 ms 12 ms 13 ms 124.158.226.149
8 174 ms 172 ms 172 ms xe-0-1-0-0.cr-gw-2-sin-pip.sg.globaltransit.net
[124.158.224.229]
9 173 ms 172 ms 173 ms ae-2.br-gw-1-lax-pip.us.globaltransit.net [124.1
58.224.18]
10 173 ms 173 ms 173 ms te0-2-0-18.ccr21.lax04.atlas.cogentco.com [38.10
4.210.81]
11 178 ms 178 ms 179 ms ntt.lax04.atlas.cogentco.com [154.54.10.30]
12 178 ms 179 ms 183 ms ae-2.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.2
29]
13 186 ms 191 ms 174 ms ae-7.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.1
5]
14 180 ms 178 ms 178 ms ae-19.r25.tokyjp05.jp.bb.gin.ntt.net [129.250.6.
213]
15 176 ms 175 ms 176 ms ae-2.r00.tokyjp03.jp.bb.gin.ntt.net [129.250.2.5
]
16 200 ms 193 ms 181 ms xe-0-0-0.bbr01.eq01.tok01.networklayer.com [61.2
13.145.38]
17 179 ms 176 ms 178 ms ae1.bbr01.eq01.sng02.networklayer.com [50.97.18.
165]
18 195 ms 184 ms 178 ms ae5.dar01.sr03.sng01.networklayer.com [50.97.18.
197]
19 178 ms * 176 ms po1.fcr01.sr03.sng01.networklayer.com [174.133.1
18.131]
20 182 ms 175 ms 186 ms 216.12.203.91-static.reverse.softlayer.com [216.
12.203.91]

From what it looks it's making 1 big loop from MY-> SG -> LAX -> Tokyo?

Hi, can you also pm me the options available as the default router is getting worst.

Any TIME users out there who frequently stream to Twitch TV? Noticed some severe degradation in buffering for the past 1-2 months and now even worst when it doesn't buffer and breaks when it loads even on low video quality setting.

Never had this issue when I was on Unifi for the 2 years of service I had.

1 7 ms 10 ms 9 ms 192.168.1.1
2 8 ms 10 ms 8 ms cgw-211-24-64-1.bbrtl.time.net.my [211.24.64.1]

3 44 ms 19 ms 19 ms xe-5-3-0-0.er-01-majjw.ni.time.net.my [223.28.2.
41]
4 20 ms 19 ms 19 ms xe-5-3-0-0.er-01-glsfb.ni.time.net.my [223.28.2.
37]
5 18 ms 9 ms 19 ms 223.28.2.70
6 18 ms 19 ms 19 ms 124.158.226.29
7 177 ms 179 ms 177 ms xe-0-1-0-1.cr-gw-2-sin-pip.sg.globaltransit.net
[124.158.224.241]
8 176 ms 180 ms 178 ms ae-2.br-gw-1-lax-pip.us.globaltransit.net [124.1
58.224.18]
9 177 ms 179 ms 179 ms ge-0-1-0-0.pp-gw-1-lax-pip.us.globaltransit.net
[124.158.250.9]
10 * * * Request timed out.

You can't tracert directly to twitch.tv but instead live.twitch.tv as instructed by twitch themselves.

http://help.twitch.tv/customer/portal/arti...route-to-twitch


I've already made a complaint sometime back in May to time directly and they have yet to resolve this issue in 4 months. Customer rep called me after I emailed but until then no one called to follow up on the status and twitch still continues to buffer erratically, sometimes it's fine, sometimes no.

Under Unifi, this was a no issue for a very long time during my 2 years contract. I'm sorry but the way Time has been performing is very dissapointing to say the least and they are behaving the same how TM was when they launched streamyx ages.

Latest result still shows this:

Tracing route to live.twitch.tv [199.9.249.120]
over a maximum of 30 hops:

1 8 ms 4 ms 6 ms 192.168.1.1
2 10 ms 10 ms 13 ms lo-0.ag-01-glsfb.ni.time.net.my [223.28.0.216]
3 12 ms 6 ms 12 ms 223.28.26.41
4 27 ms 19 ms 13 ms xe-0-1-0-0.cr-02-glsfb.ni.time.net.my [223.28.2.1]
5 20 ms 15 ms 18 ms 223.28.26.82
6 15 ms 15 ms 18 ms 124.158.226.149
7 175 ms 178 ms 179 ms xe-0-1-0-1.cr-gw-2-sin-pip.sg.globaltransit.net [124.158.224.241]
8 175 ms 178 ms 179 ms ae-2.br-gw-1-lax-pip.us.globaltransit.net [124.158.224.18]
9 177 ms 179 ms 180 ms ge-0-0-0-0.pp-gw-1-lax-pip.us.globaltransit.net [124.158.250.1]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.

This post has been edited by Problem: Sep 20 2015, 10:23 PM

For those on Astro IPTV with Time package (like me), good luck with your email getting bounced back and forth from Time and Astro both each passing the blame to each other when clearly Time is the owner of the internet part. Usual troubleshooting is suggesting that its the modem/router issue when its very clear their international bandwidth is horrible with inefficient routing especially that Global Transit node in Singapore being the worst.

Not to sound offensive to the contractors in this thread which they have been nothing but helpful, but I'm counting my days when the 2 years contract is over before reconsidering switching back to TM.

Guess my complain about Twitch about a few months back still hasn't been fixed.

Last I got a "call' from Time saying it was fixed at SG globaltransit but looks like it's back to being "problematic" again.

Sad that Time seems to have something against Twitch whereas under Unfi previously it doesn't sweat most times trying to buffer at source quality but for Time, even for low quality seems to be a struggle.

Tracing route to live.twitch.tv [199.9.249.133]
over a maximum of 30 hops:

1 6 ms 7 ms 9 ms 192.168.0.1
2 7 ms 18 ms 9 ms lo-0.ag-01-glsfb.ni.time.net.my [223.28.0.216]
3 40 ms 13 ms 7 ms 223.28.26.41
4 18 ms 22 ms 18 ms xe-0-1-0-0.cr-02-glsfb.ni.time.net.my [223.28.2.1]
5 12 ms 13 ms 15 ms 223.28.26.82
6 14 ms 17 ms 16 ms 124.158.226.149
7 187 ms 181 ms 185 ms xe-0-1-0-1.cr-gw-2-sin-pip.sg.globaltransit.net [124.158.224.241]
8 174 ms 228 ms 225 ms ae-2.br-gw-1-lax-pip.us.globaltransit.net [124.158.224.18]
9 186 ms 182 ms 187 ms ge-0-0-0-0.pp-gw-1-lax-pip.us.globaltransit.net [124.158.250.1]
10 * * * Request timed out.

Flashback 5 months ago

you can try using Twitch Buffering Fix (addon for Chrome) to see if it helps. Do note that it was removed from the Chrome store so you'll have to download it from any 3rd party sites like Link

I have my fair share of twitch issues for the past 9 months even after numerous complains (note that I am on Astro IPTV) with Time being the ISP provider but every so often it's as if Astro is bearing the grunt of the complain while the issue was not escalated directly to Time, and now Filefactory takes a long time to load well even on a Premium account.

Frustrating but might just wait out for the last 12 months before switching back to TM.