Things will never be the same...

This is an example of the routing problem. The above is located in NY, USA. Instead of taking a direct US route, it takes MY -> HK -> Tokyo -> LA -> NY. There is normally a lag in the HK link. Obviously TM engineers have not optimized routes or re-routed traffic back to normal routes.

Yes. Connecting to US sites are very laggy. Now I connect to playstation network on my PS3 is even laggier than before.

115.100.XX.XX
118.100.XX.XX

These 2 IP is total crap. Everything lags using these 2 IP. Btw, Im connecting from puchong area. Anyone in this area got problems?

Connecting to US sites is laggy for me as well, my area only gets the following range of IP 60, 118 and 124 and trying all 3 gives me the same results. Have a hard time reaching sites like Amazon and heck even google at times. I have complained to TM that before the cable cut everything was running fine then of course we had that cable problems then after repair.....it never went back to normal.

Everytime have to keep hitting the refresh button to try to force the site through. Used to download from RS @ 150Kbps, now I am lucky to even hit 20Kbps.

IP: 65.39.166.199
Date/Time: 01/07/2009 7:10:09 PM

1 * * * [-]
2 67 ms 66 ms * [219.93.218.177]
3 65 ms 64 ms 65 ms [219.93.217.165]
4 65 ms 66 ms 65 ms [58.27.103.218]
5 * * * [-]
6 70 ms 70 ms 113 ms [202.188.126.132]
7 72 ms 70 ms 71 ms [58.27.103.97]
8 72 ms 70 ms 71 ms [58.27.103.121]
9 360 ms 358 ms 360 ms [58.27.106.206]
10 271 ms 272 ms 292 ms Equinix-SJO.Peer1.net [206.223.116.30]
11 288 ms 288 ms 351 ms 10ge.ten1-1.sj-mkp2-dis-1.peer1.net [216.187.89.101]
12 279 ms 282 ms 280 ms 10ge-ten1-3.la-600w-cor-1.peer1.net [216.187.88.130]
13 274 ms 274 ms 274 ms 10ge.ten1-1.la-600w-cor-2.peer1.net [216.187.88.146]
14 317 ms 317 ms 316 ms 10ge-ten1-2.dal-eqx-cor-1.peer1.net [216.187.124.122]
15 331 ms 330 ms 333 ms 10ge-ten1-1.dal-eqx-cor-2.peer1.net [216.187.124.134]
16 334 ms 330 ms 331 ms 10ge-ten2-1.atl-telx-cor-1.peer1.net [216.187.124.118]
17 351 ms 352 ms 353 ms 10ge-ten1-1.atl-101mar-cor-1.peer1.net [216.187.120.226]
18 349 ms 349 ms 349 ms 10ge.xe-1-0-0.wdc-eqx-dis-1.peer1.net [216.187.115.37]
19 351 ms 351 ms 349 ms 10ge.ten1-2.wdc-sp2-cor-1.peer1.net [216.187.115.234]
20 349 ms 350 ms 349 ms 10ge.ten1-1.wdc-sp2-cor-2.peer1.net [216.187.116.254]
21 448 ms 460 ms 454 ms 10ge.xe-2-0-0.nyc-telx-dis-1.peer1.net [216.187.115.221]
22 454 ms 454 ms 469 ms oc192.xe-1-0-0.mtl-bvh-cor-1.peer1.net [216.187.115.53]
23 362 ms 362 ms 364 ms oc48-po6-0.mtl-bvh-dis-1.peer1.net [216.187.115.74]
24 365 ms 363 ms 363 ms [216.187.115.82]
25 * * * [-]
26 * * * [-]
27 * * * [-]
28 * * * [-]
29 * * * [-]

Destination not reached in 35 hops

In this case, the above host or the node before that appears not to be responding to ping or tracert requests, hence the unreachable status. This happens from other locations as well, not just Streamyx connection.

115.XXX is best for wow at the moment.
118.XXX sux
60.50.XXX sux
60.49.XXX sux

line restored. Running smooth as usual. Reporting from Cyberjaya

s7ran9er , is your connection really ok or you are just joking?

any reference? thanks

Its hard for me to open facebook too. getting impatient!!!

Everything is as slow as shit. Quake Live won't load at all, ACCA page takes forever to load.
f***ing shitmyx. Pissing me off.

facebook superbly kura2!

pauzai and mancy, are you getting pings of 500-600ms to facebook? Please post ping results.

This post has been edited by mylinear: Jan 7 2009, 10:23 PM

WHAT QUAKE LIVE IS ON NOW!!! ??? O-o

ping results for newgrounds, fileplanet, armorgames etc

Ping statistics for 38.119.130.61:
Packets: Sent = 100, Received = 68, Lost = 32 (32% loss),
Approximate round trip times in mili-seconds:
Minimum = 588ms, Maximum = 610ms, Average = 598ms


Ping statistics for 91.207.192.47:
Packets: Sent = 100, Received = 62, Lost = 38 (38% loss),
Approximate round trip times in mili-seconds:
Minimum = 186ms, Maximum = 300ms, Average = 255ms


Ping statistics for 69.89.31.246:
Packets: Sent = 100, Received = 65, Lost = 35 (35% loss),
Approximate round trip times in mili-seconds:
Minimum = 524ms, Maximum = 543ms, Average = 534ms


Ping statistics for 208.69.127.83:
Packets: Sent = 100, Received = 69, Lost = 31 (31% loss),
Approximate round trip times in mili-seconds:
Minimum = 575ms, Maximum = 621ms, Average = 586ms


Ping statistics for 207.38.10.202:
Packets: Sent = 100, Received = 68, Lost = 32 (32% loss),
Approximate round trip times in mili-seconds:
Minimum = 507ms, Maximum = 529ms, Average = 521ms

www.facebook.com >>> ping 677ms

Just the Beta, but what's the point when the page won't even load?

After the cable fix thing .. my download speed drop 50%