Conversion from 3 Zettabits per second to Kilooctets per second

=

Invert

Formula to convert Zettabits per second (Zbit/s) to Kilooctets per second (ko/s)

More information

Zettabits per second to Kilooctets per second conversion table

Zettabits per second (Zbit/s)Kilooctets per second (ko/s)
1 Zettabit per second1.25 × 1017 ko/s
2 Zettabits per second2.5 × 1017 ko/s
3 Zettabits per second3.75 × 1017 ko/s
4 Zettabits per second5 × 1017 ko/s
5 Zettabits per second6.25 × 1017 ko/s
10 Zettabits per second1.25 × 1018 ko/s
20 Zettabits per second2.5 × 1018 ko/s
25 Zettabits per second3.125 × 1018 ko/s
50 Zettabits per second6.25 × 1018 ko/s
100 Zettabits per second1.25 × 1019 ko/s

Data-transfer rate reference points

ReferenceZettabits per second (Zbit/s)Kilooctets per second (ko/s)
A dial-up modem5.6 × 10-17 Zbit/s7 ko/s
Typical home broadband1 × 10-13 Zbit/s12500 ko/s
Gigabit Ethernet1 × 10-12 Zbit/s125000 ko/s
Streaming a 4K film2.5 × 10-14 Zbit/s3125 ko/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Zettabit per second (Zbit/s)

The zettabit per second is a unit of data transfer rate equal to a thousand exabits per second. Its symbol is Zbit/s. No system on Earth moves data at this rate, and none is planned; the unit exists because the metric system defines every prefix for every unit, whether or not the combination has yet been needed.

To see how far off it is, take the whole internet. Global traffic at present runs at roughly one exabit per second on average, so the entire planet's communications would have to grow a thousandfold to reach one zettabit per second. At the growth rates of the last two decades that would take somewhere between twenty and thirty years, which is precisely the sort of extrapolation that has been wrong in both directions before.

A zettabit per second is 125 exaoctets per second. Since global data storage manufacturing runs at a few hundred exaoctets a year, a link at this rate would transfer the world's entire annual production of new storage capacity in a couple of seconds. Nothing could be stored at the far end; the data would have to be processed and discarded as it arrived.

That last point is not as fanciful as it sounds. Several existing systems already discard almost everything they receive: particle detectors, radio telescope arrays and network monitoring systems all process far more than they keep, because keeping it is impossible and unnecessary. A zettabit-per-second link would be an extreme case of an architecture that already exists.

The physical obstacles are less absolute than they might appear. The theoretical capacity of a single optical fibre is far above what is used today, and the practical limits come from amplifier noise, non-linear effects and the electronics at each end rather than from the glass itself. Aggregating enough fibres would reach a zettabit per second; the difficulty is that nobody has a reason to.

For a converter, the unit matters because forecasts and capacity models are written in whatever unit keeps the numbers legible. A projection that reaches into the 2050s may reasonably state totals in zettabits per second, and a reader needs to be able to convert that into something familiar.

One zettabit per second equals 1,000 exabits per second, 125 exaoctets per second, or about 0.8470 zebibits per second.


Information about the Kilooctet per second (ko/s)

The kilooctet per second is a unit of data transfer rate equal to one thousand octets per second, and therefore to eight kilobits per second. Its symbol is ko/s. It is the unit in which file transfers were reported through the whole of the dial-up era, and it still appears whenever a transfer is slow enough to need it.

The conversion from advertised connection speeds is the reason it matters. A 56-kilobit modem delivered about 7 kilooctets per second in practice, and users learned the relationship by watching progress bars: a one-megaoctet file took about two and a half minutes. The habit of dividing the advertised number by eight and then subtracting a bit for overhead dates from that period.

Storage devices of the era were similar. A floppy disc drive read at roughly 30 to 60 kilooctets per second, a single-speed compact-disc drive at 150, and an early hard drive at a few hundred. Loading a program from any of them was a matter of seconds to minutes, and software was written with that expectation in mind.

The unit still appears in serial communication. The classic serial port ran at rates up to 115,200 bits per second, which is 14.4 kilooctets per second, and equivalent rates are still used to talk to microcontrollers, scientific instruments and industrial equipment. A protocol designed for such a link cannot assume that a large message will arrive quickly.

It also appears at the bottom end of modern networking. A congested mobile connection, a distant satellite link or a heavily shared wireless network can fall to a few tens of kilooctets per second, and at that rate an ordinary web page — which now runs to a few megaoctets — takes a minute or more to load. The unit is a reminder of what the network assumes about its users.

For scale, one kilooctet per second moves a thousand characters of plain text each second, so a short letter transfers in a second and a novel in about ten minutes. Nothing about text has ever needed more than this; every increase in transfer rate since has been consumed by images, sound and video.

One kilooctet per second equals 1,000 octets per second, 8 kilobits per second, or about 0.9766 kibioctets per second.