BolehVPN: Freedom Through Security

«
»

My Internet Connection is Like Woe

The 115.132.x.x range which I have been locked to is TOTALLY hopeless:

Now just to make sure it wasn’t a line problem, I pinged our Malaysian hosted website:

Pinging bolehvpn.net [202.75.55.245] with 32 bytes of data:
Reply from 202.75.55.245: bytes=32 time=66ms TTL=55
Reply from 202.75.55.245: bytes=32 time=62ms TTL=55
Reply from 202.75.55.245: bytes=32 time=64ms TTL=55
Reply from 202.75.55.245: bytes=32 time=63ms TTL=55
Reply from 202.75.55.245: bytes=32 time=63ms TTL=55
Reply from 202.75.55.245: bytes=32 time=63ms TTL=55
Reply from 202.75.55.245: bytes=32 time=64ms TTL=55
Reply from 202.75.55.245: bytes=32 time=62ms TTL=55
Reply from 202.75.55.245: bytes=32 time=63ms TTL=55
Reply from 202.75.55.245: bytes=32 time=63ms TTL=55
Reply from 202.75.55.245: bytes=32 time=63ms TTL=55
Reply from 202.75.55.245: bytes=32 time=63ms TTL=55
Reply from 202.75.55.245: bytes=32 time=64ms TTL=55
Reply from 202.75.55.245: bytes=32 time=62ms TTL=55
Reply from 202.75.55.245: bytes=32 time=62ms TTL=55

Ping statistics for 202.75.55.245:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 66ms, Average = 63ms

Singapore also returns a good result:

Ping statistics for 202.79.222.13:
Packets: Sent = 104, Received = 104, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 87ms, Average = 72ms

Now pinging gmail.com returns not so great results:

Pinging gmail.com [209.85.171.83] with 32 bytes of data:
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237
Reply from 209.85.171.83: bytes=32 time=335ms TTL=237
Reply from 209.85.171.83: bytes=32 time=334ms TTL=237
Request timed out.
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237
Request timed out.
Request timed out.
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237
Reply from 209.85.171.83: bytes=32 time=335ms TTL=237
Reply from 209.85.171.83: bytes=32 time=334ms TTL=237
Reply from 209.85.171.83: bytes=32 time=335ms TTL=237
Reply from 209.85.171.83: bytes=32 time=334ms TTL=237
Reply from 209.85.171.83: bytes=32 time=334ms TTL=237
Request timed out.
Reply from 209.85.171.83: bytes=32 time=338ms TTL=237
Request timed out.
Reply from 209.85.171.83: bytes=32 time=337ms TTL=237
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237
Reply from 209.85.171.83: bytes=32 time=338ms TTL=237
Reply from 209.85.171.83: bytes=32 time=338ms TTL=237
Reply from 209.85.171.83: bytes=32 time=335ms TTL=237
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237
Reply from 209.85.171.83: bytes=32 time=334ms TTL=237
Reply from 209.85.171.83: bytes=32 time=335ms TTL=237
Reply from 209.85.171.83: bytes=32 time=333ms TTL=237
Reply from 209.85.171.83: bytes=32 time=334ms TTL=237
Reply from 209.85.171.83: bytes=32 time=335ms TTL=237
Reply from 209.85.171.83: bytes=32 time=335ms TTL=237
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237
Reply from 209.85.171.83: bytes=32 time=336ms TTL=237

Ping statistics for 209.85.171.83:
Packets: Sent = 33, Received = 28, Lost = 5 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 338ms, Average = 335ms

Now check out the ping to UK:

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Request timed out.
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Request timed out.
Request timed out.
Reply from 212.58.224.138: bytes=32 time=349ms TTL=110
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Reply from 212.58.224.138: bytes=32 time=351ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Request timed out.
Request timed out.
Reply from 212.58.224.138: bytes=32 time=350ms TTL=110
Reply from 212.58.224.138: bytes=32 time=349ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Reply from 212.58.224.138: bytes=32 time=349ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Request timed out.
Request timed out.
Reply from 212.58.224.138: bytes=32 time=350ms TTL=110
Reply from 212.58.224.138: bytes=32 time=349ms TTL=110
Reply from 212.58.224.138: bytes=32 time=350ms TTL=110
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=350ms TTL=110
Reply from 212.58.224.138: bytes=32 time=350ms TTL=110
Reply from 212.58.224.138: bytes=32 time=350ms TTL=110
Request timed out.
Reply from 212.58.224.138: bytes=32 time=348ms TTL=110

Ping statistics for 212.58.224.138:
Packets: Sent = 31, Received = 19, Lost = 12 (38% loss),
Approximate round trip times in milli-seconds:
Minimum = 348ms, Maximum = 351ms, Average = 349ms

I don’t know in what world is 15-38% loss acceptable…a third world country perhaps? This has also been going for more than a month now.

Tags: , , , , ,

This entry was posted on Wednesday, March 18th, 2009 at 11:10 pm and is filed under Streamyx. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

6 Responses to “My Internet Connection is Like Woe”

  1. avatar Fallen Says:
    March 19th, 2009 at 11:23 pm

    I feel your pain brother. I’ve been using my line for about 2 years now and I have ever only gotten the following IP ranges
    60.50 (fantastic, fast speeds for everything)
    60.52 (good browsing speeds, not so much for dling)
    118.101 (utter crap)

    Then there was that whole incident last month, and i got crappy speeds regardless of what IP got. Nevertheless I remained patient and optimistic after following your blog, they have to eventually fix it rite?

    Or so I thought. About weeks ago it seems that everything was back as normal, huzzah!!! For about a week… then they decided to disconnect my line just like that. Took me about a fulldays worth of redialing before I managed to reconnect.

    Then they locked me down to the 115,118 and 124 IP ranges. Googling the IP’s confirmed my worst fears.

    I’ll be joining you in your complains as a fellow kindred spirit.

  2. avatar tessa101 Says:
    March 20th, 2009 at 9:59 pm

    thats quite a large amount of packet loss. what speed do you end up downloading at (although im guessing its very jumpy)

  3. avatar Reuben Says:
    March 20th, 2009 at 11:34 pm

    4 kB/sec :( The loss is too high to even maintain a connection to the VPN.

  4. avatar Nick Says:
    March 21st, 2009 at 10:32 pm

    Connection to the UK is fubared to the max

  5. avatar snow_meow Says:
    March 22nd, 2009 at 11:56 am

    I swear I am so pissed at Streamyx.

    Ever since March 5, my connection has gotten worst.
    I keep getting disconnected almost hourly.
    Within an hour my IP changes at least 3 times. Not to mention even when I have an IP, I cannot surf nor download.
    When I get an IP it is downloading super slow like having a max of 20kb/s.

    I think at certain times, they are locking me to certain IPs which sucks because I might land up with one that does not allow me to get onto the Internet or download.

    I call Streamyx to complain and their solution after putting me on hold is to restart my modem and call them back if I still have problems.
    Well, what do you know? It has NOT WORK !!!
    Now when you call them, there is supposedly something wrong with their telephone system or something like that.

  6. avatar yinsw Says:
    March 24th, 2009 at 3:16 pm

    Phew.. I thought I was the one having so much packet loss. This actually has been happening for few months. I usually tested pinging http://www.yahoo.com whenever I reconnected.

Leave a Reply