Streamyx Slow Lar !! Solutions ?

I use to be a strong advocate... now rather prefer to give up.

Why bother about Internet ? Relax...





Behold the quietness; zen.

Take at look the ping snapshot at 3 Nov 2007; 9:44 AM.

C:\Users\brandon>ping yahoo.com

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=702ms TTL=52
Reply from 216.109.112.135: bytes=32 time=367ms TTL=52
Reply from 216.109.112.135: bytes=32 time=918ms TTL=53
Reply from 216.109.112.135: bytes=32 time=612ms TTL=52

Ping statistics for 216.109.112.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 367ms, Maximum = 918ms, Average = 649ms

C:\Users\brandon>ping netvibes.com

Pinging netvibes.com [193.189.143.249] with 32 bytes of data:

Reply from 193.189.143.249: bytes=32 time=1158ms TTL=241
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 193.189.143.249:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 1158ms, Maximum = 1158ms, Average = 1158ms

C:\Users\brandon>ping youtube.com

Pinging youtube.com [208.65.153.238] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Reply from 208.65.153.238: bytes=32 time=994ms TTL=242

Ping statistics for 208.65.153.238:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 994ms, Maximum = 994ms, Average = 994ms

C:\Users\brandon>ping google.com

Pinging google.com [64.233.167.99] with 32 bytes of data:

Reply from 64.233.167.99: bytes=32 time=1014ms TTL=241
Reply from 64.233.167.99: bytes=32 time=1094ms TTL=241
Reply from 64.233.167.99: bytes=32 time=924ms TTL=241
Request timed out.

Ping statistics for 64.233.167.99:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 924ms, Maximum = 1094ms, Average = 1010ms

C:\Users\brandon>ping pageflakes.com

Pinging pageflakes.com [74.205.69.104] with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 74.205.69.104: bytes=32 time=780ms TTL=110
Reply from 74.205.69.104: bytes=32 time=953ms TTL=110

Ping statistics for 74.205.69.104:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 780ms, Maximum = 953ms, Average = 866ms

C:\Users\brandon>ping friendster.com

Pinging friendster.com [209.11.168.112] with 32 bytes of data

Reply from 209.11.168.112: bytes=32 time=878ms TTL=108
Reply from 209.11.168.112: bytes=32 time=1133ms TTL=108
Request timed out.
Reply from 209.11.168.112: bytes=32 time=1081ms TTL=108

Ping statistics for 209.11.168.112:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 878ms, Maximum = 1133ms, Average = 1030ms

C:\Users\brandon>ping facebook.com

Pinging facebook.com [204.15.20.25] with 32 bytes of data:

Reply from 204.15.20.25: bytes=32 time=254ms TTL=236
Reply from 204.15.20.25: bytes=32 time=633ms TTL=236
Reply from 204.15.20.25: bytes=32 time=999ms TTL=236
Reply from 204.15.20.25: bytes=32 time=1095ms TTL=236

Ping statistics for 204.15.20.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 254ms, Maximum = 1095ms, Average = 745ms

Is this a strategy ? Marketing to that sort ....

Only Yahoo, Google, friendster and facebook can be well connected, others in vain.

But then again, on a second thought... Maybe I should restart the router (the non-enterprise router)....

C:\Users\brandon>ping yahoo.com

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=290ms TTL=53
Reply from 216.109.112.135: bytes=32 time=290ms TTL=53
Request timed out.
Reply from 216.109.112.135: bytes=32 time=312ms TTL=53

Ping statistics for 216.109.112.135:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 290ms, Maximum = 312ms, Average = 297ms

C:\Users\brandon>ping netvibes.com

Pinging netvibes.com [193.189.143.249] with 32 bytes of data:

Reply from 193.189.143.249: bytes=32 time=374ms TTL=241
Reply from 193.189.143.249: bytes=32 time=376ms TTL=241
Request timed out.
Reply from 193.189.143.249: bytes=32 time=373ms TTL=241

Ping statistics for 193.189.143.249:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 373ms, Maximum = 376ms, Average = 374ms

C:\Users\brandon>ping youtube.com

Pinging youtube.com [208.65.153.253] with 32 bytes of data:

Reply from 208.65.153.253: bytes=32 time=245ms TTL=242
Reply from 208.65.153.253: bytes=32 time=239ms TTL=242
Reply from 208.65.153.253: bytes=32 time=225ms TTL=242
Reply from 208.65.153.253: bytes=32 time=233ms TTL=242

Ping statistics for 208.65.153.253:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 225ms, Maximum = 245ms, Average = 235ms

C:\Users\brandon>ping google.com

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=284ms TTL=240
Reply from 72.14.207.99: bytes=32 time=289ms TTL=240
Reply from 72.14.207.99: bytes=32 time=280ms TTL=240
Reply from 72.14.207.99: bytes=32 time=287ms TTL=240

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 280ms, Maximum = 289ms, Average = 285ms

C:\Users\brandon>ping pageflakes.com

Pinging pageflakes.com [74.205.69.104] with 32 bytes of data:

Reply from 74.205.69.104: bytes=32 time=317ms TTL=110
Reply from 74.205.69.104: bytes=32 time=370ms TTL=110
Reply from 74.205.69.104: bytes=32 time=317ms TTL=110
Reply from 74.205.69.104: bytes=32 time=311ms TTL=110

Ping statistics for 74.205.69.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 311ms, Maximum = 370ms, Average = 328ms

C:\Users\brandon>ping friendster.com

Pinging friendster.com [209.11.168.112] with 32 bytes of data:

Request timed out.
Reply from 209.11.168.112: bytes=32 time=232ms TTL=108
Reply from 209.11.168.112: bytes=32 time=267ms TTL=108
Reply from 209.11.168.112: bytes=32 time=236ms TTL=108

Ping statistics for 209.11.168.112:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 232ms, Maximum = 267ms, Average = 245ms

C:\Users\brandon>ping facebook.com

Pinging facebook.com [204.15.20.25] with 32 bytes of data:

Reply from 204.15.20.25: bytes=32 time=234ms TTL=236
Reply from 204.15.20.25: bytes=32 time=232ms TTL=236
Reply from 204.15.20.25: bytes=32 time=236ms TTL=236
Reply from 204.15.20.25: bytes=32 time=246ms TTL=236

Ping statistics for 204.15.20.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 232ms, Maximum = 246ms, Average = 237ms


Looks good ? Improved tremendously.

The problem is local, the non-enterprise router cannot take too much heat... to be exact, it doesn't have a good memory-buffer system. Restarting will flush out active memory and it will then be able to make good sense of many things again.

So, solution is too restart your router whenever you find your streamyx connection funny.

Now, we can go back to a balance lifestyle.

Comments

Stephen said…
Well I'm giving up on streamyx anyways, my house streamyx was down last weekend, office line down twice in 2 weeks resulting in 10 days without internet connection... after it was fixed connection speed downed to 146kbps downstream O_o and ping results are always more than 1000ms T_T

I'm changing to Maxis broadband soon, hopefully it is better...
Brandon Teoh said…
cool...

What is the subscription fees look like for Maxis broadband ?