Why a Speed Test Caps at 100 Mbps on a 300 Mbps Plan

A speed test stuck near 100 Mbps on a 300 Mbps plan usually points to a cable, Wi-Fi, router, or ISP profile limit.

Published 2026-09-06 Last updated 2026-09-06 Category: Guides

If your speed test repeatedly tops out near 90 to 100 Mbps on a 300 Mbps plan, the issue is usually not the plan itself. In many cases, the bottleneck is a 100 Mbps link somewhere between the device, router, modem, and ISP network.

What This Pattern Usually Means

A result that stays close to 100 Mbps is a strong clue. It often matches the ceiling of Fast Ethernet, a limited Wi-Fi link, or a service profile that was provisioned incorrectly. The key is to separate a real network limit from a test artifact.

Common Reasons for a 100 Mbps Ceiling

1. A 100 Mbps Ethernet Link

If your router port, modem port, wall jack, or cable negotiates at 100 Mbps instead of 1 Gbps, the speed test will usually stop there. This is one of the most common reasons a wired test never reaches the plan rate.

2. Wi-Fi Is the Bottleneck

Wireless performance can fall well below the service tier, especially on 2.4 GHz, in crowded apartments, or when the device is far from the router. A weak Wi-Fi signal can make a 300 Mbps plan look like a 100 Mbps plan even when the ISP line is fine.

3. The ISP Profile Is Set Too Low

Some connections are provisioned with the wrong speed profile, or a billing or activation change was not applied cleanly. If every wired device sees the same cap, the ISP account or line profile may need to be checked.

4. Router or Modem Hardware Cannot Keep Up

Older routers, entry-level gateways, or overloaded modem-router combos may have limited throughput. CPU limits, outdated firmware, or traffic features such as QoS can reduce download speed enough to create a stable 100 Mbps ceiling.

5. The Test Path or Device Is the Problem

Some devices, browsers, VPNs, security tools, or nearby background downloads can distort a speed test. A single busy laptop is not enough to prove the whole connection is slow, especially if other devices perform differently.

How to Check the Real Cause

Start with a direct Ethernet test. Connect one computer to the router with a known gigabit-capable cable, then confirm the link speed in the adapter settings. If the link shows 100 Mbps, the bottleneck is local.

Next, test another device on the same cable, then compare a wired test with a nearby Wi-Fi test. If wired performance is much higher than wireless, the ISP line is probably not the issue.

Finally, run tests on more than one server and at different times of day. If all wired tests stay near the same ceiling, the result is likely tied to provisioning, hardware, or a consistent link-rate limit.

How to Improve the Result

  • Use Cat5e or Cat6 Ethernet cables and confirm every port in the path supports gigabit speeds.
  • Restart the modem and router after changes, then retest with one device only.
  • Move closer to the router or switch to 5 GHz Wi-Fi for higher throughput.
  • Update router firmware and disable features that may be limiting throughput, such as heavy QoS rules.
  • Bypass the router and test the modem or ONT directly when your setup allows it.

When to Contact Your ISP

If a wired gigabit test still sits near 100 Mbps after you have ruled out cables, ports, and local hardware, contact the ISP and ask them to verify the service profile. Mention that the connection appears capped near 100 Mbps on a 300 Mbps plan and ask them to check line provisioning and account settings.

What a Good Result Should Look Like

On a 300 Mbps plan, real-world speed tests may not reach the exact headline number every time, but they should usually clear 100 Mbps by a wide margin on a healthy wired connection. If they do not, treat the result as a troubleshooting signal, not as proof that the plan is undersized.