<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Traceroute - Tag - Fryguy's Blog</title><link>https://fryguy.net/tags/traceroute/</link><description>Traceroute - Tag - Fryguy's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 31 Aug 2026 13:00:00 +0000</lastBuildDate><atom:link href="https://fryguy.net/tags/traceroute/" rel="self" type="application/rss+xml"/><item><title>New Tool - Traceroute / Ping Visualizer</title><link>https://fryguy.net/2026/08/31/new-tool-traceroute-ping-visualizer/</link><pubDate>Mon, 31 Aug 2026 13:00:00 +0000</pubDate><author>Fryguy</author><guid>https://fryguy.net/2026/08/31/new-tool-traceroute-ping-visualizer/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/posts/traceroute-visualizer-header.svg" referrerpolicy="no-referrer">
            </div><p>New on the <a href="/tools/" rel="">Network Tools</a> page: a <a href="/tools-traceroute-visualizer/" rel="">Traceroute / Ping Visualizer</a>. Paste raw output from <code>traceroute</code>, Windows <code>tracert</code>, or <code>ping</code> and it turns the wall of text into something you can actually read at a glance — a per-hop latency chain or a per-packet chart, with timeouts, latency jumps, and dropped packets flagged automatically.</p>
<h2 id="what-it-does">What It Does</h2>
<p>It auto-detects which of the four formats you pasted — Linux/Mac <code>traceroute</code>, Windows <code>tracert</code>, Linux <code>ping</code>, or Windows <code>ping</code> — and renders the right visualization:</p>]]></description></item></channel></rss>