<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Traceroute on Bruce on AI Engineering</title><link>http://www.heyuan110.com/tags/traceroute/</link><description>Recent content in Traceroute on Bruce on AI Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 28 Jun 2020 12:12:04 +0800</lastBuildDate><atom:link href="http://www.heyuan110.com/tags/traceroute/index.xml" rel="self" type="application/rss+xml"/><item><title>Traceroute Command Explained: Network Path Tracing and Troubleshooting Guide</title><link>http://www.heyuan110.com/posts/linux/2020-06-28-traceroute/</link><pubDate>Sun, 28 Jun 2020 12:12:04 +0800</pubDate><guid>http://www.heyuan110.com/posts/linux/2020-06-28-traceroute/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/linux/2020-06-28-traceroute/cover.webp"
 alt="Diagram showing how traceroute works by incrementing TTL to probe each hop along a network path"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1600"
 height="578"
/&gt;
&lt;/p&gt;
&lt;p&gt;Slow websites, laggy video calls, SSH connections that hang forever &amp;ndash; these problems often hide somewhere along the network path between you and a remote server. The &lt;strong&gt;traceroute&lt;/strong&gt; command (&lt;code&gt;tracert&lt;/code&gt; on Windows) is the tool that answers &amp;ldquo;where exactly is the bottleneck?&amp;rdquo; It maps every router between your machine and the destination, measuring the round-trip delay at each hop so you can see precisely where things go wrong.&lt;/p&gt;</description></item></channel></rss>