| Yottabits per second (Ybit/s) | Kibibits per second (Kibit/s) |
|---|---|
| 1 Yottabit per second | 9.765625 × 1020 Kibit/s |
| 2 Yottabits per second | 1.953125 × 1021 Kibit/s |
| 3 Yottabits per second | 2.9296875 × 1021 Kibit/s |
| 4 Yottabits per second | 3.90625 × 1021 Kibit/s |
| 5 Yottabits per second | 4.8828125 × 1021 Kibit/s |
| 10 Yottabits per second | 9.765625 × 1021 Kibit/s |
| 20 Yottabits per second | 1.953125 × 1022 Kibit/s |
| 25 Yottabits per second | 2.44140625 × 1022 Kibit/s |
| 50 Yottabits per second | 4.8828125 × 1022 Kibit/s |
| 100 Yottabits per second | 9.765625 × 1022 Kibit/s |
| Reference | Yottabits per second (Ybit/s) | Kibibits per second (Kibit/s) |
|---|---|---|
| A dial-up modem | 5.6 × 10-20 Ybit/s | 54.6875 Kibit/s |
| Typical home broadband | 1 × 10-16 Ybit/s | 97656.2 Kibit/s |
| Gigabit Ethernet | 1 × 10-15 Ybit/s | 976562 Kibit/s |
| Streaming a 4K film | 2.5 × 10-17 Ybit/s | 24414.1 Kibit/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.
The kibibit per second is a unit of data transfer rate equal to 1,024 bits per second. Its symbol is Kibit/s. It is the binary counterpart of the kilobit per second, and it is the least used member of an already unusual family, because transfer rates are one of the few places in computing where the decimal convention has always been unambiguous.
Networking has counted in true thousands from the beginning. A modem rated at 56 kilobits per second meant fifty-six thousand, not fifty-seven thousand three hundred and forty-four. The reason is that a transmission rate is set by a clock, and clocks are specified in decimal frequencies: a link running at ten million symbols per second carries a decimal number of bits, not a power of two.
The binary prefixes exist for quantities, not for rates, because quantities of storage are organised in powers of two while time is not. There is no natural reason for a rate to be a power of two, and consequently no reason for a rate unit to need a binary prefix. Where one appears, it is almost always because a program divided a binary file size by a duration.
That is exactly where the kibibit per second does turn up. A tool that measures a transfer by counting kibioctets and dividing by seconds produces a rate in kibioctets per second, and multiplying by eight gives kibibits per second. The unit is a consequence of the arithmetic rather than a description of the channel.
For scale, a kibibit per second is 128 octets per second, and the difference from a kilobit per second is 2.4 per cent — smaller than the measurement error of almost any real throughput test. At this level the distinction is technically correct and practically invisible, which is a fair description of the whole binary prefix system at its lower end.
The unit is properly defined and a converter must handle it, because the IEC series applies to every unit without exception. Whether anyone writes it is a separate question from whether it means something definite, and it does.
One kibibit per second equals 1,024 bits per second, 128 octets per second, or 1.024 kilobits per second.