Mebibit to Exabit

A megabit (Mb) = 1,000,000 bits (SI decimal). A mebibit (Mibit) = 1,048,576 bits (IEC binary = 2²⁰ bits). The mebibit is 4.857% larger. Network speeds use megabits (Mb); embedded memory and flash storage specifications use mebibits when binary precision is required.

Mebibit appears primarily in microcontroller and microprocessor datasheets (e.g. "2 Mibit flash memory"), FPGA configuration file sizes, and some wireless protocol standards (802.11 frame size limits, Bluetooth payload specifications). It is rarely seen in consumer-facing applications but is common in embedded systems engineering documentation.

Yes. In 2007, a class-action settlement required Western Digital to pay $2.1 million because their hard drives advertised capacity in decimal megabits/gigabits while operating systems reported binary values — making drives appear ~7% smaller than labeled. Similar suits hit Seagate and Samsung. These lawsuits accelerated industry adoption of IEC prefixes and pushed Apple (2009) and later Windows (2021) to clarify their capacity labeling.

SPI flash chips are addressed at the bit level during serial communication — the programr shifts data in one bit at a time over the SPI bus. Datasheets specify capacity in mebibits (e.g. W25Q16 = 16 Mibit = 2 MiB) because the serial interface operates on bits, not bytes. Calculating transfer time requires bit-level math: reading a full 16 Mibit chip at 80 MHz SPI clock takes about 0.2 seconds.

Flash memory chips organise storage in binary-aligned blocks (sectors, pages) whose sizes are powers of 2. Specifying capacity in mebibits (1,048,576 bits per Mibit) maps precisely to the physical organisation of the memory array. Using decimal megabits would result in non-integer block counts, making datasheet specifications harder to verify against hardware design.

One exabit = 10¹⁸ bits = 125,000 terabytes = 125 petabytes. If every person on Earth (8 billion people) each stored 15 GB of data — roughly a modern smartphone's photos and messages — the total would be about 120 exabytes, or about 960 exabits. The entire human genome is about 1.5 GB; sequencing every person on Earth would produce about 12 exabytes of data.

Cisco's annual internet traffic reports estimated global IP traffic at roughly 4.8 exabytes per day in 2022, rising about 20% per year. Expressed in bits, that's about 38 exabits per day or roughly 440 petabits per second continuously. Video streaming accounts for over 60% of total internet traffic volume.

Data gravity is the principle that massive datasets attract applications, services, and additional data toward them — rather than being moved to where processing occurs. At exabit scale, physically transferring data becomes impractical: moving 1 exabit over a 100 Gbps link takes 116 days. Instead, companies deploy compute resources alongside the data. This effect drives cloud concentration — once an organisation stores exabits in AWS or Azure, the cost and latency of moving that data elsewhere creates powerful vendor lock-in, shaping the economics of the entire cloud industry.

The Square Kilometer Array (SKA), under construction in Australia and South Africa, will be the world's largest radio telescope. Its thousands of antennas will collectively produce roughly 1 exabit of raw sensor data per day — more than the entire global internet traffic of the early 2000s. This data cannot be stored in full; instead, on-site supercomputers reduce it by a factor of ~10,000 in real time, keeping only scientifically relevant signals. The SKA illustrates how radio astronomy pushes data processing to extreme scales that rival commercial internet infrastructure.

At 1 Gbps (a fast home connection), downloading 1 exabit would take 1 billion seconds — about 31.7 years. At 1 Tbps (a high-end data center link), it would take 1 million seconds, or about 11.6 days. This illustrates why exabit-scale data movements require massively parallel infrastructure — no single link or device handles exabit transfers directly.