Skip to content
Fix

Match your symptom to the fix.

Honest, vendor-specific guides — indexed by what the problem looks like to you, not by the product category we filed the article under. Find the fingerprint that matches; the walkthrough is one click away.

15 symptom fingerprints. Scroll, or type a word from your problem.

  • Router tuning
    My router's WAN speed test reads full speed, but every device caps at roughly half — wired and wireless both

    Hardware NAT acceleration on your router has been silently disabled by a feature you enabled and forgot about. The CPU is forwarding every packet in software, which most consumer router SoCs top out around 400–600 Mbps doing.

    Likely causes, ranked
    • 1.Security suite running (ASUS AiProtection / TP-Link HomeShield) — deep packet inspection forces software path
    • 2.Adaptive QoS enabled — disables hardware Flow Cache entirely
    • 3.VPN server, traffic analyzer, or web history features running on the router
  • ISP escalation
    I'm paying for gigabit (or close to it) and consistently getting a fraction of that, on a known-good wired connection

    Real delivery gap. You've already done the customer-side rule-outs; the line is the problem. The fix is structured escalation, not more router config.

    Likely causes, ranked
    • 1.DOCSIS line signal levels out of spec (cable) — needs an engineer truck roll
    • 2.Optical levels degraded or split too many times (fiber)
    • 3.ISP provisioning not matching the plan you're paying for (often the cause when no other issue is visible)
  • Wi-Fi diagnosis
    Wi-Fi works fine on my phone, but it's terrible on my PC in the same room

    The network isn't the variable. The device is. Almost always something specific to the PC: power management, an old Wi-Fi card, antenna position, or a USB 2.0 port choking a USB Wi-Fi adapter.

    Likely causes, ranked
    • 1.Windows power management throttling the Wi-Fi adapter (most common cause on laptops)
    • 2.Old Wi-Fi card (Wi-Fi 5 or earlier) bottlenecking against a Wi-Fi 6/6E router
    • 3.Desktop tower antennas pointed at sheet metal or hidden behind the desk
  • Cabling
    My wired ethernet is capped at exactly 90 (or ~94) Mbps no matter what device or speed test I use

    Your link has auto-negotiated from Gigabit (1000BASE-T) to Fast Ethernet (100BASE-TX). The protocol downshift happens when any one of the four wire pairs fails the Gigabit handshake. Almost always a damaged cable.

    Likely causes, ranked
    • 1.Damaged patch cable — the most common cause; swap it first
    • 2.Wall keystone jack with one or more broken pins
    • 3.In-wall run with a degraded pair (rare but happens with old Cat5 or rodent damage)
  • Cabling
    My powerline adapter is rated 'gigabit' or 'AV2000' but I'm only getting 50–150 Mbps

    Powerline PHY rates are theoretical maximums under lab conditions. Real-world throughput runs 30–50% of the advertised number on a good install, much less on a bad one. Your wiring topology, appliance noise, and outlet phasing all chew the signal.

    Likely causes, ranked
    • 1.The two adapters are on different electrical phases (US split-phase service)
    • 2.One adapter is plugged into a surge protector, power strip, or GFCI outlet
    • 3.Old branch wiring or appliances on the same circuit injecting noise
  • Wi-Fi diagnosis
    I added more Eero (or other mesh) nodes and Wi-Fi got worse, or devices keep switching between satellites

    Mesh oversaturation. In small or medium spaces, too many wireless nodes create overlapping coverage zones, force constant roaming decisions, and share spectrum between client traffic and backhaul. More nodes is not always better.

    Likely causes, ranked
    • 1.Wireless backhaul sharing spectrum with client traffic — adding satellites compounds the contention
    • 2.Overlapping coverage forcing the roaming algorithm to ping-pong devices between satellites
    • 3.Co-channel interference between adjacent mesh nodes on the same 5 GHz channel
  • Cabling
    I have coax in my walls and want a wired-quality connection without drilling for ethernet

    MoCA is the right tool for this. It uses the existing coaxial cable network in your walls to deliver near-gigabit ethernet between any two rooms with coax jacks. A pair of MoCA 2.5 adapters runs $130–180 and installs in 30 minutes.

    Likely causes, ranked
    • 1.Existing coax wall jacks are the asset — MoCA repurposes them
    • 2.Renters or owners of plaster/brick/lath walls where running cable is impractical
    • 3.Temporary setups where a permanent ethernet run isn't worth the work
  • Cabling
    I'm running ethernet and don't know if I should buy Cat6, Cat6a, Cat7, or Cat8

    Cat6 is the home-network floor in 2026. Cat6a is the future-proof choice for any in-wall run or for 10 GbE service. Cat7 is marketing — not a TIA standard. Cat8 is data-center cable, overkill for home.

    Likely causes, ranked
    • 1.If your service is up to 1 Gbps: Cat6, unshielded, UL-listed pure copper
    • 2.If your service is 2 Gbps+ or you might upgrade in 5 years: Cat6a
    • 3.If a product label says Cat7: skip it — buy Cat6a from a verified manufacturer instead
  • Plan fit
    I think I'm overpaying for an internet plan that's bigger than I actually need

    Probably true. Most homes don't need more than 300–500 Mbps; the community on r/HomeNetworking is unanimous about this. ISP middle tiers are engineered to make the top tier look like a steal — the cheapest tier is usually the right answer.

    Likely causes, ranked
    • 1.You signed up during a promo and never reviewed when the rate jumped
    • 2.You upgraded for a single use case (large game downloads, occasional 4K streaming) that doesn't actually need a higher tier
    • 3.Household size shrank but the plan didn't
  • Measurement
    My speed test says I have a fast connection, but my actual downloads are way slower

    Speed tests measure parallel TCP burst against a peered server. Real downloads use single-stream TCP against an arbitrary server with its own upload bandwidth, peering, and congestion. The two are measuring different things; the gap can be 5–25×.

    Likely causes, ranked
    • 1.The download source server is the bottleneck — its upload bandwidth, not yours
    • 2.Single-stream TCP throughput is capped by Bandwidth-Delay Product (RTT × packet loss)
    • 3.Peering between your ISP and the source server is congested, especially for cross-region downloads
  • Router tuning
    It was working fine, now it isn't, and I don't know what changed

    Time-shift regression. Common causes are a recent firmware update (router or OS), a cable that degraded across a threshold, or feature accumulation on a router that's gotten progressively more loaded over months.

    Likely causes, ranked
    • 1.Recent firmware update on the router introduced a regression or enabled new features
    • 2.Ethernet cable degraded enough to fail Gigabit auto-negotiation (look for the 90 Mbps cap)
    • 3.Years of accumulated router features (AiProtection, QoS, VPN) finally crossed the CPU's threshold
  • Wi-Fi diagnosis
    Microsoft Teams keeps showing “Your network is causing poor call quality”

    Teams is measuring a specific metric — the concealed sample ratio — and yours crossed 1.72%. The warning means audio packets are being dropped fast enough that the codec is interpolating more than it should. Almost always Wi-Fi link quality, bufferbloat under load, or a VPN routing detour.

    Likely causes, ranked
    • 1.Wi-Fi loss during the call — easy to confirm with a wired-vs-wireless test
    • 2.Bufferbloat from concurrent traffic (cloud backup, downloads) competing with audio packets
    • 3.Corporate VPN forcing Teams traffic through a slow gateway — ask IT for split tunneling
  • Measurement
    I don't understand what the numbers in my router app mean — is the live indicator my actual plan speed?

    No. The “live” number on every modern router app (Deco, Eero, ASUS, Google Home, Netgear, UniFi) is current real-time traffic — not plan capacity. At idle it reads tiny because almost nothing is flowing. Plan capacity is a separate measurement that requires running an explicit speed test.

    Likely causes, ranked
    • 1.Router apps show live traffic on the home screen because it animates nicely; plan capacity requires running a test, which doesn't
    • 2.The labels rarely make the distinction obvious
    • 3.Different apps display the same conceptual number with different meanings (Eero's “1.2 GB used” is data volume, not throughput)
  • Plan fit
    I want to know which tier my specific ISP is overselling and what I should actually buy

    Every major US ISP has a tier their sales reps push and a tier most households actually need. The pushed tier is rarely the right one. Per-ISP patterns differ: Comcast pushes 1.2 Gbps, Spectrum pushes Ultra, AT&T pushes 5 Gbps Fiber. The right answer is usually two or three tiers below.

    Likely causes, ranked
    • 1.Middle tiers are engineered as value traps to make the top tier look cheap
    • 2.Cable upload caps are independent of download tier — fiber 300/300 often beats cable 1000/35
    • 3.Data caps (Comcast 1.2 TB, Cox 1.25 TB) make the cheaper-looking plan more expensive for heavy households
  • ISP escalation
    I've talked to my ISP and they keep saying 'looks fine on our end' but it isn't

    Tier-1 support is script-driven and rewards closing tickets, not solving them. If your data is consistent and you've ruled out customer-side issues, the escalation path is well-defined: senior tech → retention → executive resolution, and external escalation via FCC informal complaint or state PUC when that stalls.

    Likely causes, ranked
    • 1.Tier-1 closes tickets too quickly with 'remote diagnostic shows no issue'
    • 2.Internal incentives reward short calls, not resolved problems
    • 3.The executive resolution team exists but tier-1 reps won't volunteer it

Coming next

  • · Zoom call quality diagnostic — Zoom's “Unstable Connection” warning thresholds
  • · Google Meet / Discord call diagnostic siblings
  • · Gaming-specific bufferbloat fixes (FPS jitter spikes on a fine-on-paper connection)
  • · VPN-induced throughput cap — how to diagnose the corporate-VPN tax
  • · When your ISP-supplied modem is the bottleneck

Once a guide resolves your throughput cap, run the stability test — throughput recovery is half the picture. Jitter, packet loss, and loaded latency are the other half, and they don't fix themselves when bandwidth comes back.