<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ADAPT INDIA NETWORKS</title>
    <description>The latest articles on DEV Community by ADAPT INDIA NETWORKS (@adaptindianetworks).</description>
    <link>https://dev.to/adaptindianetworks</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4253496%2Fe0388211-7ac6-4463-a9a9-1b3f75ef3b1b.jpg</url>
      <title>DEV Community: ADAPT INDIA NETWORKS</title>
      <link>https://dev.to/adaptindianetworks</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/adaptindianetworks"/>
    <language>en</language>
    <item>
      <title>Your Speed Test Is Lying: How to Measure Jitter, Packet Loss and Bufferbloat on Office Internet</title>
      <dc:creator>ADAPT INDIA NETWORKS</dc:creator>
      <pubDate>Thu, 19 Nov 2026 09:38:15 +0000</pubDate>
      <link>https://dev.to/adaptindianetworks/your-speed-test-is-lying-how-to-measure-jitter-packet-loss-and-bufferbloat-on-office-internet-b6c</link>
      <guid>https://dev.to/adaptindianetworks/your-speed-test-is-lying-how-to-measure-jitter-packet-loss-and-bufferbloat-on-office-internet-b6c</guid>
      <description>&lt;p&gt;Every time someone complains that video calls are freezing, someone else runs a speed test, sees a big number, and says the internet is fine.&lt;/p&gt;

&lt;p&gt;Speed tests measure one thing: how much data you can push through in a short burst. Calls, VoIP, remote desktop and most real work care about something else entirely, which is how consistent that connection is. A line can show 200 Mbps and still make every Teams call sound like a robot.&lt;/p&gt;

&lt;p&gt;I work with a telecom partner in India and spend a lot of time explaining this to office IT folks. Here's how to actually measure what matters, with tools you probably already have.&lt;/p&gt;

&lt;h2&gt;
  
  
  The four numbers that matter
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Latency:&lt;/strong&gt; how long a packet takes to get there and back. Lower is better.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Jitter:&lt;/strong&gt; how much that latency varies from one packet to the next. Calls hate jitter more than they hate high latency.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Packet loss:&lt;/strong&gt; packets that never arrive. Even 1 to 2% is enough to make calls choppy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bufferbloat:&lt;/strong&gt; how much latency jumps when the line is busy. This is the sneaky one, and it's why calls break the moment someone starts a big upload.&lt;/p&gt;

&lt;p&gt;Rough rules of thumb for voice and video: latency under about 100 ms to the service you use, jitter under about 30 ms, packet loss under 1%. Not hard limits, but good enough to know if you have a problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test 1: a long ping, not a short one
&lt;/h2&gt;

&lt;p&gt;A 4-packet ping tells you nothing. Run at least 100.&lt;/p&gt;

&lt;p&gt;Linux / macOS:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ping -c 100 1.1.1.1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Windows:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ping -n 100 1.1.1.1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Look at the summary at the end. Packet loss is the percentage. On Linux/macOS, the &lt;code&gt;mdev&lt;/code&gt; (or &lt;code&gt;stddev&lt;/code&gt;) value is a decent stand-in for jitter. On Windows, look at how far apart the minimum and maximum are. If min is 8 ms and max is 300 ms, you have a jitter problem even if the average looks fine.&lt;/p&gt;

&lt;p&gt;Run it once when the office is empty and once at the busiest hour. The difference is the story.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test 2: find where the problem is with mtr
&lt;/h2&gt;

&lt;p&gt;Ping tells you there's loss. &lt;code&gt;mtr&lt;/code&gt; tells you where.&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mtr -rwzbc 100 1.1.1.1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;On Windows, the built-in equivalent is:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;pathping 1.1.1.1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;You get a list of every hop between you and the target, with loss and latency at each one.&lt;/p&gt;

&lt;p&gt;How to read it without fooling yourself:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Loss at a middle hop that &lt;strong&gt;doesn't continue&lt;/strong&gt; to the final hop is usually fine. Many routers deprioritise replies to these probes.&lt;/li&gt;
&lt;li&gt;Loss that &lt;strong&gt;starts at one hop and continues all the way to the end&lt;/strong&gt; is real. Note where it starts.&lt;/li&gt;
&lt;li&gt;If it starts at hop 1 or 2, it's probably your own router, firewall or Wi-Fi.&lt;/li&gt;
&lt;li&gt;If it starts a few hops in, inside your ISP's network, that's the screenshot you send to their support team.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Test 3: run it over a cable first
&lt;/h2&gt;

&lt;p&gt;Before blaming the ISP, plug a laptop directly into the router or firewall with a cable and run the same tests. If the cable is clean and Wi-Fi isn't, your internet is fine and your Wi-Fi needs fixing. This one step settles about half of all "internet is slow" arguments.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test 4: bufferbloat
&lt;/h2&gt;

&lt;p&gt;Start a long ping in one terminal:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ping 1.1.1.1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Then, in another window, start a big upload (a large file to Google Drive, for example) and watch the ping times.&lt;/p&gt;

&lt;p&gt;If latency goes from 10 ms to 400 ms while the upload runs, that's bufferbloat. It explains the classic complaint: "calls are fine until someone sends a big file". There are also browser-based bufferbloat tests that show latency under load if you want a quick picture.&lt;/p&gt;

&lt;p&gt;The fix is usually SQM or QoS on your firewall (shaping traffic slightly below line speed so queues don't build up), or simply more upload bandwidth.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test 5: real throughput with iperf3
&lt;/h2&gt;

&lt;p&gt;Online speed tests hit a nearby server, often inside your ISP's network, so they can look better than real life. If you have a server or VM outside your office (a cloud VM works), install &lt;code&gt;iperf3&lt;/code&gt; on both ends.&lt;/p&gt;

&lt;p&gt;On the server:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;iperf3 -s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;From the office:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;iperf3 -c &amp;lt;server-ip&amp;gt; -t 30
iperf3 -c &amp;lt;server-ip&amp;gt; -t 30 -R
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;The &lt;code&gt;-R&lt;/code&gt; flag tests the reverse direction, so you see both upload and download. On a shared broadband line, run it at different times of day. If the numbers swing a lot, you're seeing contention, other users in your area sharing the same capacity.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the results usually point to
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Clean on cable, bad on Wi-Fi:&lt;/strong&gt; fix the Wi-Fi. Access point placement, channels, too many users per access point.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bufferbloat during uploads:&lt;/strong&gt; QoS/SQM on the firewall, or more upload bandwidth.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Loss or jitter starting inside the ISP's network:&lt;/strong&gt; take your mtr output to the ISP.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fine at 9 am, bad at 4 pm, every day:&lt;/strong&gt; contention on a shared connection. This is where a dedicated &lt;a href="https://www.adapt-india.net/services/smart-internet-ill/" rel="noopener noreferrer"&gt;internet leased line&lt;/a&gt; helps, since the bandwidth isn't shared and upload matches download. We explain the difference in more detail in our &lt;a href="https://www.adapt-india.net/blog/why-dedicated-internet-leased-lines-matter/" rel="noopener noreferrer"&gt;leased line vs broadband guide&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multiple sites with uneven links:&lt;/strong&gt; &lt;a href="https://www.adapt-india.net/services/smartflo-sd-wan/" rel="noopener noreferrer"&gt;SD-WAN&lt;/a&gt; measures latency, jitter and loss on every link continuously and moves each app to the healthiest one, which is these tests done automatically, every second.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Save your results
&lt;/h2&gt;

&lt;p&gt;Whatever you find, save the output with the date and time. When you call the ISP with "100-packet ping, 6% loss starting at hop 4, every day between 3 and 6 pm, mtr attached", you get a very different response from "sir, the internet is slow".&lt;/p&gt;

&lt;p&gt;Got a weird mtr output you can't read? Paste it in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I work with &lt;a href="https://www.adapt-india.net/" rel="noopener noreferrer"&gt;Adapt India Networks&lt;/a&gt;, a Tata Tele Business Services and ACT Fibernet partner in New Delhi.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>networking</category>
      <category>sysadmin</category>
      <category>devops</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
