ISP Routing Evidence Checklist: How to Prove a Bad Path
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
- Wired test results (remove Wi-Fi).
- Time-of-day pattern notes (3+ days).
- Under-load vs idle comparison (bufferbloat ruled out).
- Multiple targets/regions (not one server only).
- 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 ChecklistFind the trigger before escalation.
Packet Loss TriageLoss evidence and isolation.
Modem/ONT IssuesRule out the physical/link layer.
Matchmaking Lag MythsRouting can vary per match.
Related Articles
Fix Input Lag Fast (PC & Console): The No-Placebo Checklist
Stop chasing myths. This checklist targets the real causes of heavy feel: display processing, unstable pacing, render queue buffering, and background spikes.
Exclusive Mode Myths: When It Helps Audio (Rare) and When It Breaks Games
Exclusive mode can reduce OS mixing, but it often creates conflicts and instability. Use it only when it improves consistency, not because it sounds ‘pro’.
HDMI Black Level and RGB Range: The Quick Fix for Washed Out or Crushed Images
Washed out blacks or crushed shadow detail is often a range mismatch, not a bad screen. Use this quick check to fix readability in minutes.
Audio Chain for Gaming: One Clean Layer at a Time (No Stacking)
If direction feels wrong, you’re probably stacking processing. This guide shows a clean audio chain and the one-layer rule that restores readable footsteps.
Audio Chain Baseline: One Clean Path That Fixes Most Footstep Confusion
Footsteps become readable when your audio path is clean and consistent. This baseline removes stacked processing, wrong modes, and unstable levels that destroy direction cues.
VRR Range Basics: Why the Same Setup Feels Great in One Game and Bad in Another
VRR isn’t magic. If your FPS lives outside the VRR range, feel becomes inconsistent. Learn range basics, edge bouncing, and how to stay stable.
Audio Chain for Gaming: One Clean Path from Game to Ears
Audio positioning improves when the chain is clean and stable. Build one path: one device, one mode, minimal processing, consistent levels.
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.
Motion Clarity for Gaming: Blur Sources and the Fix Order That Works
Motion clarity isn’t one setting. Blur comes from multiple sources. Use this fix order to improve readability without adding latency or artifacts.
Render Queue Basics: Why the Game Feels Delayed Even at High FPS
High FPS doesn’t guarantee low delay. If frames queue up, you feel input lag. Learn the basics and the practical steps that reduce queueing delay.
Background Load Kill Switch: Stop Overlays, Sync, and Scans From Ruining Feel
If feel changes day-to-day, background load is a prime suspect. Use this kill-switch checklist to remove the usual culprits and stabilize frametimes.
120Hz Feels Worse? Diagnosis Checklist (Wrong Mode, VRR Range, Caps)
Higher refresh can expose instability. Use this checklist to diagnose why 120Hz feels worse: wrong mode, wrong refresh path, VRR range issues, or missing caps.