Conversion from 2 Zettabits per second to Mebibits per second

=

Invert

Formula to convert Zettabits per second (Zbit/s) to Mebibits per second (Mibit/s)

More information

Zettabits per second to Mebibits per second conversion table

Zettabits per second (Zbit/s)Mebibits per second (Mibit/s)
1 Zettabit per second953674316406250 Mibit/s
2 Zettabits per second1.90734863281 × 1015 Mibit/s
3 Zettabits per second2.86102294922 × 1015 Mibit/s
4 Zettabits per second3.81469726562 × 1015 Mibit/s
5 Zettabits per second4.76837158203 × 1015 Mibit/s
10 Zettabits per second9.53674316406 × 1015 Mibit/s
20 Zettabits per second1.90734863281 × 1016 Mibit/s
25 Zettabits per second2.38418579102 × 1016 Mibit/s
50 Zettabits per second4.76837158203 × 1016 Mibit/s
100 Zettabits per second9.53674316406 × 1016 Mibit/s

Data-transfer rate reference points

ReferenceZettabits per second (Zbit/s)Mebibits per second (Mibit/s)
A dial-up modem5.6 × 10-17 Zbit/s0.0534058 Mibit/s
Typical home broadband1 × 10-13 Zbit/s95.3674 Mibit/s
Gigabit Ethernet1 × 10-12 Zbit/s953.674 Mibit/s
Streaming a 4K film2.5 × 10-14 Zbit/s23.8419 Mibit/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 Mebibit per second (Mibit/s)

The mebibit per second is a unit of data transfer rate equal to 1,048,576 bits per second. Its symbol is Mibit/s. It is the binary counterpart of the megabit per second, and the two differ by 4.9 per cent — small, but large enough to change a headline figure.

That five per cent is where the unit starts to matter. A connection advertised at 100 megabits per second and a connection at 100 mebibits per second differ by about five megabits, which is a whole high-definition video stream. In a specification, a contract or a benchmark report, quoting one and delivering the other is a real discrepancy rather than a rounding difference.

In practice the confusion is rare in networking, because network equipment is always specified in decimal. What produces mebibit figures is measurement software: a tool that counts a transfer in mebioctets and divides by elapsed seconds is reporting a binary rate, and multiplying by eight makes it mebibits per second. A person comparing that reading with an advertised rate must convert twice, once for the base and once for the factor of eight.

Where a genuine binary rate does arise is inside a machine. A memory bus transfers a fixed number of bits per clock cycle, and the width is a power of two — sixty-four bits at a time, for instance — so the quantity moved per cycle is binary even though the clock frequency is not. Rates derived from such a structure are naturally expressed with binary prefixes.

For scale, a mebibit per second is 131,072 octets per second, or about 128 kibioctets per second. That is roughly a photograph every two seconds, or a plain-text novel every four. It is a rate at which the modern web is slow but usable, which puts it in the range that mobile networks fall to when congested.

The correct symbol has the lowercase i, and its presence is the only reliable way to tell the two conventions apart. A document writing Mbit/s in a context where the underlying figure came from a binary computation has misstated its own measurement by five per cent.

One mebibit per second equals 1,048,576 bits per second, 131,072 octets per second, or about 1.049 megabits per second.