The plan says 500 Mbps. The download window says 58 MB/s. Both numbers are correct, and the gap between them is one letter and a factor of eight.
Lowercase b, uppercase B
- Mbps is megabits per second. Network equipment counts bits.
- MB/s is megabytes per second. File sizes are counted in bytes.
- One byte is eight bits, so divide Mbps by 8 to get MB/s.
| Plan | Theoretical top speed | Realistic on a wire |
|---|---|---|
| 100 Mbps | 12.5 MB/s | around 10–11 MB/s |
| 300 Mbps | 37.5 MB/s | around 30–34 MB/s |
| 500 Mbps | 62.5 MB/s | around 50–56 MB/s |
| 1000 Mbps | 125 MB/s | around 100–110 MB/s |
A 100 Mbps line moves at most 12.5 MB/s. A 4GB game download takes at least 320 seconds even on a perfect line — over five minutes.
Where the rest of the speed goes
- Protocol overhead. Every packet carries headers; acknowledgements and retransmissions take another bite.
- Wi-Fi. Distance, walls, interference, and older standards all cut throughput. Only a cable tells you what the line itself can do.
- The server. A busy server or a distant mirror caps you no matter what you paid for.
- Everyone else in the house. Background updates and other devices share the same pipe.
- Old hardware. An aging router or Wi-Fi card becomes the ceiling before your plan does.
Rule of thumb: 70–90% of the advertised rate on Ethernet is normal. On Wi-Fi, anything goes.
Reading the numbers without being fooled
- Speed tests report megabits; download managers usually show megabytes. Convert before comparing.
- Judging the ISP? Test wired. Judging the Wi-Fi? Test wireless. They are different questions.
- One slow download proves nothing. Try a second source before blaming anyone.
- If a gigabit plan tops out near 100 Mbps on every device, check the cable and router — gigabit needs gigabit ports at both ends.
When a download looks slow, multiply by eight before complaining. Half of all speed complaints dissolve at that step.