{"id":3597,"date":"2026-11-04T00:00:01","date_gmt":"2026-11-03T16:00:01","guid":{"rendered":"http:\/\/www.greymateredu.com\/blog\/?p=3597"},"modified":"2026-11-04T00:00:01","modified_gmt":"2026-11-03T16:00:01","slug":"how-to-use-the-traceroute-command-in-a-terminal-4797-1942e3","status":"publish","type":"post","link":"http:\/\/www.greymateredu.com\/blog\/2026\/11\/04\/how-to-use-the-traceroute-command-in-a-terminal-4797-1942e3\/","title":{"rendered":"How to use the traceroute command in a terminal?"},"content":{"rendered":"

Hey there, let\u2019s cut through the jargon for a sec: if you\u2019ve ever dealt with wonky internet, laggy video calls, or apps that just won\u2019t connect like they should, traceroute is your bread and butter. And since I\u2019m the guy who\u2019s been selling terminals for years\u2014you know, the kind people actually use without fighting weird UIs\u2014I\u2019ve seen how people mess up traceroute all the time. Either they run it wrong, ignore the weird numbers, or just never get why it matters beyond \u201cit says something about my internet.\u201d Terminal<\/a><\/p>\n

<\/p>\n

First off, let\u2019s get one thing straight: traceroute isn\u2019t some fancy black box. It\u2019s a terminal command built right into most operating systems\u2014Windows, macOS, Linux, even some network gear\u2014and it\u2019s basically a map of your internet connection. Like, if you\u2019re trying to get from your couch to a friend\u2019s house, traceroute lists every street corner, stop sign, and random detour your data takes along the way. That\u2019s it. No rocket science, just good info.<\/p>\n

I sell terminals because I\u2019ve seen too many cheap ones that lag mid-SSH session or crash when you run simple network tools. But even if you\u2019ve got a top-tier terminal, if you don\u2019t know how to use traceroute, it\u2019s like owning a sports car and only driving it to the grocery store. Let\u2019s break this down like I\u2019d explain it to a buddy who\u2019s just picked up their first dev terminal from my shop.<\/p>\n

First, how do you even launch it? If you\u2019re on Linux or macOS, open the Terminal app (the one I sell, obviously) and pop that command into the prompt. On Windows, it\u2019s a little different\u2014they call it tracert, no \u201ce\u201d at the end, and you run it in Command Prompt or PowerShell if you\u2019ve got a newer setup. That\u2019s a tiny gotcha a lot of new terminal users miss, so watch for that.<\/p>\n

Now, what do you type after the command? Let\u2019s say you want to trace the path to google.com. On macOS\/Linux, you type traceroute google.com; on Windows, tracert google.com. Hit enter, and you\u2019ll see a list pop up. Each line is a \u201chop\u201d\u2014that\u2019s one stop your data makes. The number at the start is the hop number, starting at 1 (that\u2019s your local router, usually) and going all the way to the final destination.<\/p>\n

Next, the three numbers after the hop: those are round-trip times (RTT) in milliseconds. That\u2019s how long it takes a tiny packet of data to go from your terminal to that hop and back. So if hop 1 is 1ms, that\u2019s your router talking to itself basically\u2014super fast. If hop 10 is 200ms? That\u2019s a problem waiting to happen.<\/p>\n

Wait, sometimes you\u2019ll see asterisks (*) instead of numbers. That means that hop isn\u2019t returning a response to traceroute. Why? Firewalls block ICMP packets (the ones traceroute uses) all the time\u2014some network admins don\u2019t want random people poking their routers. That\u2019s not a failure, it\u2019s just the internet being private. Don\u2019t panic if you see a few *s; focus on the numbers that are consistent.<\/p>\n

Let\u2019s talk about common use cases, because that\u2019s where this stops being a boring command and becomes a problem solver. I get calls every week from customers using my terminals for remote work: \u201cMy VPN is lagging so bad I can\u2019t join meetings!\u201d Run traceroute to your work\u2019s server. If hop 5 is 300ms and all others are 50, that\u2019s where the bottleneck is\u2014either your ISP\u2019s line to that office is garbage, or their network has a problem.<\/p>\n

Another one: online gaming. Ever get \u201cserver timed out\u201d mid-match? Traceroute to the game\u2019s server. If the last few hops are spiking, that\u2019s not your terminal\u2014it\u2019s the game\u2019s host or your ISP. A lot of people waste money upgrading their router when the issue is 10 hops away, not their own gear.<\/p>\n

And for web dev folks? If your app is loading slow for users on the East Coast but fast for you in California, run traceroute from a terminal located on the East Coast. That shows you the extra hops and delays in that region, so you can fix a CDN issue instead of redoing your code.<\/p>\n

Wait, there\u2019s a trick a lot of pro terminal users use: controlling the number of hops. By default, traceroute will keep going until it hits the destination, but if you just want to check the first 15 stops, you can add a flag. On macOS\/Linux, it\u2019s traceroute -m 15 google.com. On Windows, tracert -h 15 google.com. That saves time if you don\u2019t need the full map. Also, if you want to use a different packet size (some hops are finicky about that), the -s flag on macOS\/Linux works\u2014useful if you\u2019re debugging a specific issue with large files.<\/p>\n

Now, let\u2019s talk about the mistakes people make all the time. First, running traceroute once and calling it a day. Network conditions change\u2014traceroute at 2pm when everyone\u2019s home from work will look different than at 2am when it\u2019s quiet. Run it a few times, especially if you\u2019re troubleshooting a intermittent issue. Second, ignoring the \u201clast hop\u201d number. That\u2019s the destination itself. If that\u2019s spiking, the problem is the host, not your side. Third, using a bad terminal. I see it all the time: people buy a cheap off-brand terminal from a random site, and when they run traceroute, the numbers are weird and inconsistent because the terminal\u2019s network stack is garbage. That\u2019s why my terminals are built with stripped-down, reliable OSes that don\u2019t bloat the network tools\u2014you get accurate results, no matter what.<\/p>\n

Let\u2019s do a quick example to make it real. Suppose I\u2019m on my test terminal, running traceroute to a server I use for hosting my demo sites. The output looks like this:
\n1 router.home (192.168.1.1) 1ms 1ms 1ms
\n2 isp-gateway.example.com (10.0.0.1) 5ms 6ms 5ms
\n3 core-1.atlanta.isp.net (203.0.113.45) 12ms 11ms 13ms
\n4 peering.example.net (198.51.100.22) 45ms 47ms 44ms
\n5 server.demo (209.132.1.1) 210ms 205ms 208ms<\/p>\n

So here, hop 5 is the final server. That 200ms RTT is way higher than the previous hops. That means the delay is between our peering link and the actual server. If I were the user here, I\u2019d check if that server\u2019s host has a problem, or if my ISP\u2019s peering agreement is garbage. No need to waste time messing with my terminal or router settings for something that\u2019s not on my end.<\/p>\n

Another thing: traceroute vs mtr, which is another tool a lot of terminal users ask about. Mtr is like a combination of traceroute and ping\u2014it updates in real time, so you can see average, min, max RTT per hop. It\u2019s great for ongoing troubleshooting, but traceroute is simpler for a quick map of where things go. I stock terminals with both tools pre-installed, because half the users who buy my kit need one, half the other.<\/p>\n

Wait, should I mention when not to use traceroute? Yeah\u2014if you\u2019re trying to troubleshoot a problem with a specific app, not the connection. If your email loads slow but your web surfing is fast, traceroute to the email server, not google.com. Target the right destination, that\u2019s half the battle. A lot of new users just run traceroute to a random big site, and they miss the actual issue with their service\u2019s server.<\/p>\n

And for the network admins reading? (I know a lot of my customers are small business owners who use terminals for their server rooms.) Traceroute is also useful for testing new network gear. If you just set up a new switch, run traceroute from a terminal plugged into it to make sure it\u2019s routing traffic correctly. If the hops are all zero or inconsistent, the switch\u2019s configuration is off. That\u2019s a quick check that saves you hours of digging through network logs.<\/p>\n

Now, let\u2019s wrap this up like I would with a customer in my shop. Traceroute isn\u2019t some advanced, scary command\u2014it\u2019s the terminal\u2019s built-in detective for your internet. You don\u2019t need a fancy degree to use it, just a reliable terminal (shameless plug, but I\u2019ve stood behind every terminal I sell for 5 years) and a little patience to look at the numbers. If you\u2019re messing with your home internet for gaming, remote work, or small business servers, traceroute will tell you exactly where the problem is\u2014no guesswork, no overpaying for unnecessary upgrades.<\/p>\n

<\/p>\n

If you\u2019ve been dealing with wonky connections and want a terminal that actually runs traceroute (and other network tools) without glitches, or if you need help troubleshooting a specific issue, hit up our team to chat about your setup. We\u2019ll walk you through it, no sales pitch, just real answers from people who use terminals every day.<\/p>\n

1.25mm Pitch Connectors<\/a> References
\nTraceroute Command – Linux Man Pages
\nTracert Command – Microsoft Learn
\nMTR – My Traceroute Official Documentation<\/p>\n

\n

Zhejiang AMA&Hien Technology Co., Ltd.<\/a>
We are one of the most professional terminal manufacturers in China since 1989, specialized in providing high quality customized products for global clients. We warmly welcome you to buy cheap terminal made in China here from our factory.
Address: Puqi Special Industrial Zone, Yueqing City, Zhejiang Province, China
E-mail: huangyimeng@ama.com.cn
WebSite: https:\/\/www.amaelec.com\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Hey there, let\u2019s cut through the jargon for a sec: if you\u2019ve ever dealt with wonky … How to use the traceroute command in a terminal?<\/span>Read more<\/a><\/p>\n","protected":false},"author":42,"featured_media":3597,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3560],"class_list":["post-3597","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industry","tag-terminal-46f2-197380"],"_links":{"self":[{"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/posts\/3597","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/users\/42"}],"replies":[{"embeddable":true,"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/comments?post=3597"}],"version-history":[{"count":0,"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/posts\/3597\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/posts\/3597"}],"wp:attachment":[{"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/media?parent=3597"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/categories?post=3597"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.greymateredu.com\/blog\/wp-json\/wp\/v2\/tags?post=3597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}