ISP Routing Evidence Checklist: How to Prove a Bad Path

If wired is unstable and only some regions feel bad, it might be routing. Use this evidence checklist so ISP support can’t hand-wave the issue away.
Published:
Aleksandar Stajic
Updated: February 23, 2026 at 01:15 PM

Routing issues are real, but support won’t act on feelings. You need evidence: consistent times, reproducible tests, and proof that the problem persists on Ethernet with minimal background load.

Evidence Checklist

  1. Wired test results (remove Wi-Fi).
  2. Time-of-day pattern notes (3+ days).
  3. Under-load vs idle comparison (bufferbloat ruled out).
  4. Multiple targets/regions (not one server only).
  5. Screenshots/logs of spikes and loss symptoms.

What to Say to Support

  • Issue is reproducible on Ethernet, minimal load.
  • Not a Wi-Fi/interference problem.
  • Time windows and patterns documented.
  • Request line quality and routing escalation.

Rule: don’t escalate until you’ve isolated your local path. Evidence turns ‘maybe’ into action.

Related Guides

Jitter Spikes Checklist

Find the trigger before escalation.

Packet Loss Triage

Loss evidence and isolation.

Modem/ONT Issues

Rule out the physical/link layer.

Matchmaking Lag Myths

Routing can vary per match.

Related Articles

End-to-End Feel Diagnosis: A Simple Flow That Finds the Real Cause

Stop guessing. Use this end-to-end flow to diagnose bad feel: display mode, timing, input queue, audio chain, and network load — in the right order.

Streaming Stutter: Storage, Decompression, and the Hitch Pattern

Streaming stutter is asset loading: new areas, new textures, periodic hitches. Learn the pattern, what to change first, and what upgrades actually help.

Input Stability Week: The 7-Day Plan to Lock Consistent Feel

Your setup won’t feel consistent if you change five variables a day. Use this 7-day plan to lock a baseline, isolate issues, and keep control stable.

QoS Myths for Gaming: What Helps, What Hurts, and the Real Priority

QoS is not a magic ‘gaming’ toggle. Good queue management reduces latency under load. Bad QoS adds jitter or breaks fairness. Here’s the stable way to think about it.

Capture and Overlays: When Recording Tools Add Delay and Spikes

Recording and overlays can change timing and feel. Use this checklist to isolate capture overhead and keep frametimes stable while streaming or clipping.

Latency Chain Explained: Where Delay Actually Comes From (End to End)

Input lag is a chain, not one setting. Learn where delay comes from (device, render queue, display) and the fix order that actually improves feel.

Comfort to Control: Why Ergonomics Improves Aim More Than You Think

Ergonomics is not optional. Fatigue changes grip, timing, and precision. Use a simple comfort baseline so your control stays consistent for hours.

Latency Features Explained: Reflex, Anti-Lag, and When They Actually Help

Latency features help only when the baseline is stable. Learn what Reflex/Anti-Lag type features do, when they reduce queue delay, and when they cause instability.

Console Audio Modes: Stereo, Surround, and Why Auto Often Fails

Auto audio modes can change your cues mid-session. Learn how console audio modes interact with games and headsets, and how to lock a stable mode for readable direction.

Fix Input Lag Fast: The No-Placebo Checklist (Display, Timing, Background Load)

Stop guessing. This checklist isolates the real causes of input lag: display processing, unstable timing, and background load — in the right order.

V-Sync and Tearing: When It Helps, When It Hurts, and the Stable Alternative

Tearing is visible, but the wrong fix can add heavy feel. Learn when V-Sync is worth it, when it hurts, and how VRR + caps reduce tearing with less tradeoff.

Audio EQ Minimalism: Small Changes That Improve Footstep Readability

EQ can help, but big curves often destroy distance and direction cues. Use minimal moves to improve footsteps without turning audio into mush.