Conversion from 5 Yottabits per second to Kilooctets per second

=

Invert

Formula to convert Yottabits per second (Ybit/s) to Kilooctets per second (ko/s)

More information

Yottabits per second to Kilooctets per second conversion table

Yottabits per second (Ybit/s)Kilooctets per second (ko/s)
1 Yottabit per second1.25 × 1020 ko/s
2 Yottabits per second2.5 × 1020 ko/s
3 Yottabits per second3.75 × 1020 ko/s
4 Yottabits per second5 × 1020 ko/s
5 Yottabits per second6.25 × 1020 ko/s
10 Yottabits per second1.25 × 1021 ko/s
20 Yottabits per second2.5 × 1021 ko/s
25 Yottabits per second3.125 × 1021 ko/s
50 Yottabits per second6.25 × 1021 ko/s
100 Yottabits per second1.25 × 1022 ko/s

Data-transfer rate reference points

ReferenceYottabits per second (Ybit/s)Kilooctets per second (ko/s)
A dial-up modem5.6 × 10-20 Ybit/s7 ko/s
Typical home broadband1 × 10-16 Ybit/s12500 ko/s
Gigabit Ethernet1 × 10-15 Ybit/s125000 ko/s
Streaming a 4K film2.5 × 10-17 Ybit/s3125 ko/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Yottabit per second (Ybit/s)

The yottabit per second is a unit of data transfer rate equal to a thousand zettabits per second. Its symbol is Ybit/s. For thirty years it was the largest rate the metric system could name, and it describes a speed that has no application anywhere: not in engineering, not in research, and not in any forecast that anyone takes seriously.

Its distance from reality is easy to state. Global internet traffic averages roughly one exabit per second, so a yottabit per second is about a million times the combined communication of the entire human species. The largest single link ever built runs at a few hundred terabits per second, which is a ten-billionth of this figure.

The unit is nonetheless properly defined, and that completeness is the point. The metric system's rule is that every prefix combines with every unit without exception, so a reader who has never seen Ybit/s can decode it from the prefix alone. A system with gaps would need a table of which combinations are legal, and a table is exactly what a rule-based system exists to avoid.

There is a physical way to think about the number. A yottabit per second is 125 zettaoctets per second, and the total quantity of data humanity has ever stored is a few hundred zettaoctets. A link at this rate would therefore transmit the entire accumulated information of the species in a couple of seconds. No such body of data exists in one place to be sent, and nothing at the far end could receive it.

The prefix yotta was adopted in 1991 alongside zetta, at a conference that also had to consider which letters remained free. It stood at the top of the metric ladder until 2022, when ronna and quetta were added above it, partly because data quantities were beginning to approach the old ceiling. Rates have not followed quantities upward at the same pace.

For a converter, handling the unit is a matter of consistency rather than utility. A tool that converts every metric prefix correctly does not need to decide which of them anyone will use, and a figure written in yottabits per second — however unlikely — converts by the same rule as any other.

One yottabit per second equals 1,000 zettabits per second, 125 zettaoctets per second, or about 0.8272 yobibits 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.