Network diagnostics on Mac with built-in utilities

  • macOS integrates multiple network diagnostic tools, although many are hidden in System Settings, special menus, and Terminal.
  • Wireless Diagnostics and its channel scanner allow you to thoroughly analyze Wi-Fi, detect interference, and generate comprehensive reports for support.
  • The classic commands (ping, traceroute, dig, netstat) and networkQuality cover advanced diagnostics, but without a centralized graphical interface like the old Network Utility.
  • Third-party apps fill the gaps with more user-friendly interfaces, port scanning, and persistent monitoring for more demanding uses.

Network diagnostics on Mac

If you use a Mac and your connection is choppy, macOS's own built-in utilities They can help you more than you might think. You don't need to install anything unusual to have a good suite of tests: Apple includes graphical assistants, hidden tools, and Terminal commands capable of analyzing everything from your home Wi-Fi to a more complex network with routers, switches, and servers.

The problem is that, although the tools are there, Many are hidden and not at all intuitive to find.Some have disappeared as standalone apps, others only exist in the command line, and still others are buried in menus that no one ever opens. Let's take a systematic look at everything macOS offers for network diagnostics with its built-in utilities, what's missing compared to what was available before, and how to fill those gaps when you need to go a little further.

Basic network status in macOS: where to start

Before diving into advanced tests, it's advisable to review the general network settings of your Mac and connection statusMany problems can be solved by checking a couple of basic settings.

In current versions of macOS, the gateway is System Configuration (or System Preferences in earlier versions)From the Network panel you can see:

  • Whether you are connected via Wi-Fi, Ethernet, or another type of interface.
  • The IP address that you have been assigned.
  • The general status of the connection (connected, disconnected, auto-configured, etc.).
  • In Wi-Fi, the network you are connected to and the basic signal strength.

Furthermore, in older macOS versions, the famous [unclear] appeared on that same screen. colored “traffic lights” next to each network serviceGreen indicated everything was working correctly, yellow indicated a configuration problem, and red indicated no connection. It was a very visual way to understand at a glance whether the Mac was connected to the internet or not.

You also have integrated configuration and diagnostic wizardsIn Network preferences, there's usually a "Wizard" button or something similar that launches two types of help: one for setting up new connections and another specifically for diagnosing problems when something goes wrong. They're not magic, but for home use, they resolve many DNS issues, gateway problems, or misconfigured networks.

If your problem is related to Wi-Fi, the menu in the top bar also provides clues. Pressing the Wi-Fi icon while holding down the Alt (Option) keyAdditional technical information appears: network name, channel, bandwidth, RSSI (signal strength), noise, security mode, and other parameters that are very useful for diagnosing interference or poor coverage.

Wireless Diagnostics: The Hidden Tool of Wi-Fi

For everything related to wireless networks, macOS includes a powerful but rather hidden utility: Wireless DiagnosticsYou won't see any icon in the Applications folder, but it's there.

The quickest way to open it is to hold down the Option key and Click on the Wi-Fi icon in the menu barIn the drop-down menu, you'll see the option "Open Wireless Diagnostics…". Selecting it will launch a wizard that guides you step-by-step through analyzing Wi-Fi and internet connection problems.

When your Mac connects to the Wi-Fi router but You can't load pages, email fails, or streaming keeps cutting out.This utility analyzes the situation and runs a battery of automated tests. Upon completion, it generates a report with:

  • List of problems detected (e.g., weak signal, interference, unresponsive DNS, etc.).
  • Specific recommendations to solve them (change the channel, move the Mac closer to the router, modify router settings, etc.).
  • General best practices for using a more stable Wi-Fi connection.

In addition to the assistant, Wireless Diagnostics includes advanced tools hidden in your Window menu which many users don't even touch, but which are pure gold:

  • Wi-Fi ScannerThis shows all nearby networks, the channel they use, signal strength, and noise. Ideal for seeing if your network shares a channel with too many neighbors.
  • Performance monitorA real-time graph showing Wi-Fi performance, signal quality, and fluctuations. It's useful for checking how the connection changes if you move around, change the router's antenna, or adjust the channel.
  • Sniffer (packet capture)This feature allows you to capture raw wireless network traffic for later analysis with tools like Wireshark. It's an advanced function, intended for administrators or people who already know what they're looking at.

While performing the analysis, the utility generates a compressed file with all the technical details of the diagnostic sessionThat file is saved in the folder /var/tmp It usually starts with “WirelessDiagnostics” and ends with “.tar.gz”. It’s perfect for sending to a network administrator, your ISP’s technical support, or a tech-savvy colleague to calmly review the problem.

If you want to locate the file easily, open Finder, Click the face icon in the Dock, then go to Go > Go to Folder. Writes /var/tmp and press Enter: the folder where the diagnostic file is located will open directly, ready to attach or archive.

Wi-Fi Channel Scanner on Mac: Why It Matters So Much

One of the main culprits behind a choppy Wi-Fi connection is the use of a channel saturated by too many neighboring networksThis happens especially in the 2,4 GHz band, which is still the most used in many apartments and apartment blocks.

To understand this, imagine that Wi-Fi channels are lanes of a highwayIf all the cars (all the neighbors' networks) travel in the same lane, traffic becomes slow and sluggish. In the 2,4 GHz band, many countries only have 11 channels, and of those, only 3 don't overlap (1, 6, and 11). The rest overlap and generate cross-interference that drastically reduces your speed.

In the 5 GHz and 6 GHz bands things improve considerably because There are many more channels available in different widths (20, 40, 80, and even 160 MHz). In practice, these frequencies result in less interference between networks, and most modern routers can automatically select a fairly decent 5 or 6 GHz channel without you having to change any settings.

Even so, if you want to get the most out of your network, channel planning is key. For that, you need a wireless channel scanner ask them to tell you what networks are around, what channel each one uses, and with what power.

macOS includes a basic scanner built into Wireless Diagnostics. By opening the utility and using the corresponding option in the window menu, you can See at a glance nearby networks and the channel each one uses.It's not the prettiest interface in the world, but it does the job: detecting if your router is sharing a channel with four or five other networks, or if there's a less congested channel you can choose in the router's settings.

For more demanding users, there are third-party apps with more user-friendly interfaces and more comprehensive analysiswith channel occupancy graphs, signal histograms, etc. But if you just want to know if your channel is congested, the built-in macOS functionality is more than enough.

Network Utility: what it did and why it's no longer around

For years, macOS (and before that Mac OS X) included a graphical application called Network UtilityIt was the Swiss Army knife of basic diagnostics: in a single window you had buttons to launch Ping, Traceroute, Lookup (DNS search), Whois, Netstat, port scanning, and even Finger.

For users who wouldn't touch Terminal even if they were paid, It was a very convenient way to type in a domain or IP address and press a button This app was used to check if a server was responding, to see the path to a destination, or to view domain registration information. It was also widely used in professional environments, for example, to diagnose connectivity between workstations and license servers, similar to how Rhino for Mac used Zoo.

You could find it with Spotlight by typing "Network Utility" and Open it like any other application.From there, quick tests were performed when shared services were acting strangely, when you wanted to check if a port was open on a router or if a DNS was resolving correctly.

The problem is that, with the arrival of macOS Big Sur, Apple marked Network Utility as obsoleteThe app disappeared from the usual route, and although it continued to exist for a while in /System/Library/CoreServices/ApplicationsIt no longer contained the tools: when you opened it, it invited you to use other system apps, such as Wireless Diagnostics, and little else.

None of the background functions have disappeared from the system: All the network commands are still there in TerminalWhat Apple has done away with is the unified graphical interface, forcing users to jump to the command line or look for third-party solutions if they want something similar to the old experience.

Terminal Tools in macOS: The Classic Arsenal

Beneath the pretty interface, macOS is still a Unix-like system, and that means that It comes standard with a lot of veteran network utilities that administrators have used for decades. All of them are available from the Terminal app.

Among the most important integrated tools are:

  • pingping: Checks if a host is reachable and measures the round-trip time (latency). If you suspect your internet connection is poor, pinging a reliable domain will tell you if there is packet loss or very high latency.
  • tracerouteThis shows the path that packets take to reach a destination, hopping through the various intermediate routers. It is key to pinpointing where in the route a problem is occurring.
  • netstatIt displays active connections, listening ports, routing tables, and various statistics. It's very detailed, but without filters, it can generate a considerable wall of text.
  • nslookup y youThey allow you to perform low-level DNS queries to see how a domain name resolves, which servers respond, which records are returned, etc.
  • whois: retrieves domain registration information, such as owner, dates, DNS servers, and other public data.
  • nc (netcat): a network Swiss Army knife capable of connecting to ports, sending and receiving data, and even performing basic port scans.

These tools are incredibly flexible and powerful. The drawback is that For a user who is not used to the command line, they can be intimidating.The output is plain text without embellishments, and you need to know which parameters to use, and how to interpret times, paths, and error messages.

Even though Network Utility is gone, Everything I did is still possible with these commandsIf you only need to perform occasional tests (a ping, a quick traceroute), a couple of learned examples will suffice. But if you want a more user-friendly experience or need to consolidate many functions in one place, that's when third-party apps come into play.

NetworkQuality: Measure the real quality of your connection on macOS

With macOS Monterey, Apple quietly added a new tool that It doesn't appear in any menu, but it comes pre-installed on all modern Macs.: the command networkQualityIt is designed to measure the “quality” of the internet connection, not just the raw speed.

By simply typing networkQuality In Terminal, pressing Enter launches a series of tests that measure:

  • Upload capacity: something like your effective upload bandwidth.
  • Download capacity: equivalent to the effective download bandwidth.
  • Upload and download flows: number of test flows used to evaluate the connection.
  • Responsiveness, measured in RPM (round-trips per minute): how many round trips the network can complete per minute under normal load.

The advantage of this tool compared to web services like Fast.com or Speedtest is that Measures rise, fall and response in parallel by defaultTypical online tests usually involve downloading and then uploading sequentially. NetworkQuality, on the other hand, simulates real-world scenarios like a video call or voice chat: you're receiving data (the other person's video) at the same time as you're sending yours (your camera, microphone, or screen sharing).

Thus, responsiveness values ​​are highly relevant to real time applicationsA connection may have high bandwidth but poor performance under load, resulting in dropouts, lag, and poor quality in video calls or online games.

The command also offers a simple classification of connection status with labels like Low, Medium or High for responsiveness, both upload and download, if you run it with the sequential argument -sThis quick view is very useful when you want to know if the network is "acceptable" for intensive use without getting into technical details.

Internally, the tests are done against Apple's content delivery network, using a URL like https://mensura.cdn-apple.com/api/v1/gm/config as reference. They do not replace other tools such as ping or speedtest-clibut they add a diagnostic layer more focused on the actual user experience.

Network Quality and quality testing in iOS and iPadOS

The philosophy of measuring responsiveness is also present in iOS and iPadOSHowever, the process for using it is somewhat more convoluted and is geared more towards developers and field testing.

To evaluate the quality of the Wi-Fi network on an iPhone or iPad using Apple's tools, you need to follow a series of steps:

  • Connect to the specific Wi-Fi network you want to analyze.
  • Log in to the Apple developer portal with your account and go to the Wi-Fi profiles and logs section.
  • Download the “WiFi Performance Diagnostics” profile and Install it from Settings > Downloaded Profile on the device.
  • Once the profile is installed, go to Settings > Wi-Fi, tap the information icon for the connected network and enter the "Diagnostics" section.
  • There, run the "Responsiveness" test.

If you are also a registered developer and have your device prepared using Xcode, then... Settings > Developer Settings You'll also find a similar responsiveness test in the networking section. It's a more professionally oriented approach, but it's based on the same concept of measuring the network under real-world conditions.

What's missing from macOS today in terms of network diagnostics?

Despite all of the above, there are several clear gaps in the current landscape of network diagnostics in macOSApple provides many "raw" capabilities, but has removed or never offered certain features that are important to some users.

One of the most notable gaps is the absence of an integrated graphical app that groups all the classic testsNetwork Utility played that role and, by disappearing, has left many less technical users without a centralized panel where they could perform Ping, Traceroute, DNS queries or port scans with a single click.

There isn't one either. direct and simple replacement for port scanningAlthough you can use nc to manually test specific ports or install utilities such as nmapThere is no pre-installed graphical interface tool that allows anyone to check which services are accessible from outside, or to verify if the firewall and router are configured as they should be.

Another weak point is the results presentationTerminal is practical and powerful, but its plain text output isn't exactly convenient for detecting patterns or quickly interpreting a long traceroute. Viewing 20 hops with varying latencies in list form requires some experience, and an unfiltered netstat can be downright overwhelming.

Finally, a system for integrated persistent monitoringThe tools Apple offers work like snapshots: you run ping, see the results, and that's it; you run networkQuality, get a summary, and you're done. There's no way to continuously monitor network quality, save history, or trigger alerts when something degrades, unless you set up your own custom scripts and logging systems.

When built-in tools aren't enough: third-party options

As is often the case in the Mac ecosystem, The gaps left by Apple are usually filled by third-party developers.Network diagnostics is no exception: there are everything from very simple utilities to wrap Terminal commands with a graphical interface, to complete suites for administration and development.

If you are a user who only needs solve specific problems (To see if a site is responding, or where the route is stuck), a simple utility with a text field and a button above "ping" or "traceroute" is more than enough. There are also apps focused on displaying traceroutes more visually, with maps and diagrams that are easy to interpret without technical expertise.

For those who frequently perform network diagnostics, something is more useful more polished and organizedTools that combine ping, traceroute, DNS lookups, port scanning, and netstat with formatted output, the ability to save results, compare tests, or export data. These are typical in technical support environments, small businesses, or studios that rely heavily on remote servers.

If you manage servers, cloud services, or develop applications that are heavily network-dependent, your requirements increase significantly. You will need The classic set of functions: ping, traceroute, DNS, whois, port scanning, netstat and often, packet analysis with pcap captures. In this area, it is common to supplement the integrated utilities with packages such as nmap, Wireshark, and specific monitoring solutions.

In all these cases, it is worth considering aspects of privacySome tools, especially web-based ones, send your queries and results to external servers for processing. If you're scanning ports on sensitive systems or querying domains you'd prefer to keep private, it's best to use local tools that don't upload data to any external service or collect usage analytics.

Applications have appeared that specifically seek to... Restore what Network Utility did, but with a more modern design.For example, there are solutions that combine Ping, Traceroute, DNS lookup, Netstat, Whois, Finger, and port scanning into a single window, all running locally on your Mac without intermediary servers. Many are written using recent Apple technologies, with fast interfaces and clear tables where the output is presented better than the raw text of Terminal.

Practical example: checking the network between home and studio

Imagine a very common scenario: you have your house with the main router from the provider and, about 50 meters away, a studio connected by Ethernet cable. In the studio you have a small switch connected to a NAS, a Wi-Fi access point (for example an AirPort) and an iMacFrom time to time you notice that the connection to the NAS is slow, that the iMac takes a long time to access the Internet, or that the studio Wi-Fi isn't performing as it should.

With macOS's built-in tools, you can start with something as simple as:

  • Use ping from iMac to NAS to check for packet loss or unstable latency. If the response is consistent and without loss, the problem is most likely not in the local network segment.
  • Launch traceroute from iMac to an external domain To check the route the connection takes from the studio to the internet. If you see long times or drops at an intermediate hop (for example, at your home router), you already have a point to check.
  • Run networkQuality on the iMac To measure the actual responsiveness of that connection, we compare it to the same test performed from a laptop at home. If the response is worse in the studio, the Ethernet link between home and studio may not be in optimal condition, or the switch may be overloaded.
  • If you also use Wi-Fi in the studio, resort to Wireless Diagnostics to scan AirPort channels and performance and see if the signal degrades more than expected.

By combining these tools, even without installing anything else, You can get a pretty accurate idea of ​​whether the bottleneck is in the cable, the switch, the router, or the internet connection itself.And if you need to go further (for example, checking specific ports or monitoring for hours), then additional tools would come into play.

macOS, even without the old Network Utility, still offers a solid set of utilities for diagnosing networks, but they are spread across System Settings, hidden menus, and Terminal. The key is knowing where each piece is hidden: basic network status and wizards for the simple things, Wireless Diagnostics for everything Wi-Fi, classic Unix commands for direct testing, and networkQuality to assess how your connection really performs under pressure.With these tools, and by using a third-party app when you want a more convenient or complete view, it is perfectly possible to locate bottlenecks, interference, configuration problems or drops in quality both in home Wi-Fi and in somewhat more complex networks.