| Terabits per second (Tbit/s) | Yottabits per second (Ybit/s) |
|---|---|
| 1 Terabit per second | 1 × 10-12 Ybit/s |
| 2 Terabits per second | 2 × 10-12 Ybit/s |
| 3 Terabits per second | 3 × 10-12 Ybit/s |
| 4 Terabits per second | 4 × 10-12 Ybit/s |
| 5 Terabits per second | 5 × 10-12 Ybit/s |
| 10 Terabits per second | 1 × 10-11 Ybit/s |
| 20 Terabits per second | 2 × 10-11 Ybit/s |
| 25 Terabits per second | 2.5 × 10-11 Ybit/s |
| 50 Terabits per second | 5 × 10-11 Ybit/s |
| 100 Terabits per second | 1 × 10-10 Ybit/s |
| Reference | Terabits per second (Tbit/s) | Yottabits per second (Ybit/s) |
|---|---|---|
| A dial-up modem | 0.000000056 Tbit/s | 5.6 × 10-20 Ybit/s |
| Typical home broadband | 0.0001 Tbit/s | 1 × 10-16 Ybit/s |
| Gigabit Ethernet | 0.001 Tbit/s | 1 × 10-15 Ybit/s |
| Streaming a 4K film | 0.000025 Tbit/s | 2.5 × 10-17 Ybit/s |
The terabit per second is a unit of data transfer rate equal to a thousand gigabits per second. Its symbol is Tbit/s. It is the unit of the internet's backbone: the submarine cables, the exchange points and the long-haul optical links that carry traffic between continents.
A single modern transoceanic cable carries several hundred terabits per second. It achieves this not with one enormous channel but with wavelength division multiplexing, which sends dozens of separate colours of light down each fibre at once, and with several fibre pairs in the same cable. Each wavelength carries a few hundred gigabits, and the totals add up.
The historical comparison is worth stating plainly. The first transatlantic telephone cable, laid in 1956, carried thirty-six simultaneous voice calls. A cable laid in the 2020s carries hundreds of terabits per second, enough for hundreds of millions of simultaneous calls. That is a factor of roughly ten million in seventy years, and it was achieved almost entirely by changing what is sent down the glass rather than by laying more cable.
Internet exchange points, where networks meet and hand traffic to one another, publish their throughput in terabits per second. The largest in Europe and Asia peak in the tens of terabits, and those public graphs are among the most reliable measurements of how heavily the internet is being used at a given moment, because they count real traffic rather than capacity.
In octets, a terabit per second is 125 gigaoctets per second — the contents of a large laptop's disc moved every second, continuously. No single storage system can feed such a link; the traffic on these routes is the aggregate of millions of separate connections, each of them tiny by comparison.
Laboratory records go far higher, into petabits per second, using multi-core fibre and hundreds of wavelengths at once, though over short distances under controlled conditions. The gap between what is demonstrated in a laboratory and what is deployed under an ocean has historically been about a decade.
One terabit per second equals 1,000 gigabits per second, 125 gigaoctets per second, or about 0.9095 tebibits 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.