Conversion from 100 Terabits per second to Exaoctets per second

=

Invert

Formula to convert Terabits per second (Tbit/s) to Exaoctets per second (Eo/s)

More information

Terabits per second to Exaoctets per second conversion table

Terabits per second (Tbit/s)Exaoctets per second (Eo/s)
1 Terabit per second0.000000125 Eo/s
2 Terabits per second0.00000025 Eo/s
3 Terabits per second0.000000375 Eo/s
4 Terabits per second0.0000005 Eo/s
5 Terabits per second0.000000625 Eo/s
10 Terabits per second0.00000125 Eo/s
20 Terabits per second0.0000025 Eo/s
25 Terabits per second0.000003125 Eo/s
50 Terabits per second0.00000625 Eo/s
100 Terabits per second0.0000125 Eo/s

Data-transfer rate reference points

ReferenceTerabits per second (Tbit/s)Exaoctets per second (Eo/s)
A dial-up modem0.000000056 Tbit/s7 × 10-15 Eo/s
Typical home broadband0.0001 Tbit/s1.25 × 10-11 Eo/s
Gigabit Ethernet0.001 Tbit/s1.25 × 10-10 Eo/s
Streaming a 4K film0.000025 Tbit/s3.125 × 10-12 Eo/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Terabit per second (Tbit/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.


Information about the Exaoctet per second (Eo/s)

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.