Hell is near my fellow friends...

I'm downloading some patches. And they are fast. Better download and patch fast
Before the internet slows down again and I have to wait for years to download the patch

reporting from Kl:

transfer rate still unstable or worst every minutes... browsing lyn took me hella 5 mins to keep refreshing... google can;t browse... I can't do anything...

What is TM doing again, now some sites SUPER FAST and some SUPER SLOW. Unbelievable, really runned by monkeys their company, orang utans and mat rempits.

speedtest to USA LOS ANGELES full speed.

Speedtest to BRITAIN LONDON. 0. cannot even start ==



This post has been edited by andrew9292: May 22 2009, 07:55 PM

I'm waiting for the 1000ms ping to come....hail to streamyx!!

oh boy, here comes the 'checking client version' 'stuckage'

No difference for me. Still need to refresh 20 times to get this page loaded

Weird, try access Yahoo!, it's freaking fast dispite the slowdown.

Reporting from SS19 subang jaya

Taking so damn long to load most of the sites

Even most of the avatars and signatures of lowyat members are not loading.

Crap

Your browser might be loading from a cache. Try clearing your history and browser data and try again. Or visit a site you haven't gone in a long time.

is the speed restored ?

let me know if yes?

is it better now, just now totally can not surf.

C:\Documents and Settings\Andrew>ping 202.188.0.133 -n 12

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=9ms TTL=247
Reply from 202.188.0.133: bytes=32 time=30ms TTL=247
Reply from 202.188.0.133: bytes=32 time=31ms TTL=247
Reply from 202.188.0.133: bytes=32 time=29ms TTL=247
Reply from 202.188.0.133: bytes=32 time=33ms TTL=247
Reply from 202.188.0.133: bytes=32 time=28ms TTL=247
Reply from 202.188.0.133: bytes=32 time=29ms TTL=247
Reply from 202.188.0.133: bytes=32 time=27ms TTL=247
Reply from 202.188.0.133: bytes=32 time=25ms TTL=247

Ping statistics for 202.188.0.133:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 33ms, Average = 22ms

okay, no packet loss to LOCAL routes now, but fluctuating pings now...what in the world is TM doing...i'm in Kota Damansara.

----------------

BUT LOOK AT THIS... 41% packet loss International Route.... with pings MORE STABLE than local route... Looks like the monkeys in TM are swinging from department to department, destroying equiptments... ==

C:\Documents and Settings\Andrew>ping hosted.filefront.com -n 12

Pinging hosted.filefront.com [38.118.213.25] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Reply from 38.118.213.25: bytes=32 time=324ms TTL=52
Reply from 38.118.213.25: bytes=32 time=326ms TTL=52
Reply from 38.118.213.25: bytes=32 time=324ms TTL=52
Reply from 38.118.213.25: bytes=32 time=326ms TTL=52
Reply from 38.118.213.25: bytes=32 time=325ms TTL=52
Request timed out.
Request timed out.
Reply from 38.118.213.25: bytes=32 time=327ms TTL=52
Reply from 38.118.213.25: bytes=32 time=328ms TTL=52

Ping statistics for 38.118.213.25:
Packets: Sent = 12, Received = 7, Lost = 5 (41% loss),
Approximate round trip times in milli-seconds:
Minimum = 324ms, Maximum = 328ms, Average = 325ms

C:\Documents and Settings\Andrew>

Ping is nice, but browsing to the website suck

Why? If slow and ping is not nice, full of Packet Loss or High Ping then its understandable.... might be lowyat net's server upgrade issue too. Otherwise it means TM is CAPPING to local site?

This post has been edited by andrew9292: May 22 2009, 08:13 PM

biasa la screamnuts

Might be related to "6:15PM - we are having network connectivity issues to TMNet. "

found out taiwan and hong kong website is blazing fast....too fast
some website can't even load

tmnet is giving the special dial up experience package for everyone who miss the good old day

1000ms ping for what... How about 100% timeout



This has happened in two consecutive pings

This post has been edited by kazek: May 22 2009, 09:21 PM

the speed didn't change from the 3 hrs ago since the epic downtime...