Healthy Network vs. Activity Monitor: Why You Need More Than Throughput Data

What Activity Monitor Actually Shows You

Activity Monitor is every Mac user’s first instinct when something feels wrong. Open it, click the Network tab, and you get a wall of data. But what data, exactly?

The per-process columns show four values for each running application: Sent Bytes, Received Bytes, Sent Packets, and Received Packets. This tells you which apps are using the network and how much data they’re moving. If Dropbox is consuming 50 Mbps of your upload bandwidth, you’ll see it here.

The system-wide summary at the bottom of the window aggregates everything: total packets in and out, total data received and sent, and current throughput in bytes per second. Below that, a real-time rolling graph shows recent packets per second or data per second (you can toggle between the two). The update frequency is configurable at 1-second, 2-second, or 5-second intervals. You can even display this graph in the Dock icon for a persistent visual.

This is genuinely useful information. If you suspect a specific app is hogging bandwidth, Activity Monitor will confirm it. If you’re downloading a large file and want to verify data is actually flowing, the throughput graph shows it clearly. For questions about how much data is moving and which app is moving it, Activity Monitor is the right tool.

The problem is what it doesn’t show.

The Blind Spots: What Activity Monitor Can’t Tell You

Activity Monitor’s Network tab has five critical blind spots that make it nearly useless for diagnosing connection quality problems:

No Latency Data

Throughput and responsiveness are not the same thing. You can have 500 Mbps of throughput and 200ms of latency simultaneously, fast at moving bulk data but sluggish for anything interactive. Activity Monitor has zero concept of round-trip time. It cannot tell you how long a packet takes to reach its destination and return. For video calls, gaming, and any real-time application, latency is the metric that matters most, and Activity Monitor doesn’t measure it at all.

No Packet Loss

Activity Monitor counts bytes and packets that were successfully transferred. It does not count packets that were sent but never arrived. A 2% packet loss rate, enough to destroy VoIP audio quality and cause visible video freezing, is completely invisible in Activity Monitor. The throughput graph might look perfectly normal while your call sounds like it’s underwater.

No Jitter Measurement

Jitter, the variation in latency between consecutive packets, is the single most important metric for real-time application quality. It determines whether your voice sounds natural or robotic, whether your game feels responsive or rubber-bands. Activity Monitor has no concept of packet timing consistency. This metric simply doesn’t exist in the tool.

No Persistent Historical Data

Activity Monitor does have a real-time rolling throughput graph, but it shows only the last few minutes of data and only for throughput: not latency, not loss, not jitter. There’s no 24-hour view, no saved history, no way to go back and correlate “my call dropped at 3 PM” with network data from that time. When the data scrolls off the graph, it’s gone forever. If your connection had problems while you were asleep, at lunch, or simply not staring at the window, you’ll never know.

No Connection Quality Assessment

Activity Monitor answers “how much data is flowing?” It cannot answer “how well is it flowing?” These are fundamentally different questions. A connection moving 100 Mbps with 3% packet loss and 60ms of jitter is objectively terrible for a video call, but Activity Monitor would show it as a healthy stream of bytes. There’s no status indicator, no quality score, no threshold-based alerting.

Side-by-Side: The Same Network Problem in Both Tools

Imagine this scenario: you’re on a video call. Audio keeps cutting out. The other person’s face freezes every few seconds. You open Activity Monitor to investigate.

The underlying problem is 3% packet loss combined with 45ms of jitter, more than enough to wreck any real-time application. Here’s what each tool shows:

Same network. Same moment. Same problem. Completely different levels of insight. Activity Monitor sees data moving and reports success. Healthy Network sees data arriving late, out of order, and with gaps, and tells you exactly what’s going wrong.

When Activity Monitor Is the Right Tool

Activity Monitor isn’t a bad tool. It’s a bandwidth tool being asked to do a quality job. For the questions it is designed to answer, it’s excellent:

• Identifying bandwidth hogs. Dropbox syncing 50 GB in the background? Time Machine backing up to a network drive? Activity Monitor shows you exactly which process is consuming your upload bandwidth.
• Catching unexpected uploads. If an app is sending data you didn’t expect, the per-process byte counters make it obvious. This is valuable for both performance and privacy.
• Verifying active transfers. When you’re downloading a large file and want to confirm it’s actually progressing, the throughput graph provides real-time confirmation.
• Monitoring total throughput. If you need to know how much data your Mac is sending or receiving right now, Activity Monitor gives you the answer instantly.

For all of these use cases, Activity Monitor is the right tool. The problem arises only when you try to use it for something it was never designed to do: assess connection quality.

When You Need More

Throughput data isn’t enough when the question shifts from “how much?” to “how well?” You need quality metrics when:

• Before, during, and after calls. Checking connection quality before joining an important meeting means you can switch to Ethernet or troubleshoot before the call starts, not after it’s already fallen apart.
• Diagnosing intermittent issues. “It was fine 5 minutes ago” is one of the hardest problems to debug. Without historical data, you’re left guessing. Continuous monitoring with trends catches patterns that point-in-time checks miss.
• Understanding why it’s slow. “My internet is slow” has many possible causes. Is it latency? Packet loss? Jitter? Bufferbloat? Each has different solutions. Specific metrics lead to specific fixes.
• Monitoring trends over hours or days. ISP throttling during peak hours, Wi-Fi degradation when neighbors come home, interference patterns that correlate with specific times. These only become visible with persistent historical data.
• Getting actionable information. Not just “something is wrong” but “your jitter is 42ms, which exceeds the 15ms threshold for stable video calls.” Specific numbers enable specific conversations with your ISP or IT team.

What About the Built-In Terminal Tools?

Activity Monitor isn’t the only tool macOS ships with. Before reaching for a third-party app, it’s worth knowing what’s already available in Terminal, and where each tool falls short.

networkQuality (macOS 12+)

This is the strongest built-in option. Run networkQuality -v in Terminal and it measures download capacity, upload capacity, RPM (Round-trips Per Minute, a measure of latency under load), and idle latency. It’s essentially an Apple-hosted speed and responsiveness test.

However, it’s a one-shot test that runs for about 12 seconds and then stops. It does not measure jitter. It does not report packet loss as a discrete metric. It has no GUI, no menu bar presence, no alerts, and no saved history. And because it’s essentially a speed test, it generates significant network traffic during the test, making it unsuitable for background monitoring. You wouldn’t run it during a call.

ping

The classic. Run ping 1.1.1.1 and you get round-trip latency to a specific host, plus a packet loss percentage in the summary. It’s quick, it’s free, and it works.

But it requires Terminal, reports no jitter (only standard deviation, which is a rough proxy), has no GUI, and the user must know to run it at the right time. Leaving a ping running in a Terminal window is possible but impractical. It produces raw text with no visualization, no thresholds, and no alerts.

Wireless Diagnostics (Option-click Wi-Fi Icon)

This shows Wi-Fi signal strength, channel information, noise levels, and interference from neighboring networks. Useful for diagnosing link-layer Wi-Fi problems, but it measures the wireless link only, not end-to-end network quality to internet hosts. Your Wi-Fi signal can be perfect while your ISP connection is degraded.

Network Utility

This app provided a GUI for ping, traceroute, and other network tools. It was deprecated in macOS Big Sur (2020) and has been fully removed. It is not available on Sonoma or Sequoia.

The Common Limitation

Every built-in tool is either a one-shot snapshot or requires an open Terminal window and manual interpretation. None provide continuous passive monitoring. None save historical data. None sit in your menu bar. And none measure jitter, the metric that matters most for real-time application quality.

Here’s how they compare:

Each built-in tool serves a purpose. networkQuality is great for a quick gut-check. ping is indispensable for targeted troubleshooting. Wireless Diagnostics helps with Wi-Fi channel planning. But none of them replace continuous, passive, always-on quality monitoring.

How Healthy Network Fills the Gaps

Healthy Network was built specifically for the question Activity Monitor can’t answer: how well is my connection performing right now, and how has it been performing over time?

• Always-on menu bar monitoring. No window to keep open. A glance at the menu bar tells you whether your connection is healthy, degraded, or failing: green, yellow, or red.
• Three core quality metrics. Latency, packet loss, and jitter, updated continuously with tiny TCP probes that consume negligible bandwidth.
• Threshold-based status. You set the thresholds for your use case (gaming, video calls, browsing) and the app tells you when conditions cross them. No mental math required.
• Path diagnostics. When something goes wrong, Healthy Network isolates the problem to a specific segment: Mac → Router → Internet. Is the issue your Wi-Fi, your router, or your ISP? The answer is one click away.
• Historical sparklines and dashboard. See the last 24 hours of quality data at a glance. Correlate “my call was bad at 3 PM” with actual metrics from that time. Spot patterns like evening degradation or periodic spikes.
• Diagnostic reports. Generate a shareable report with timestamped data to send to your ISP, IT team, or anyone who can help. Concrete numbers are more persuasive than “it feels slow.”

The Complementary Workflow

The best approach isn’t choosing one tool over another. It’s using each for what it does best:

Here’s how they work together in practice: Healthy Network’s menu bar turns yellow during a call. You open the popover and see latency has spiked to 150ms with bufferbloat detected. You open Activity Monitor and find Dropbox is uploading 2 GB in the background. You pause the sync. Healthy Network turns green. Problem identified, diagnosed, and resolved, with each tool contributing the piece of information it’s uniquely suited to provide.

Activity Monitor told you what was consuming bandwidth. Healthy Network told you how that bandwidth usage was affecting your connection quality. Neither tool alone had the full picture. Together, they gave you a complete diagnosis in seconds.

For more on menu bar tools that help remote workers stay connected, see our broader roundup of connectivity monitoring options.

Frequently Asked Questions