Extreme DSL Suckiness
Jan. 30th, 2003 10:55 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
shannon_aWell, it's now been about 5 and a half days since we got our new DSL line from Extreme DSL, and I have to say at this point I'm very disappointed with their service.
I've writen elsewhere, at length, about their lies concerning turn-on dates.
And, now that we have a line, there's no joy.
In the 5.5 days since we got our service up, there are have been four downtimes, the first just a couple of minutes after I got everything working on our end. That first was 4 hours long; last night we were down for 3 hours. The two other downtimes were about a half hour each in length.
Total downtime: 8 hours out of ~132, or 6%. That I know of.
I was willing to put aside the first time downtime, saying that it might have been due to the recent MSSQL attack, but after three repeats ... it's starting to get pretty old and inexcusable.
Worse, whenever we have actual uptime, the quality of our line regularly varies between good and almost unusable. Our response time for our next-hop router varies from about 20ms, where it should be, up to 2s. Which is to say: 100x slower than it should be.
I'm going to swap some cables and move some machines around this weekend to bring my home setup into ExtremeDSL's "specs" (though they should be unecessary), but if these problems continue afterward, someone's going to get quite an earful over at ExtremeDSL, and will continue to on a daily basis till they start delivering the service they advertise. (And I should note that the downtimes are well and truly their problems; it's only the bad line quality that I need to investigate from my side first.)
This morning's line:
7377 packets transmitted, 7342 packets received, 0% packet loss
round-trip min/avg/max = 17.7/123.1/4228.0 ms
Slightly better than it has been, but still about 6x worse than it should be, on average, and flapping terribly.
Damn it.
Having to run a ping all the time, so that I can see if my line has gone done or just gotten dramatically slow when I stop being able to access remote sites I'm working on is getting very old.
The workout this morning was OK.
I've writen elsewhere, at length, about their lies concerning turn-on dates.
And, now that we have a line, there's no joy.
In the 5.5 days since we got our service up, there are have been four downtimes, the first just a couple of minutes after I got everything working on our end. That first was 4 hours long; last night we were down for 3 hours. The two other downtimes were about a half hour each in length.
Total downtime: 8 hours out of ~132, or 6%. That I know of.
I was willing to put aside the first time downtime, saying that it might have been due to the recent MSSQL attack, but after three repeats ... it's starting to get pretty old and inexcusable.
Worse, whenever we have actual uptime, the quality of our line regularly varies between good and almost unusable. Our response time for our next-hop router varies from about 20ms, where it should be, up to 2s. Which is to say: 100x slower than it should be.
I'm going to swap some cables and move some machines around this weekend to bring my home setup into ExtremeDSL's "specs" (though they should be unecessary), but if these problems continue afterward, someone's going to get quite an earful over at ExtremeDSL, and will continue to on a daily basis till they start delivering the service they advertise. (And I should note that the downtimes are well and truly their problems; it's only the bad line quality that I need to investigate from my side first.)
This morning's line:
7377 packets transmitted, 7342 packets received, 0% packet loss
round-trip min/avg/max = 17.7/123.1/4228.0 ms
Slightly better than it has been, but still about 6x worse than it should be, on average, and flapping terribly.
Damn it.
Having to run a ping all the time, so that I can see if my line has gone done or just gotten dramatically slow when I stop being able to access remote sites I'm working on is getting very old.
The workout this morning was OK.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2003-01-30 02:13 pm (UTC)500 packets transmitted, 500 packets received, 0% packet loss
round-trip min/avg/max/stddev 19.514/24.443/474.912/24.062 ms
This wasn't to the host right upstream, but was to something fairly close (primary name server). The multi-second pings do seem a bit ... crappy. And that average isn't real impressive.
no subject
Date: 2003-01-30 03:06 pm (UTC)More importantly, I know what they should *feel* like and that doesn't include my connection not echoing commands I type in a remote shell for mini-eternities. Regularly.