| Exbioctets per second (Eio/s) | Yottabits per second (Ybit/s) |
|---|---|
| 1 Exbioctet per second | 0.00000922337203685 Ybit/s |
| 2 Exbioctets per second | 0.0000184467440737 Ybit/s |
| 3 Exbioctets per second | 0.0000276701161106 Ybit/s |
| 4 Exbioctets per second | 0.0000368934881474 Ybit/s |
| 5 Exbioctets per second | 0.0000461168601843 Ybit/s |
| 10 Exbioctets per second | 0.0000922337203685 Ybit/s |
| 20 Exbioctets per second | 0.000184467440737 Ybit/s |
| 25 Exbioctets per second | 0.000230584300921 Ybit/s |
| 50 Exbioctets per second | 0.000461168601843 Ybit/s |
| 100 Exbioctets per second | 0.000922337203685 Ybit/s |
| Reference | Exbioctets per second (Eio/s) | Yottabits per second (Ybit/s) |
|---|---|---|
| A dial-up modem | 6.07153 × 10-15 Eio/s | 5.6 × 10-20 Ybit/s |
| Typical home broadband | 1.0842 × 10-11 Eio/s | 1 × 10-16 Ybit/s |
| Gigabit Ethernet | 1.0842 × 10-10 Eio/s | 1 × 10-15 Ybit/s |
| Streaming a 4K film | 2.71051 × 10-12 Eio/s | 2.5 × 10-17 Ybit/s |
The exbioctet per second is a unit of data transfer rate equal to 1,024 pebioctets per second, or two to the sixtieth power octets per second. Its symbol is Eio/s. It is the binary counterpart of the exaoctet per second, and the two differ by 15.3 per cent.
No machine, network or aggregate reaches this rate. An exbioctet per second is more than eight times the total instantaneous traffic of the entire internet, and it would move the world's whole stock of stored data in a matter of minutes. The unit describes a capacity with no source that could supply it and no destination that could take it in.
Two to the sixtieth is nevertheless a familiar number in computing, because it is the size of the address space a 64-bit machine can reach in octets divided by sixteen. The same power of two turns up in filesystem limits, in memory maps and in the design of every system built on that architecture, so the quantity is well known even though no rate approaches it.
The unit exists because the IEC series was defined completely. Every binary prefix pairs with every unit, exactly as every metric prefix does, so that a reader who has never seen Eio/s can decode it from the prefix alone. A system with gaps would need a table of permitted combinations, which is precisely what a rule-based system exists to avoid.
The difference from the decimal unit is worth restating at each level because it compounds. At the kibioctet it was 2.4 per cent, here it is more than an eighth, and at the yobioctet it will be more than a fifth. That growth is the reason the binary prefixes were created, and it is why the lowercase i has to be written even in figures nobody will check.
For a converter, the treatment is mechanical: six multiplications by 1,024 from octets, or the equivalent divisions coming down. The value of doing it correctly is not that anyone will use the result, but that a tool which handles every case the same way can be trusted on the cases that matter.
One exbioctet per second equals 1,024 pebioctets per second, 1,152,921,504,606,846,976 octets per second, or about 1.153 exaoctets per second.
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.