Conversion from Yottabits per second to Octets per second

=

Invert

Formula to convert Yottabits per second (Ybit/s) to Octets per second (octet/s)

More information

Yottabits per second to Octets per second conversion table

Yottabits per second (Ybit/s)Octets per second (octet/s)
1 Yottabit per second1.25 × 1023 octet/s
2 Yottabits per second2.5 × 1023 octet/s
3 Yottabits per second3.75 × 1023 octet/s
4 Yottabits per second5 × 1023 octet/s
5 Yottabits per second6.25 × 1023 octet/s
10 Yottabits per second1.25 × 1024 octet/s
20 Yottabits per second2.5 × 1024 octet/s
25 Yottabits per second3.125 × 1024 octet/s
50 Yottabits per second6.25 × 1024 octet/s
100 Yottabits per second1.25 × 1025 octet/s

Data-transfer rate reference points

ReferenceYottabits per second (Ybit/s)Octets per second (octet/s)
A dial-up modem5.6 × 10-20 Ybit/s7000 octet/s
Typical home broadband1 × 10-16 Ybit/s12500000 octet/s
Gigabit Ethernet1 × 10-15 Ybit/s125000000 octet/s
Streaming a 4K film2.5 × 10-17 Ybit/s3125000 octet/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 Octet per second (octet/s)

The octet per second is a unit of data transfer rate equal to eight bits per second. Its symbol is octet/s. It is the unit in which software reports transfer speeds, as against the bits per second in which hardware and network services advertise them, and the factor of eight between the two conventions is the source of endless confusion.

The division of labour is consistent once it is understood. Anything describing a physical link — an Ethernet port, a fibre connection, a radio channel, a broadband package — is quoted in bits per second, because bits are what the signalling actually carries. Anything describing a file moving from one place to another is quoted in octets per second, because files are measured in octets.

A download manager that reports 12 megaoctets per second on a connection sold as 100 megabits per second is not disagreeing with the advertisement; it is stating the same rate in the other convention, and the arithmetic between them is a division by eight. Recognising this immediately removes the most common cause of complaint about internet speed.

Individual octets per second appear in the same narrow places as individual bits: deep-space telemetry, low-power sensor links, and the slowest legacy serial connections. A rate of a hundred octets per second would move a page of text in about twenty seconds, which was a normal experience in the 1970s and is unimaginable now.

The unit also underlies the way disc and interface throughput is described. A drive that sustains 500 megaoctets per second is moving four gigabits per second across its interface, and matching the two figures is a routine part of system design: an interface rated in gigabits must be compared with a drive rated in octets, and the factor of eight decides whether one starves the other.

Storage tools reinforce the convention. Every file copy utility, backup program and command-line transfer tool reports in octets per second or its multiples, and every network measurement tool reports in bits per second. A person reading both at once has to keep the conversion in mind, which is exactly what makes the distinction worth stating explicitly.

One octet per second equals 8 bits per second, 0.008 kilobits per second, or 0.001 kilooctets per second.