Why You May Pay for 300 Mbps but Only Get 100 Mbps

What the 300 Mbps vs 100 Mbps gap usually means

If you are paying for a 300 Mbps broadband plan but your download speed keeps landing near 100 Mbps, the problem is often not the plan itself. The number on your bill describes the access tier, while the speed you actually see depends on the modem, router, Wi-Fi signal, Ethernet link, device limits, and the way the ISP provisions the line.

A stable result around 90 to 110 Mbps is a strong clue that one part of the path is capped at 100 Mbps. That cap can come from a Fast Ethernet port, a damaged cable, an older router, a modem in bridge mode with a 100 Mbps interface, or a device that cannot process traffic any faster.

Reason 1: Your router or modem may be capped at 100 Mbps

Older routers and some gateways still use 100 Mbps WAN or LAN ports, which means your broadband service can never reach the full plan rate through that device. The same applies to some mesh nodes, switches, and powerline adapters. If every test tops out near 100 Mbps, check the model specifications for Gigabit Ethernet support.

Look for 100/1000 Mbps or Gigabit markings on the ports and confirm that the link negotiated at 1 Gbps in the admin interface. If the hardware only supports Fast Ethernet, replacing it is usually the most direct fix.

Reason 2: Wi-Fi is often the real bottleneck

Wi-Fi speeds are usually lower than wired speeds because of interference, distance, wall materials, channel congestion, and radio limits. A phone or laptop connected on 2.4 GHz may show close to 100 Mbps even on a much faster internet plan, especially in apartment buildings or crowded neighborhoods.

Test the same device next to the router on 5 GHz or Wi-Fi 6, then compare it with a wired Ethernet test. If the wired result is much higher, the ISP line is probably fine and the issue is in the wireless path. For better results, place the router in open space, use a cleaner channel, and keep the device on the band that matches its hardware.

Reason 3: The Ethernet cable or port may be the problem

A damaged cable, a low-grade cable, or a port that negotiated at 100 Mbps can flatten your speed even when the rest of the network is capable of more. This is common when an older cable is reused, when a wall jack is patched through legacy equipment, or when a dock or adapter only supports Fast Ethernet.

Use a known-good Cat 5e or better cable and connect a computer directly to the router or modem. Then check the link speed in the operating system or router interface. If it still shows 100 Mbps, swap the cable, test a different port, and remove intermediate devices until you find the bottleneck.

Reason 4: The device you are testing on may be limiting throughput

Some laptops, tablets, USB adapters, and older desktop network cards cannot sustain higher download speeds. Power saving settings, background scans, VPN clients, antivirus filtering, and CPU load can also reduce the measured rate. When that happens, the speed test reflects the device, not the broadband line.

Run the test on a second device that is known to support Gigabit Ethernet or modern Wi-Fi standards. If one device reaches close to the plan rate and another does not, the weaker device is the limiting factor. Update the network driver, disable VPN temporarily, and close heavy background transfers before testing again.

Reason 5: The ISP may be provisioning the line incorrectly

Sometimes the access line, account profile, or modem registration is not set up for the speed tier you purchased. This is more likely when the issue started after an upgrade, a modem replacement, or a service move. In those cases, every local test may stop around the same speed no matter what hardware you use.

Check whether the modem is fully online, whether the service tier shown in the customer portal matches your plan, and whether the issue appears on both wired and wireless tests. If the results are consistent across multiple devices and cables, contact the ISP and ask them to review provisioning, line errors, and signal levels.

Reason 6: Network congestion and test conditions can distort the result

Even when the line is healthy, a busy local network can reduce speed. Large downloads, cloud backups, game updates, streaming devices, and smart home traffic all share the same connection. Speed test servers can also vary, so a single test may understate what the line can do at another time or on another server.

For a cleaner reading, pause other network activity, connect by Ethernet, and test several times on different servers. Compare download, upload, and latency. If only one server looks slow while others are normal, the issue is likely the test path rather than your broadband service.

How to isolate the bottleneck step by step

Start with a wired test from one computer directly to the router or modem. If the result is near 100 Mbps, inspect the cable, port speed, and network adapter. If wired speed is much higher than Wi-Fi speed, focus on wireless settings, placement, and interference. If both wired and wireless tests stay low, the modem, provisioning, or ISP line is the next place to look.

1. Test with a single device and no other traffic running.
2. Use Ethernet before you judge the ISP speed.
3. Check the link rate shown by the router, modem, or operating system.
4. Repeat the test on another device to rule out hardware limits.
5. Save the result details before you contact support.

What to optimize before calling your ISP

The fastest wins are usually replacing any 100 Mbps equipment, using a better cable, and moving the test to a wired connection. After that, tune Wi-Fi by using 5 GHz or Wi-Fi 6 where supported, changing the router location, and reducing interference from neighboring networks. If the router is several years old, a modern model with Gigabit ports and better wireless radios can make a clear difference.

If the issue remains after those checks, contact the ISP with specific evidence: wired test results, device models, time of day, and whether the problem affects download, upload, or both. That gives support a better chance to distinguish a local hardware issue from a provisioning or network-side problem.

When the problem points to the service, not your gear

If multiple wired devices all stop around 100 Mbps, the same cable and router tests are clean, and the speed remains low at different times of day, the fault is more likely upstream. That can happen on cable broadband during congestion, on fiber when the account profile is wrong, or on any connection where the modem reports errors.

At that point, ask the ISP to review line statistics, signal quality, and provisioning status. A clear pattern across devices matters more than a single speed test result, and it helps support teams move faster.