- DSL Reports, also great
if you want to check your throughput speed. Needs java installed
in your browser.
- Bell Atlantic. Used to give static IP. Not linux friendly, but check out
links. Supposedly rp-pppoe is
- speakeasy, linux friendly
- PatriotNet (linux, but a bit pricey?)
- Atlantech.net (www.atlantech.net or www.serveranswer.com)
- DNS services:
BellSouth survival guide, plus lots of useful links
I typically get (the only one on the block) around 300kB/s download,
upload of course restricted to 128k, or about 14kB/s. However, after
January 22, @home was converted to comcast, and now we're well below
100 kB/s, and during the "hot" hours probably more like 25 often.... :-(
My own speed tests (aug/sep 2001)
- NEW: 22 jan - feb 7 event list, shows how
cable has progressively dropped speed, including some really bad days
where the speed dropped to the 20s... Note the stability of DSL
(all the dropouts are strongly correlated with my downloads)
- NEW: 22-30 jan: note the bad
drops on Jan 27 and Jan 28.... down to the 20s
- NEW: (23-jan-2002) Cable/DSL comparison
before and after the Comcast transition. See also the
daily variations (22-27 jan 2002) as well as
weekly variations (22-27 jan 2002).
- raw index of files
- cable speed histogram,
and plotted as function of time(event).
If you are wondering if the dropdown in speed is due to me,
it's mostly not, judging from
correlating average locally induced traffic with the bulk speed
of the test file.
- dsl speed histogram,
and plotted as function of time(event)
- event vs. speed density map:
scale is from 0 (bottom) to 400 kB/s (top). DSL is at around
63 kB/s bottom right, modem is around 300, but a strong secondary
peak around 240 is appearing since recently.
- shell script with which this was measured
This should be in comcast's FAQ
comcast sometimes goes for a bit",
and this happened to me on a monday i think, and some more
intermittent slowness that week. A few nights later I could not get
(comcast) email, and this evening it was totally frazzled, very very
eventually I broke down and called them. spent well over an hour with them.
not solve it. Even switched computers, rebooted them (and they were
not dismissive of linux!!!). But only one fatal mistake the tech guy
didn't catch. So here's the thing to know:
if you leave your modem on all the time, you keep the same IP (dhcp).
However, if you do have longer dropouts (and they do occur), it's quite possible
that you have - from the modem point of view - lost the IP. but linux
doesn't know that.... so i must have been using an IP that somebody
else was also using.
Solution: take true power off the cable for about 30 or so secs. I did that,
but was using the green 'power' button (even saying to the tech as i was
doing it). As i turned it on a little later i commented that the lights
came back the same way as they were before, instead of the usual
orange/green flickers that you get during a power cycle.... That was
the thing he missed: he should have let me take the power cable off,
the button isn't really power..... Lesson learned! Cost me about 3
hours this evening. what a waste.