Anyone experience Starhub lag

[Weinter]

Sorry I think it is their DNS server down

Tracing route to notebookcheck.com [83.64.101.24]

over a maximum of 30 hops:



1 11 ms 11 ms 10 ms cm1.zeta242.maxonline.com.sg [116.87.242.1]

2 10 ms 13 ms 39 ms 172.20.54.1

3 9 ms 10 ms 11 ms 172.26.54.1

4 26 ms 11 ms 36 ms 172.20.7.18

5 12 ms 9 ms 12 ms 172.20.7.42

6 13 ms 13 ms 14 ms 203.116.250.205

7 12 ms 15 ms 26 ms 203.118.3.163

8 95 ms 108 ms 96 ms p16-2-1-2.r21.tokyjp01.jp.bb.gin.ntt.net [129.250.11.29]

9 106 ms 117 ms 107 ms ae-3.r21.osakjp01.jp.bb.gin.ntt.net [129.250.4.214]

10 215 ms 254 ms 216 ms as-1.r21.snjsca04.us.bb.gin.ntt.net [129.250.3.197]

11 231 ms 243 ms 273 ms ae-0.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.96]

12 289 ms 320 ms 291 ms as-1.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.166]

13 298 ms 319 ms 292 ms us-was01a-ri1-ge-0-0-0.aorta.net [206.223.115.104]

14 302 ms 291 ms 306 ms us-was02a-rd1-10ge-3-0.aorta.net [213.46.190.189]

15 315 ms 306 ms 302 ms fr-par02a-rd1-pos-2-0.aorta.net [213.46.160.105]

16 304 ms 305 ms 301 ms fr-par02a-rd2-ge-12-0.aorta.net [213.46.163.166]

17 340 ms 351 ms 334 ms at-vie01a-ra3-ge-0-0-0.aorta.net [213.46.160.190]

18 360 ms 332 ms 333 ms vie1-tg-01-001.shuttle.vien.inode.at [213.46.173.62]

19 * * * Request timed out.

20 335 ms 336 ms 333 ms mypro-hosting.com [83.64.101.24]



Trace complete.

The hops in bold has a very very high latency
One Word Starhub sucks

[JPadPro]

The crawling speed of web surfing and etc is getting ridiculous and unbearable during peak hours. :(

[DenverSuker]

i did a test too...... but my test was only good for the first 8 loops ....other than that ..
the rest just timed out...... my lord!!!!!!

[albertchng]

Sorry I think it is their DNS server down

Tracing route to notebookcheck.com [83.64.101.24]
over a maximum of 30 hops:

1 11 ms 11 ms 10 ms cm1.zeta242.maxonline.com.sg [116.87.242.1]
2 10 ms 13 ms 39 ms 172.20.54.1
3 9 ms 10 ms 11 ms 172.26.54.1
4 26 ms 11 ms 36 ms 172.20.7.18
5 12 ms 9 ms 12 ms 172.20.7.42
6 13 ms 13 ms 14 ms 203.116.250.205
7 12 ms 15 ms 26 ms 203.118.3.163
8 95 ms 108 ms 96 ms p16-2-1-2.r21.tokyjp01.jp.bb.gin.ntt.net [129.250.11.29]
9 106 ms 117 ms 107 ms ae-3.r21.osakjp01.jp.bb.gin.ntt.net [129.250.4.214]
10 215 ms 254 ms 216 ms as-1.r21.snjsca04.us.bb.gin.ntt.net [129.250.3.197]
11 231 ms 243 ms 273 ms ae-0.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.96]
12 289 ms 320 ms 291 ms as-1.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.166]
13 298 ms 319 ms 292 ms us-was01a-ri1-ge-0-0-0.aorta.net [206.223.115.104]
14 302 ms 291 ms 306 ms us-was02a-rd1-10ge-3-0.aorta.net [213.46.190.189]
15 315 ms 306 ms 302 ms fr-par02a-rd1-pos-2-0.aorta.net [213.46.160.105]
16 304 ms 305 ms 301 ms fr-par02a-rd2-ge-12-0.aorta.net [213.46.163.166]
17 340 ms 351 ms 334 ms at-vie01a-ra3-ge-0-0-0.aorta.net [213.46.160.190]
18 360 ms 332 ms 333 ms vie1-tg-01-001.shuttle.vien.inode.at [213.46.173.62]
19 * * * Request timed out.
20 335 ms 336 ms 333 ms mypro-hosting.com [83.64.101.24]

Trace complete.

The hops in bold has a very very high latency
One Word Starhub sucks


Here's mine.

Tracing route to notebookcheck.com [83.64.101.24]
over a maximum of 30 hops:

5 8 ms 9 ms 9 ms ge-3-0-0-3500.sapporo.singnet.com.sg [202.166.124.153]
6 8 ms 9 ms 9 ms xe-2-2-0-0.budweiser.singnet.com.sg [202.166.126.9]
7 9 ms 9 ms 9 ms ae1-0.beck.singnet.com.sg [202.166.124.234]
8 9 ms 9 ms 19 ms 203.208.190.57
9 9 ms 11 ms 9 ms ge-1-1-0-0.sngtp-ar6.ix.singtel.com [203.208.183.81]
10 268 ms 196 ms 196 ms so-3-3-3-0.lonlx-cr2.ix.singtel.com [203.208.151.130]
11 279 ms 279 ms 279 ms uk-lon01a-rd2-ge-2-2.aorta.net [195.66.226.89]
12 277 ms 279 ms 279 ms uk-lon02a-rd1-pos-0-0.aorta.net [213.46.174.77]
13 275 ms 273 ms 273 ms 213.46.174.169
14 215 ms 216 ms 216 ms at-vie15a-ra1-xe-0-1-0-0.aorta.net [213.46.160.234]
15 216 ms 217 ms 216 ms at-vie01a-ra3-ge-4-0-0-0.aorta.net [213.46.173.137]
16 216 ms 216 ms 216 ms vie1-tg-01-001.shuttle.vien.inode.at [213.46.173.62]
17 215 ms 216 ms 216 ms 172.22.253.2
18 214 ms 216 ms 216 ms mypro-hosting.com [83.64.101.24]

Trace complete.

Sama sama mah. SingNet user here.

[Weinter]

Sorry can you open your eyes and look
We have 20 hops you have 18 hops
My 19 hop time out
Your highest is only 216ms for 8 hops
Mine is 360ms for 9 hops
HOW IS IT THE SAME
100ms difference is alot for 9 hops
And this is using small test packets can you imagine DATA PACKETS?!

[albertchng]

Sorry I think it is their DNS server down

Tracing route to notebookcheck.com [83.64.101.24]
over a maximum of 30 hops:

1 11 ms 11 ms 10 ms cm1.zeta242.maxonline.com.sg [116.87.242.1]
2 10 ms 13 ms 39 ms 172.20.54.1
3 9 ms 10 ms 11 ms 172.26.54.1
4 26 ms 11 ms 36 ms 172.20.7.18
5 12 ms 9 ms 12 ms 172.20.7.42
6 13 ms 13 ms 14 ms 203.116.250.205
7 12 ms 15 ms 26 ms 203.118.3.163 SINGAPORE
8 95 ms 108 ms 96 ms p16-2-1-2.r21.tokyjp01.jp.bb.gin.ntt.net [129.250.11.29] JAPAN
9 106 ms 117 ms 107 ms ae-3.r21.osakjp01.jp.bb.gin.ntt.net [129.250.4.214] JAPAN
10 215 ms 254 ms 216 ms as-1.r21.snjsca04.us.bb.gin.ntt.net [129.250.3.197] USA
11 231 ms 243 ms 273 ms ae-0.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.96] USA
12 289 ms 320 ms 291 ms as-1.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.166] USA
13 298 ms 319 ms 292 ms us-was01a-ri1-ge-0-0-0.aorta.net [206.223.115.104] USA
14 302 ms 291 ms 306 ms us-was02a-rd1-10ge-3-0.aorta.net [213.46.190.189] USA
15 315 ms 306 ms 302 ms fr-par02a-rd1-pos-2-0.aorta.net [213.46.160.105] FRANCE
16 304 ms 305 ms 301 ms fr-par02a-rd2-ge-12-0.aorta.net [213.46.163.166] FRANCE
17 340 ms 351 ms 334 ms at-vie01a-ra3-ge-0-0-0.aorta.net [213.46.160.190] AUSTRIA
18 360 ms 332 ms 333 ms vie1-tg-01-001.shuttle.vien.inode.at [213.46.173.62] AUSTRIA
19 * * * Request timed out.
20 335 ms 336 ms 333 ms mypro-hosting.com [83.64.101.24] AUSTRIA

Trace complete.

The hops in bold has a very very high latency
One Word Starhub sucks


Here's mine.

Tracing route to notebookcheck.com [83.64.101.24]
over a maximum of 30 hops:

5 8 ms 9 ms 9 ms ge-3-0-0-3500.sapporo.singnet.com.sg [202.166.124.153]
6 8 ms 9 ms 9 ms xe-2-2-0-0.budweiser.singnet.com.sg [202.166.126.9]
7 9 ms 9 ms 9 ms ae1-0.beck.singnet.com.sg [202.166.124.234]
8 9 ms 9 ms 19 ms 203.208.190.57
9 9 ms 11 ms 9 ms ge-1-1-0-0.sngtp-ar6.ix.singtel.com [203.208.183.81] SINGAPORE
10 268 ms 196 ms 196 ms so-3-3-3-0.lonlx-cr2.ix.singtel.com [203.208.151.130] UK
11 279 ms 279 ms 279 ms uk-lon01a-rd2-ge-2-2.aorta.net [195.66.226.89] UK
12 277 ms 279 ms 279 ms uk-lon02a-rd1-pos-0-0.aorta.net [213.46.174.77] UK
13 275 ms 273 ms 273 ms 213.46.174.169 AUSTRIA
14 215 ms 216 ms 216 ms at-vie15a-ra1-xe-0-1-0-0.aorta.net [213.46.160.234] AUSTRIA
15 216 ms 217 ms 216 ms at-vie01a-ra3-ge-4-0-0-0.aorta.net [213.46.173.137] AUSTRIA
16 216 ms 216 ms 216 ms vie1-tg-01-001.shuttle.vien.inode.at [213.46.173.62] AUSTRIA
17 215 ms 216 ms 216 ms 172.22.253.2
18 214 ms 216 ms 216 ms mypro-hosting.com [83.64.101.24] AUSTRIA

Trace complete.

Sama sama mah. SingNet user here.


Sorry can you open your eyes and look
We have 20 hops you have 18 hops
My 19 hop time out
Your highest is only 216ms for 8 hops
Mine is 360ms for 9 hops
HOW IS IT THE SAME
100ms difference is alot for 9 hops
And this is using small test packets can you imagine DATA PACKETS?!


Look at SH route v/s SN route, you should know why the extra hops & bad latency.

[phuque99]

Sorry can you open your eyes and look
We have 20 hops you have 18 hops
My 19 hop time out
Your highest is only 216ms for 8 hops
Mine is 360ms for 9 hops
HOW IS IT THE SAME
100ms difference is alot for 9 hops
And this is using small test packets can you imagine DATA PACKETS?!

Noob interpretation, time out and intermittent hop latency means nothing. Neither does number of hops. Your actual performance is the last line, the latency response of the destination. Given 1 million hops, 1mil millisecond on all routers, it means nothing.

What is meaningful is your last hop response time, that's all. So don't write noob response, see last hop, and last hop alone. That's your actual performance, number of hops (and their latency) don't mean anything.

Also, one hop measurement is not meaningful. Get more average performance more important, like ping over 5 minutes or winMTR tool for timed averages. Lastly, most upstream provider SLA is about 300ms from one point over another. Thus 0.1s over so many provider is hardly anything to kpkb about, let alone non-commercial subscription :P

So relax, don't have wrong expectations.

[liangtam]

Nothing wrong with the jump mah, the traffic did reach aorta, albeit at a different location. Hence ISP at other side have to route it over to their other PoPs.

While u can say its not that efficient route when u make a comparison, there are other factors that is taken at from router's side. As well as the routes made available from your isp(like sh) as well as the other end willing open up not.

[osimese]

so many ppl also kanna the lag..

[hotweb]

I cannot even surf at all on sunday (now), esp overseas websites. cannot even load a normal page.

what is wrong with Starhub? broken undersea cable?
still paying $30 a month but hardly able to surf anything..going to jump ship soon...

[Walk_Hard]

mine has been crawling over the past month. I can't even update steam to play my game! And surfing to overseas sites is just awful, takes forever to load anything.

WTF is starhub doing about this?

[spark7]

pls call them and F them. I been doing it everyday to vent my anger! show them we r not happy!

[kenloonglow]

I called a few times...no1 pick...busy leh

[blacklotus]

pls call them and F them. I been doing it everyday to vent my anger! show them we r not happy!

It seems that SH's CSOs are now also FTs. The ones I managed to contact nowadays all speak with Tagalog accent one. :( Last time, I still can get 1 or 2 local girls next door. Guess SH's service is so bad our locals also don't wanna handle the complaints liao. =:p

[santaboi]

Tracing route to notebookcheck.com [83.64.101.24]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 8 ms 8 ms cm1.kappa196.maxonline.com.sg [58.182.196.1]
3 13 ms 8 ms 9 ms 172.20.52.65
4 10 ms 48 ms 14 ms 172.26.52.1
5 14 ms 10 ms 27 ms 172.20.7.18
6 16 ms 12 ms 37 ms 172.20.7.42
7 15 ms * 14 ms 203.116.250.205
8 14 ms 13 ms 16 ms 203.118.3.163
9 220 ms 212 ms 211 ms p16-2-1-2.r21.tokyjp01.jp.bb.gin.ntt.net [129.25
0.11.29]
10 220 ms 232 ms 217 ms ae-3.r21.osakjp01.jp.bb.gin.ntt.net [129.250.4.2
14]
11 226 ms 227 ms 239 ms as-1.r21.snjsca04.us.bb.gin.ntt.net [129.250.3.1
97]
12 225 ms 224 ms 226 ms ae-0.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.9
6]
13 282 ms 305 ms 291 ms as-1.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.1
66]
14 * * * Request timed out.
15 317 ms 286 ms 292 ms us-was02a-rd1-10ge-4-0.aorta.net [213.46.190.193
]
16 370 ms 366 ms 383 ms fr-par02a-rd1-pos-13-0-0.aorta.net [213.46.160.1
69]
17 374 ms 369 ms 369 ms fr-par02a-rd2-ge-12-0.aorta.net [213.46.163.166]

18 402 ms 412 ms 400 ms at-vie01a-ra3-ge-0-0-0.aorta.net [213.46.160.190
]
19 394 ms 393 ms 395 ms vie1-tg-01-001.shuttle.vien.inode.at [213.46.173
.62]
20 * * * Request timed out.
21 392 ms 389 ms 392 ms mypro-hosting.com [83.64.101.24]

Trace complete.