| Yottabits per second (Ybit/s) | Exaoctets per second (Eo/s) |
|---|---|
| 1 Yottabit per second | 125000 Eo/s |
| 2 Yottabits per second | 250000 Eo/s |
| 3 Yottabits per second | 375000 Eo/s |
| 4 Yottabits per second | 500000 Eo/s |
| 5 Yottabits per second | 625000 Eo/s |
| 10 Yottabits per second | 1250000 Eo/s |
| 20 Yottabits per second | 2500000 Eo/s |
| 25 Yottabits per second | 3125000 Eo/s |
| 50 Yottabits per second | 6250000 Eo/s |
| 100 Yottabits per second | 12500000 Eo/s |
| Reference | Yottabits per second (Ybit/s) | Exaoctets per second (Eo/s) |
|---|---|---|
| A dial-up modem | 5.6 × 10-20 Ybit/s | 7 × 10-15 Eo/s |
| Typical home broadband | 1 × 10-16 Ybit/s | 1.25 × 10-11 Eo/s |
| Gigabit Ethernet | 1 × 10-15 Ybit/s | 1.25 × 10-10 Eo/s |
| Streaming a 4K film | 2.5 × 10-17 Ybit/s | 3.125 × 10-12 Eo/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 exaoctet per second is a unit of data transfer rate equal to a thousand petaoctets per second, or eight exabits per second. Its symbol is Eo/s. Nothing built runs at this rate: it is about eight times the total traffic of the entire internet, counted across every network on the planet at once.
The unit is useful mainly for thought experiments about limits. If every hard drive and flash chip manufactured in a year were read simultaneously at full speed, the combined rate would be in this range. So would the total output of every camera sensor in every phone on Earth if they all recorded at once. These are sums over the whole world's hardware, not rates any system experiences.
There is one situation in which very large data volumes really do move faster than any network, and it puts the unit in perspective. Physically shipping a container of hard drives across an ocean transfers more data per second, averaged over the journey, than any cable. A shipping container holding a few exaoctets crossing the Atlantic in a week works out to several gigaoctets per second, and a truck of drives driven across a city beats almost any local link.
That calculation is not a joke; cloud providers offer it as a service. When a customer needs to move petaoctets into a data centre, the provider ships a lorry full of storage rather than attempting the transfer over a network, because the network would take months. The bandwidth of a vehicle is enormous, though its latency is measured in days.
For the unit itself, an exaoctet per second is 125 petaoctets per second, and it would transfer the world's entire stock of stored data — a few hundred zettaoctets — in about a week of continuous running. No mechanism exists to feed such a link, and none is being designed.
A converter must nevertheless handle the unit, because it appears in aggregate capacity models, in academic papers on the theoretical limits of communication, and in any table that lists the metric prefixes completely. A quantity does not need a use for its name to be well formed.
One exaoctet per second equals 1,000 petaoctets per second, 8 exabits per second, or about 0.8674 exbioctets per second.