Route analyzer, DNS benchmark and Apply DNS

The Route Analyzer is BRUTAL's deepest network tool. Where the Ping Test gives you a fast single number per region, the Route Analyzer measures the full distribution your connection actually feels — median latency, 95th-percentile spikes, jitter and packet loss — then traces your route to find bottlenecks, benchmarks DNS resolvers, and can apply the fastest one with a click.

The buttons on the page

• Analyze — the full run: regional latency to 9 reference endpoints, then a DNS benchmark, then an overall network health grade (A–F) with honest, evidence-based tips.
• DNS Only — just the DNS benchmark, when you only want to find a faster resolver.
• Detect My Match — finds the real server your running game or emulator is connected to and probes it directly.
• Bufferbloat — the latency-under-load test (covered in its own article).
• Trace Route — a hop-by-hop traceroute that classifies each hop and flags the worst latency jump.
• Apply DNS / One-Click Optimize — sets the fastest resolver on your active adapter and flushes the cache.

Honest latency: median, p95, jitter and loss

When you click Analyze, BRUTAL sends a real burst of ICMP probes to each region and reports the whole picture, not a flattering best-case sample:

• Median (the big number): your typical round-trip latency.
• p95: the latency on a bad tick — what you feel when it spikes.
• Jitter: how much latency varies probe to probe. High jitter causes rubber-banding even when the average looks fine.
• Loss: the percentage of probes that never came back. Even 1–2% loss ruins fast games.

If your network blocks ICMP entirely, BRUTAL falls back to a TCP-connect timer and labels it “(tcp)” so you know it is connect time, not pure ping. The best region is chosen by lowest median and then lowest jitter — because stability matters as much as raw speed.

The network health grade

After Analyze, a graded card (A through F) summarizes your connection. The score is weighted toward what players actually feel: latency, jitter and packet loss carry the most weight, reachability a little, and DNS is deliberately small — DNS speed affects loading and matchmaking, never your in-game ping. The tips below the grade are specific and honest: if your loss is high it says so and points you to a wired connection and the bufferbloat test; if your connection is already clean it tells you the remaining latency is physical distance no software can remove.

Detect My Match

This is the killer feature for honesty. Click Detect My Match while a game or emulator is running and in a live match. BRUTAL finds the actual public server your game process is talking to (via the running game/emulator PID) and probes that exact IP for median, p95, jitter and loss. If no game is connected, it tells you to start a match and try again; if the server blocks ICMP, it says so rather than faking a number.

Trace Route and bottleneck detection

Click Trace Route to map the path packets take, hop by hop, with per-hop latency and loss. Each hop is classified as Local, Local/ISP, ISP backbone, Internet transit or Destination, and the single biggest latency jump is flagged in orange as the bottleneck. This tells you where your lag is added — your own network, your ISP, or somewhere out on the internet. A second click on the button cancels a long trace, and BRUTAL automatically stops early if the path goes dark (several hops in a row blocking ICMP).

The DNS benchmark

BRUTAL benchmarks 7 popular resolvers — Cloudflare, Google, Quad9, OpenDNS, Comodo Secure, AdGuard and CleanBrowsing. Crucially, it does not just ping their IP addresses. It sends a real A-record DNS query over UDP port 53 to each resolver, bypassing your OS cache, and takes the median of several tries. That measures genuine resolver responsiveness, the way your browser and game launcher actually experience it. The fastest is marked Recommended.

Apply DNS (and how to revert)

1. Run Analyze or DNS Only so a fastest resolver is found.
2. Click Apply DNS Settings (or One-Click Optimize) and confirm the dialog. It shows exactly which resolver and IPs will be set.
3. BRUTAL picks your real internet adapter — the one with an active gateway, not a VPN or Hyper-V virtual adapter — and sets primary + secondary DNS via netsh, then flushes the DNS cache.
4. If it fails (some adapters refuse static DNS), BRUTAL tells you honestly and suggests setting it manually in Windows.

If a tweak breaks your connection: Repair Network Stack

The page also has a Repair Network Stack button. It runs the standard recovery sequence — netsh winsock reset, netsh int ip reset, netsh int tcp reset and ipconfig /flushdns — to recover from broken or overly aggressive network tweaks. A restart is required to finish.

Common issues and troubleshooting

• Detect My Match finds nothing: make sure the game is running and you are actually in a match, then click again. The connection has to exist for BRUTAL to find it.
• Many regions time out / results show (tcp): your ISP or firewall is blocking ICMP, so BRUTAL fell back to TCP-connect timing. The numbers are still useful, just labeled.
• Apply DNS picked the wrong adapter: BRUTAL prefers the adapter with an active default gateway. If you are on a VPN or virtual adapter, disconnect it and re-apply, or set DNS manually.
• Trace Route stops before the destination: that is normal — many endpoints (including AWS edges and game servers) filter ICMP, so BRUTAL bails once the path is clearly blocked.