Jump to content

Worse than dial up


vern

Recommended Posts

11:30 PM and this is typical for my so called connection.

C:Documents and SettingsAdministrator>ping /w 5000 yahoo.com

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

Reply from 206.190.60.37: bytes=32 time=1522ms TTL=55

Reply from 206.190.60.37: bytes=32 time=1454ms TTL=55

Reply from 206.190.60.37: bytes=32 time=1568ms TTL=55

Reply from 206.190.60.37: bytes=32 time=1798ms TTL=55

Ping statistics for 206.190.60.37:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 1454ms, Maximum =  1798ms, Average =  1585ms

Would any of you pay $50.00 per month for this?

Link to comment
Share on other sites

Wow, thats bad.

C:Documents and SettingsAdmin>ping /w 5000 yahoo.com

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

Reply from 206.190.60.37: bytes=32 time=38ms TTL=51

Reply from 206.190.60.37: bytes=32 time=38ms TTL=51

Reply from 206.190.60.37: bytes=32 time=37ms TTL=51

Reply from 206.190.60.37: bytes=32 time=37ms TTL=51

Ping statistics for 206.190.60.37:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 37ms, Maximum = 38ms, Average = 37ms

Link to comment
Share on other sites

Ever since school let out that has been normal for my connection.

From about 4 am to 8 am ping times run about 50 to 100 ms.

Then at about 8:30 am which is now it starts.

C:Documents and SettingsAdministrator>ping yahoo.com

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

Reply from 206.190.60.37: bytes=32 time=323ms TTL=54

Reply from 206.190.60.37: bytes=32 time=529ms TTL=54

Reply from 206.190.60.37: bytes=32 time=403ms TTL=54

Reply from 206.190.60.37: bytes=32 time=529ms TTL=54

Ping statistics for 206.190.60.37:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 323ms, Maximum =  529ms, Average =  446ms

And during the day will get progressively worse

At about 9 pm it goes as high as 3500 to 4000+ ms.

TelCo has done nothing to fix it.

I call support, they open a ticket, I call back a week later, they say ticket was closed.

Rinse, repeat

Damn, even Starband satellite internet was better than this.

I may well just go back to dial up....

Link to comment
Share on other sites

C:Documents and SettingsAdministrator>ping testmy.net

Pinging testmy.net [74.54.226.166] with 32 bytes of data:

Reply from 74.54.226.166: bytes=32 time=72ms TTL=50

Reply from 74.54.226.166: bytes=32 time=74ms TTL=50

Reply from 74.54.226.166: bytes=32 time=71ms TTL=50

Reply from 74.54.226.166: bytes=32 time=73ms TTL=50

Ping statistics for 74.54.226.166:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 71ms, Maximum =  74ms, Average =  72ms

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

Reply from 64.233.187.99: bytes=32 time=70ms TTL=244

Reply from 64.233.187.99: bytes=32 time=67ms TTL=244

Reply from 64.233.187.99: bytes=32 time=70ms TTL=244

Reply from 64.233.187.99: bytes=32 time=70ms TTL=244

Ping statistics for 64.233.187.99:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 67ms, Maximum =  70ms, Average =  69ms

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

Reply from 206.190.60.37: bytes=32 time=134ms TTL=54

Reply from 206.190.60.37: bytes=32 time=99ms TTL=54

Reply from 206.190.60.37: bytes=32 time=74ms TTL=54

Reply from 206.190.60.37: bytes=32 time=79ms TTL=54

Ping statistics for 206.190.60.37:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 74ms, Maximum =  134ms, Average =  96ms

maybe i'll get an extra hour or two of decent performance today before the kiddies start up bittorrent.

Link to comment
Share on other sites

You know you said it right there, frickin torrents, shit that erks me, people not only trade stolen shit, but they are leaching bandwidth at the same time, from others.

There was a guy that had uncapped his modem near me, and every night he would set his torrents up, no one on the node could barely brows the net, someone, took care of him, and then the ISP did.  :haha:

Link to comment
Share on other sites

Interesting.

I have received no notice whatsoever about that.

Why would I pay $50.00 per month for DSL when I won't even be able to download the new WoW expansion when it comes out in a few months without exceeding the bandwidth limit?

I'm feeling pretty smart now for not signing a service contract with them 10 months ago to get a 10 dollar per month discount.

I think I will be downgrading my account today to the 256 / 100 Kbps $19.95 per month plan.

EDIT: I'm connected to a remote DSLAM unit located 16 miles from the CO. Bittorernt can and does slow it down for everybody because the span between the unit and the CO isn't fat enough to support all the users using at the same time.

Link to comment
Share on other sites

Interesting.

I have received no notice whatsoever about that.

Why would I pay $50.00 per month for DSL when I won't even be able to download the new WoW expansion when it comes out in a few months without exceeding the bandwidth limit?

I'm feeling pretty smart now for not signing a service contract with them 10 months ago to get a 10 dollar per month discount.

I think I will be downgrading my account today to the 256 / 100 kbps $19.95 per month plan.

No one is getting notice as far as I know.

Ask them if they call that 256/100 service broadband. I would be interested to see if they still do. Since the FCC now says broadband is 768kbps or faster.

Link to comment
Share on other sites

C:Documents and SettingsAdministrator>ping /w 10000 testmy.net

Pinging testmy.net [74.54.226.166] with 32 bytes of data:

Reply from 74.54.226.166: bytes=32 time=1248ms TTL=50

Reply from 74.54.226.166: bytes=32 time=1165ms TTL=50

Reply from 74.54.226.166: bytes=32 time=1015ms TTL=50

Reply from 74.54.226.166: bytes=32 time=1017ms TTL=50

Ping statistics for 74.54.226.166:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 1015ms, Maximum =  1248ms, Average =  1111ms

It's either this crap or satellite which is just as bad lagwise.

Well I just got a call back from the PR people and the guy tells me they have been "upgrading" the main lines from the CO the the big CO and are having some problems with it and it should be fixed by tomorrow.

And he ask me to wait until tomorrow to call the PSC if I would.

I'll giver em one more day.

Link to comment
Share on other sites

Maybe squeaking loud enough to the right person helps.get some grease....

And mentioning the PSC didn't hurt either.

C:Documents and SettingsAdministrator>ping /w 10000 yahoo.com

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

Reply from 206.190.60.37: bytes=32 time=82ms TTL=54

Reply from 206.190.60.37: bytes=32 time=75ms TTL=54

Reply from 206.190.60.37: bytes=32 time=72ms TTL=54

Reply from 206.190.60.37: bytes=32 time=71ms TTL=54

Ping statistics for 206.190.60.37:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 71ms, Maximum =  82ms, Average =  75ms

C:Documents and SettingsAdministrator>ping google.com

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

Reply from 72.14.207.99: bytes=32 time=63ms TTL=244

Reply from 72.14.207.99: bytes=32 time=61ms TTL=244

Reply from 72.14.207.99: bytes=32 time=59ms TTL=244

Reply from 72.14.207.99: bytes=32 time=81ms TTL=244

Ping statistics for 72.14.207.99:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 59ms, Maximum =  81ms, Average =  66ms

Link to comment
Share on other sites

My only options here are this, satellite, or dial up.

I had Starband and Wildblue.

Won't go through that again.

I mentioned to the phone guy I spoke with yesterday the new 5 gig bandwidth limit and he said he hadn't heard anything about that.

Not surprising as they seem to be trying to keep it a secret for some reason.

He told me, well Wildblue and other satellite providers use caps.

I ask him if the DSLAM unit cost 500 million dollars like a satellite placed in geostationary orbit does since that is the only way to add bandwidth to a satellite connection.

I find it extremely annoying whenever anyone tries to compare apples and lemons when attempting to make a point.

Link to comment
Share on other sites

I ask him if the DSLAM unit cost 500 million dollars like a satellite placed in geostationary orbit does since that is the only way to add bandwidth to a satellite connection.

I find it extremely annoying whenever anyone tries to compare apples and lemons when attempting to make a point.

very true indeed.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...