Terabit to Mebibyte

One terabit per second (Tbps) equals 125 gigabytes per second — enough to transfer the entire contents of a 1 TB hard drive in about 8 seconds. At this speed, you could download the entire Netflix library (estimated at around 100 petabytes) in roughly 800,000 seconds, or about 9 days.

Submarine fiber optic cables (such as the transatlantic cables connecting Europe and the Americas), long-haul terrestrial fiber routes, and the internal switching fabric of the largest hyperscale cloud data centers (Google, Amazon, Microsoft) operate at terabit and multi-terabit speeds. These use wavelength-division multiplexing (WDM) to carry many 100 Gbps or 400 Gbps channels on a single fiber.

Not in the foreseeable future for a single household connection. Current consumer endpoints (laptops, phones, TVs) cannot process or use data at terabit speeds — Wi-Fi 7 tops out around 46 Gbps theoretically. Terabit access would require new hardware at every endpoint. The practical benefit would be minimal since content servers themselves are not yet able to deliver at terabit rates to a single user.

Global internet traffic is measured in exabytes per month. Estimates suggest the internet backbone carries over 1,000 Tbps (1 Pbps) in aggregate during peak hours. Major internet exchange points (IXPs) like DE-CIX in Frankfurt regularly see peak traffic above 10 Tbps, and the largest cloud providers' internal networks operate at multi-petabit scales.

Current 5G mmWave cells can deliver up to 10–20 Gbps aggregate capacity shared among users in a sector. Industry roadmaps for 6G (targeted around 2030) aim for 1 Tbps aggregate throughput per cell site using sub-terahertz frequencies (100–300 GHz), massive MIMO antenna arrays, and intelligent reflecting surfaces. Achieving terabit wireless capacity requires extremely dense small-cell deployments — potentially one access point every 50–100 meters in urban areas.

MB (megabyte) = 1,000,000 bytes (SI decimal). MiB (mebibyte) = 1,048,576 bytes (IEC binary). MiB is 4.86% larger. This gap is why a file manager on Linux showing "512 MiB" of free RAM and a marketing sheet showing "512 MB" of RAM are technically different: the marketing sheet refers to fewer bytes.

The original CD-ROM standard defined capacity as 74 minutes of audio or 650,000,000 bytes. Technically this is 650 MB in SI terms, or approximately 620 MiB (since 650,000,000 ÷ 1,048,576 ≈ 620). However, the CD industry loosely used "MB" to mean 650 × 10⁶ bytes. Some media used 700 MB (≈ 668 MiB). This inconsistency is a classic example of the pre-IEC ambiguity.

Docker reports image sizes in decimal MB (e.g., "docker images" shows 150 MB), but the underlying layer storage on disk uses binary-aligned block sizes. A "150 MB" Docker image actually occupies roughly 143 MiB on disk before compression. Compressed layers further complicate things: a 150 MB uncompressed image might only transfer 50 MB over the network. Container registries like Docker Hub display compressed sizes, while "docker images" shows uncompressed — leading to frequent confusion in CI/CD pipeline size budgets.

One mebibyte (1,048,576 bytes) holds about: one minute of MP3 audio at 128 kbps (≈ 960 kB, so slightly under 1 MiB), a medium-resolution JPEG photo (0.5–2 MiB), about 200 pages of plain text, or the complete text of a short novel. A typical Linux kernel image at boot is 8–12 MiB compressed.

RAM chips are physically organized as binary address grids — each address line doubles the capacity, so sizes must be exact powers of 2 (4 GiB = 2³² bytes, 8 GiB = 2³³ bytes). USB flash drives use NAND flash that is also binary internally, but manufacturers reserve variable amounts for wear levelling, bad block management, and controller firmware. A "64 GB" USB drive might have 64 GiB of raw NAND but only expose 59.6 GiB (64 × 10⁹ ÷ 2³⁰) to the user — the label uses decimal marketing, unlike RAM which honestly reflects binary sizing.