Conversion from 25 Zettabits per second to Kibibits per second

=

Invert

Formula to convert Zettabits per second (Zbit/s) to Kibibits per second (Kibit/s)

More information

Zettabits per second to Kibibits per second conversion table

Zettabits per second (Zbit/s)Kibibits per second (Kibit/s)
1 Zettabit per second9.765625 × 1017 Kibit/s
2 Zettabits per second1.953125 × 1018 Kibit/s
3 Zettabits per second2.9296875 × 1018 Kibit/s
4 Zettabits per second3.90625 × 1018 Kibit/s
5 Zettabits per second4.8828125 × 1018 Kibit/s
10 Zettabits per second9.765625 × 1018 Kibit/s
20 Zettabits per second1.953125 × 1019 Kibit/s
25 Zettabits per second2.44140625 × 1019 Kibit/s
50 Zettabits per second4.8828125 × 1019 Kibit/s
100 Zettabits per second9.765625 × 1019 Kibit/s

Data-transfer rate reference points

ReferenceZettabits per second (Zbit/s)Kibibits per second (Kibit/s)
A dial-up modem5.6 × 10-17 Zbit/s54.6875 Kibit/s
Typical home broadband1 × 10-13 Zbit/s97656.2 Kibit/s
Gigabit Ethernet1 × 10-12 Zbit/s976562 Kibit/s
Streaming a 4K film2.5 × 10-14 Zbit/s24414.1 Kibit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Zettabit per second (Zbit/s)

The zettabit per second is a unit of data transfer rate equal to a thousand exabits per second. Its symbol is Zbit/s. No system on Earth moves data at this rate, and none is planned; the unit exists because the metric system defines every prefix for every unit, whether or not the combination has yet been needed.

To see how far off it is, take the whole internet. Global traffic at present runs at roughly one exabit per second on average, so the entire planet's communications would have to grow a thousandfold to reach one zettabit per second. At the growth rates of the last two decades that would take somewhere between twenty and thirty years, which is precisely the sort of extrapolation that has been wrong in both directions before.

A zettabit per second is 125 exaoctets per second. Since global data storage manufacturing runs at a few hundred exaoctets a year, a link at this rate would transfer the world's entire annual production of new storage capacity in a couple of seconds. Nothing could be stored at the far end; the data would have to be processed and discarded as it arrived.

That last point is not as fanciful as it sounds. Several existing systems already discard almost everything they receive: particle detectors, radio telescope arrays and network monitoring systems all process far more than they keep, because keeping it is impossible and unnecessary. A zettabit-per-second link would be an extreme case of an architecture that already exists.

The physical obstacles are less absolute than they might appear. The theoretical capacity of a single optical fibre is far above what is used today, and the practical limits come from amplifier noise, non-linear effects and the electronics at each end rather than from the glass itself. Aggregating enough fibres would reach a zettabit per second; the difficulty is that nobody has a reason to.

For a converter, the unit matters because forecasts and capacity models are written in whatever unit keeps the numbers legible. A projection that reaches into the 2050s may reasonably state totals in zettabits per second, and a reader needs to be able to convert that into something familiar.

One zettabit per second equals 1,000 exabits per second, 125 exaoctets per second, or about 0.8470 zebibits per second.


Information about the Kibibit per second (Kibit/s)

The kibibit per second is a unit of data transfer rate equal to 1,024 bits per second. Its symbol is Kibit/s. It is the binary counterpart of the kilobit per second, and it is the least used member of an already unusual family, because transfer rates are one of the few places in computing where the decimal convention has always been unambiguous.

Networking has counted in true thousands from the beginning. A modem rated at 56 kilobits per second meant fifty-six thousand, not fifty-seven thousand three hundred and forty-four. The reason is that a transmission rate is set by a clock, and clocks are specified in decimal frequencies: a link running at ten million symbols per second carries a decimal number of bits, not a power of two.

The binary prefixes exist for quantities, not for rates, because quantities of storage are organised in powers of two while time is not. There is no natural reason for a rate to be a power of two, and consequently no reason for a rate unit to need a binary prefix. Where one appears, it is almost always because a program divided a binary file size by a duration.

That is exactly where the kibibit per second does turn up. A tool that measures a transfer by counting kibioctets and dividing by seconds produces a rate in kibioctets per second, and multiplying by eight gives kibibits per second. The unit is a consequence of the arithmetic rather than a description of the channel.

For scale, a kibibit per second is 128 octets per second, and the difference from a kilobit per second is 2.4 per cent — smaller than the measurement error of almost any real throughput test. At this level the distinction is technically correct and practically invisible, which is a fair description of the whole binary prefix system at its lower end.

The unit is properly defined and a converter must handle it, because the IEC series applies to every unit without exception. Whether anyone writes it is a separate question from whether it means something definite, and it does.

One kibibit per second equals 1,024 bits per second, 128 octets per second, or 1.024 kilobits per second.