Conversion from 100 Yottabits per second to Bits per second

=

Invert

Formula to convert Yottabits per second (Ybit/s) to Bits per second (bit/s)

More information

Yottabits per second to Bits per second conversion table

Yottabits per second (Ybit/s)Bits per second (bit/s)
1 Yottabit per second1 × 1024 bit/s
2 Yottabits per second2 × 1024 bit/s
3 Yottabits per second3 × 1024 bit/s
4 Yottabits per second4 × 1024 bit/s
5 Yottabits per second5 × 1024 bit/s
10 Yottabits per second1 × 1025 bit/s
20 Yottabits per second2 × 1025 bit/s
25 Yottabits per second2.5 × 1025 bit/s
50 Yottabits per second5 × 1025 bit/s
100 Yottabits per second1 × 1026 bit/s

Data-transfer rate reference points

ReferenceYottabits per second (Ybit/s)Bits per second (bit/s)
A dial-up modem5.6 × 10-20 Ybit/s56000 bit/s
Typical home broadband1 × 10-16 Ybit/s100000000 bit/s
Gigabit Ethernet1 × 10-15 Ybit/s1 × 109 bit/s
Streaming a 4K film2.5 × 10-17 Ybit/s25000000 bit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

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


Information about the Bit per second (bit/s)

The bit per second is the fundamental unit of data transfer rate. Its symbol is bit/s, often written bps. It counts how many binary decisions a channel carries in one second, and every other unit of transmission speed is a multiple of it.

Because it is a rate, it has the form of a quantity divided by time, exactly like metres per second or litres per second. That makes the arithmetic straightforward: a link running at a given number of bits per second, multiplied by a duration in seconds, gives the total number of bits transferred, and dividing by eight converts that to octets.

The unit must be distinguished from the baud, which counts symbols per second rather than bits. Early modems transmitted one bit per symbol, so the two numbers were the same and the words were used interchangeably. Modern schemes encode several bits in each symbol — by varying phase and amplitude together — so a channel running at 3,000 baud may carry 33,600 bits per second. Only the bit rate describes how much information moves.

Claude Shannon established the theoretical ceiling in 1948. The capacity of a channel in bits per second depends on its bandwidth and on the ratio of signal to noise, and no coding scheme can exceed it. Every advance in modem and radio design since has been an attempt to approach that limit more closely, and modern systems come within a fraction of a decibel of it.

In practice the raw bit rate of a link is never the rate at which useful data arrives. Protocol headers, error-correcting codes, acknowledgements and retransmissions all consume capacity, and the usable fraction is typically 90 to 95 per cent on a wired link and considerably less on a shared wireless one.

Single bits per second are rarely quoted, because almost every channel is faster. The exceptions are deep-space communication, where a probe billions of kilometres away may return data at a few tens of bits per second, and certain low-power sensor networks that transmit a handful of bits at long intervals to preserve battery life.

One bit per second equals 0.125 octets per second, 0.001 kilobits per second, or about 0.0009766 kibibits per second.