Nope, that would be considered crazy fast back in the day, it was 56 kilobits per second. That's about 6.8 kilobytes, but realistically and with overhead it was usually around 5KB/s.
Nope, that would be considered crazy fast back in the day, it was 56 kilobits per second. That's about 6.8 kilobytes, but realistically and with overhead it was usually around 5KB/s.
33.6 kbit/s (a later addition)
31.2 kbit/s (a later addition)
28.8 kbit/s (the theoretical maximum for most people; I remember being jealous of people who actually got it)
26.4 kbit/s (what my internet usually hit in practice)
24.0 kbit/s (I remember seeing this)
21.6 kbit/s (apparently this was very common, though I don't remember seeing it)
19.2 kbit/s
16.8 kbit/s
14.4 kbit/s (quite possible)
(lower bitrates are also documented; this is all multiples of 2.4 kbit/s)
Also, remember to assume about 10 bits per byte of actual data, since there is various protocol overhead.For completeness, 33.6 required insane levels of signal clarity on the phone line, and was mostly fiction outside of urban and dense suburban areas.
Prior to 14.4k, there were other generations of modems that came before: 9600, 2400, and even 300 baud modems were all you could get in their respective eras. Each of which were cutting edge at the time.
56K (also called V.90 or "V.everything"), leaned into the quantization that happens on digital phone trunks, rather than let the analog-to-digital conversion chew up your analog modem waveforms. The trick here is that the psuedo-digital-over-analog leg from your house to the local exchange was limited by a few miles. Try this from too far out of town, and it just doesn't work. And to be clear, this was prior to DSL, which is similar but a completely different beast.
Oh, and the V.90 spec was a compromise between two competing 56K standards at the time: K56Flex and X2. This meant that ISPs needed to have matching modems on their end to handle the special 56K signaling. Miraculously, the hardware vendors did something that was good for everyone and compromised on a single standard, and then pushed firmware patches that allowed the two brands to interoperate on existing hardware.
Also, line conditions were subject to a range of factors. It's all copper wire hung from power-poles after all. So, poor quality materials, sloppy workmanship, and aging infrastructure would introduce noise all by itself, and even during weather events. This meant that, for some, it was either a good day or a bad day to try to dial into the internet.
Of course we're talking terminal, BBS, and Compuserve users here. AOL was probably grief at those speeds.
"56k" modems hit the scene (at affordable prices) in ~1998 and 3.2-4.1KB/s were pretty normal. People in high school who "only" had a 28.8 modem were considered dinosaurs by then. We didn't get DSL until ~mid 2000 IIRC
It did depend on line quality, though. We had some kinds of splitters and internal cabling in the house for allowing multiple phones (and eventually the modem), and I remember that prior to some changes made to that, I only used to get up to ~40k.
I remember being amazed to see download resume right in the browser even as late as 2009 (I was only on dial up u til about 2006).
(It might also have been slow early DSL. I'm not sure when exactly this was or when the transition happened.)
Between that and the time I discovered "DISPLAY=<my IP>:0 xdm" worked from our shell account I'm surprised we weren't kicked off the ISP.
Then I went to install it and the ISO was corrupted. I never got to try Debian until I joined the Air Force and downloaded it at work.
I got DSL a few weeks later.
I had a friend with a 56K ISDN line (data over voice channel) and it was much better performance (10's of milliseconds.)
Worthwhile to also mention that ISDN was full duplex, instead of half-duplex like dialup. The modems on either end would need to time-slice to allow bi-directional communication, which in a TCP laden world like the web meant that every interaction was orders of magnitude more latent than on ISDN, in which you had symmetrical, full-duplex 56k of bandwidth between you and the ISDN modem. That's the biggest reason why you had a significant decrease in latency.
Fortunately, I got cable internet around 1997 and never looked back.
My "favorite" thing when working tech support was explaining to people in expensive new subdivisions that Southwest Bell saved money by deploying pair gains instead of running more copper, and that's why they were never, ever going to see more than 33.6 (if very lucky) or 28.8 (more likely).
A common trick was to get them to add 3 commas to their dial string. That would prevent their modem from starting to train up until 3 seconds after they finished dialing. That would give our modems time to answer and start the 56K initiation. The delay would cause them to miss that, and then start trying to train up a much more stable 33.6 connection. It capped their max speed but made their connection a lot more reliable.
Later on, there were modems that required a CPU with MMX instructions. Dealt with that a lot when I ran my short-lived computer shop.
I made it a policy in '97 to only buy external modems.
They never did figure out where all their bandwidth was going, although the boarding house festooned with cat4 was suspicious. They came and snipped some more conspicuous cables, which were of course immediately spliced back together.
They tried to shut the internet down overnight in response, but their DNS level block was a mere roadbump, and in the end they got another ISDN line… which was immediately put to use in the downstairs kitchen VCD factory. Put the Hong Kong kids out of business, as with them you’d have to wait until next term, with us you got your warez tomorrow, with a fried breakfast.