| Megabits per second (Mbit/s) | Exaoctets per second (Eo/s) |
|---|---|
| 1 Megabit per second | 1.25 × 10-13 Eo/s |
| 2 Megabits per second | 2.5 × 10-13 Eo/s |
| 3 Megabits per second | 3.75 × 10-13 Eo/s |
| 4 Megabits per second | 5 × 10-13 Eo/s |
| 5 Megabits per second | 6.25 × 10-13 Eo/s |
| 10 Megabits per second | 1.25 × 10-12 Eo/s |
| 20 Megabits per second | 2.5 × 10-12 Eo/s |
| 25 Megabits per second | 3.125 × 10-12 Eo/s |
| 50 Megabits per second | 6.25 × 10-12 Eo/s |
| 100 Megabits per second | 1.25 × 10-11 Eo/s |
| Reference | Megabits per second (Mbit/s) | Exaoctets per second (Eo/s) |
|---|---|---|
| A dial-up modem | 0.056 Mbit/s | 7 × 10-15 Eo/s |
| Typical home broadband | 100 Mbit/s | 1.25 × 10-11 Eo/s |
| Gigabit Ethernet | 1000 Mbit/s | 1.25 × 10-10 Eo/s |
| Streaming a 4K film | 25 Mbit/s | 3.125 × 10-12 Eo/s |
The megabit per second is a unit of data transfer rate equal to one million bits per second. Its symbol is Mbit/s, often written Mbps. It is the unit in which internet connections are sold, which makes it the data unit most people encounter by name.
Because it is a decimal million and not 1,048,576, the conversion to octets is exact and easy: one megabit per second is 125 kilooctets per second, so a hundred-megabit connection delivers about 12.5 megaoctets per second at best. Anyone who watches a file transfer and does the division has understood the entire relationship between how connections are advertised and how transfers are reported.
What a household actually needs is far below what it usually buys. Standard-definition video streaming uses about 3 megabits per second, high definition about 5, and ultra-high definition about 25. A video call is around 3 to 8. A large family watching four separate high-definition streams while somebody downloads a game is using perhaps 60 megabits per second, which a hundred-megabit connection handles comfortably.
The reason to buy more capacity than that is not peak speed but behaviour under load. A link that is near its limit develops queues, and queues add delay, which shows up as stutter in video calls and lag in games. A connection with generous headroom keeps its latency low, and that is a more noticeable improvement than a higher number on a speed test.
Wired local networks pass through this range on the way up. The original Ethernet ran at 10 megabits per second, its successor at 100, and both were the standard office connection for a decade each before gigabit replaced them. Wireless standards followed the same path with a lag, and both are now measured in hundreds of megabits or in gigabits.
Real throughput is always below the nominal rate. Protocol overhead takes 5 to 10 per cent on a wired link; a shared wireless channel loses much more, because the medium is divided between all the devices using it and interference forces retransmission. A connection advertised at 100 megabits per second measured at 90 over cable and 50 over a busy wireless network is behaving normally.
One megabit per second equals 1,000,000 bits per second, 125 kilooctets per second, or about 0.9537 mebibits per second.
The exaoctet per second is a unit of data transfer rate equal to a thousand petaoctets per second, or eight exabits per second. Its symbol is Eo/s. Nothing built runs at this rate: it is about eight times the total traffic of the entire internet, counted across every network on the planet at once.
The unit is useful mainly for thought experiments about limits. If every hard drive and flash chip manufactured in a year were read simultaneously at full speed, the combined rate would be in this range. So would the total output of every camera sensor in every phone on Earth if they all recorded at once. These are sums over the whole world's hardware, not rates any system experiences.
There is one situation in which very large data volumes really do move faster than any network, and it puts the unit in perspective. Physically shipping a container of hard drives across an ocean transfers more data per second, averaged over the journey, than any cable. A shipping container holding a few exaoctets crossing the Atlantic in a week works out to several gigaoctets per second, and a truck of drives driven across a city beats almost any local link.
That calculation is not a joke; cloud providers offer it as a service. When a customer needs to move petaoctets into a data centre, the provider ships a lorry full of storage rather than attempting the transfer over a network, because the network would take months. The bandwidth of a vehicle is enormous, though its latency is measured in days.
For the unit itself, an exaoctet per second is 125 petaoctets per second, and it would transfer the world's entire stock of stored data — a few hundred zettaoctets — in about a week of continuous running. No mechanism exists to feed such a link, and none is being designed.
A converter must nevertheless handle the unit, because it appears in aggregate capacity models, in academic papers on the theoretical limits of communication, and in any table that lists the metric prefixes completely. A quantity does not need a use for its name to be well formed.
One exaoctet per second equals 1,000 petaoctets per second, 8 exabits per second, or about 0.8674 exbioctets per second.