symptomsd, the daemon that takes your Mac's network pulse
symptomsd tracks your Mac's network health, the machinery behind the Wi-Fi Recommendations menu. Measured on a real Mac: 50,000 log lines a day of radio telemetry.
By Chethan Kumar S N · Updated
Every daemon in this series gets measured by the same ruler. Processor time, memory, the doors it opens, the words in its manual. symptomsd breaks the ruler in a way no previous entry has: it is the thinnest daemon measured so far, three binaries that are almost entirely hollow, 49 strings in the main one, and yet its log is the second chattiest in the series at 50,726 lines in a single day. The code is a stub. The words are all measurements. That inversion is the whole story of this daemon, because a symptom is not a thing, it is an observation, and this is the process your Mac pays to make observations about its own network.
The name is a medical metaphor, and it is a good one. A doctor does not install anything in you. A doctor watches, measures, compares against a baseline, and only then says something is wrong. That is precisely this daemon’s job description.
The manual says almost nothing, twice, eight years apart
macOS ships symptomsd with a real manual page, dated February 14, 2017, and the whole description is two sentences:
symptomsd is a daemon that provides services for the Symptom Framework.
There are no configuration options to symptomsd. Users should not run symptomsd manually.
The sibling binary, symptomsd-distributed, has its own manual page, dated January 31, 2025. It is the same name line and the same two sentences with the name swapped, word for word. Somebody at Apple opened the original manual, copied it, changed one word, and shipped it eight years later. The third binary, symptomsd-diag, has no manual page at all. The gap between those 302 byte manuals and what the daemons actually do is the rest of this page.
What a symptom is, in Apple’s own words
Apple never puts the word symptomsd in front of a customer, but the feature it feeds is one you have probably seen. When your Mac detects a problem with its Wi-Fi, the Wi-Fi menu in the menu bar offers help, and Apple’s Mac User Guide describes it plainly: “If Wi-Fi issues are detected on your Mac, you can view the issues and suggested solutions. Click in the menu bar, then choose Wi-Fi Recommendations.” The same page notes the limits: “Wi-Fi recommendations aren’t available for enterprise networks or Personal Hotspots.”
Detected by what? Something has to notice that pages are loading slowly, that the signal is degraded, that connections are dropping, before any menu can offer anything. The deeper tool in the same guide, Wireless Diagnostics, is asked to “analyse the network’s connection to the internet”, after which “you get a list of detected issues and possible solutions, and information about Wi-Fi best practices”, and it is careful to add that “Wireless Diagnostics doesn’t change your network settings.” Analysis, detection, recommendations, no changes made. That is a doctor’s chart, not a surgeon, and the machinery for taking the pulse is this framework family.
The framework family is worth seeing in one list, because its shape is the job description. macOS 27 carries eight sibling frameworks with Symptom in the name, covering reporters, distribution, link advisories and network diagnostics, plus the umbrella Symptoms framework with five more inside it, for analytics, evaluation, presentation feeds and managed events. The presentation frameworks are the tell. A symptom nobody presents is just a log line.
Measured on a real Mac
The numbers below were measured read only on a MacBook Pro with Apple silicon running macOS 27.0.1, 26 days and 23 hours after boot.
| Measurement | Value |
|---|---|
| Process ID, parent | 556, parent 1 (launchd) |
| User | _networkd, the “Network Services” account, uid 24 |
| Uptime | since boot, never exited, runs = 1 |
| Processor time | 50:02.59 total, about 1m 51s a day |
| Memory | 8,000 to 9,264 KB across three samples |
| Binary | /usr/libexec/symptomsd, 189,856 bytes |
| Architectures | x86_64, arm64e and arm64e.x1, Intel slice still present |
| Code signature | com.apple.symptomsd, platform identifier 26 |
| Strings in binary | 49 |
Three of those rows deserve a sentence each. The reserved account is the same pattern as the location daemon’s: a real user that exists only for this job, so the daemon holds no privileges of yours. The wandering memory footprint is the healthy pattern, not a leak, because the launch job sets EnablePressuredExit and the system takes memory back whenever the daemon goes quiet. And 49 strings is a series low by a wide margin, because the binary is deliberately hollow. It links exactly one framework, the evaluator, version 2394.0.4, and the code for that framework is not even on disk: like all modern system frameworks it lives in the dyld shared cache, and the on disk copy holds nothing but resources and a signature. The daemon you can see is a doorway into a library you cannot read.
Three processes, one job
The confusion in Activity Monitor is structural, because the symptom machinery ships as three separate binaries, all in /usr/libexec, all signed the same way:
| Process | Runs as | What it is |
|---|---|---|
| symptomsd | _networkd | the collector and evaluator, this page |
| symptomsd-diag | root | the diagnostics pipeline, uploads under strict gates |
| symptomsd-distributed | you | an on-demand agent, launched by notification |
The distributed agent had run zero times since login on the Mac measured here, waiting on a notification that never came. The diag daemon had launched 23 times since boot, roughly one maintenance window a day plus extra passes, and its last exit reason was JETSAM_REASON_MEMORY_IDLE_EXIT, the system reclaiming an idle process on purpose. The main daemon has never exited at all.
The doors it opens
The launch configuration, read from its own property list, says a lot for 30 lines of text. It advertises three Mach services to the system, symptom analytics, managed events, and one named usymptomsd, plus a fourth registered on host special port 27 for resource notifications. Those are the doors other processes knock on to ask what the network’s health is.
How it wakes up is the more interesting half. It asks notifyd to be told every time the network changes state, and it asks distnoted to be told whenever Launch Services registers or unregisters an application, because an app appearing or disappearing changes what flows it should expect to see. It also watches one file path, /Library/Preferences/com.apple.symptoms.plist, which is the one configuration file the manual pretends does not exist. On the Mac measured here that file does not exist either, which is the most Apple sentence on this page: the documented configuration options are none, and the undocumented configuration file is absent.
One day of its log, counted
The single richest source for what this daemon does is its own output. One day, all three processes, 50,726 lines, sorted by the tag each line carries:
| Tag | Lines | What it was doing |
|---|---|---|
| bbh | 23,452 | TCP flow metrics and scoring |
| rnf | 10,652 | layer 2 radio measurements |
| netepochs | 6,346 | link quality state changes |
| noi | 1,211 | networks of interest bookkeeping |
| analytics | 1,114 | the analytics store |
The daemon never expands those tags. But the lines under them are pure, quotable telemetry. Under the radio tag, this is the daemon checking the airwaves on the main interface:
L2 Metrics on en0: rssi: -45 [-1,-1] -> -45, snr: 17 (cca [wake/total] self/other/intf): [0,0]/[1,1]/[1,1]/3 (txFrames/txReTx/txFail): 168/35/0
Signal strength, signal to noise ratio, channel clearance counts, transmit retries. A line like this appeared thousands of times in a day, along with the radio type, 802.11ax, and the running averages of transmit and receive rates. Under the TCP tag, this is a 30 second health check of every connection on the machine:
TCP metrics iteration:553 since 30.00 secs: allflows=54/C=0/R=0/W=0/flows=4/unacked=0/rxbytes=59845/txbytes=29222
Fails, retransmits, unacknowledged packets, bytes each way. And every batch ends with a verdict, a line reading “TCP progress metrics score: 0, problem ratio: 0.00 (baseline: 0.00)”. Score against baseline. The doctor’s chart again, written every 30 seconds.
The shape of the day matters more than the total. The four hours between 2am and 6am, when the Mac measured here was asleep with the lid closed, produced zero lines. The busiest hour, 8pm, produced 4,749. One mid-morning hour produced 53, because the lid was closed then too. This daemon does not tick. It reacts.
It knows your apps by name
The most surprising census in this series so far: the flow watcher inside this daemon logs process names, with bundle attribution, whenever a network flow behaves unusually. One day, counted by process:
| Process | Lines | Attributed to |
|---|---|---|
| acumbrellaagent | 226 | com.cisco.secureclient.vpn.service.agent |
| mDNSResponder | 151 | the system resolver |
| Comet Helper | 8 | ai.perplexity.comet |
| CopperRiver | 4 | the assistant this site is written by |
| Slack, Claude, Chromium, dnscryptproxy | 2 or fewer each | assorted apps |
A sample line, verbatim: “Unexpected UDP local port on flow 24390673 for process acumbrellaagent attributed com.cisco.secureclient.vpn.service.agent, was 0.0.0.0:0 now 0.0.0.0:59771”. That is a VPN agent rebinding a UDP socket, noticed, attributed and written down. Another line catches a browser helper sending a DNS query to the router, remote endpoint 192.168.1.1:53, and names the bundle that did it. Nothing here is content. It is pattern of life: which process, which endpoint, which change. If you have ever wondered how macOS can pop up a sensible “this app is using your network” style fact, this is the layer that knows.
One entry in that table deserves a confession. CopperRiver, the assistant that measured all of this and wrote this page, appears in the symptom log four times, for four network flows it opened while doing the research. The observer was observed.
The half that can phone home, and its leashes
The root daemon, symptomsd-diag, is the part of this story with privacy stakes, so its configuration deserves quotation rather than paraphrase. Its property list schedules four maintenance activities with CloudKit, and every one of them carries the same gates: AllowBattery false, RequireScreenSleep true, and where transfer matters, RequireInexpensiveNetworkConnectivity true and prohibit_constrained true, meaning metered connections are refused. Transfer sizes are capped, 10 MB for the main pipeline passes and 1 MB for the statistics report, on intervals of four hours to a day.
More telling is what the daemon itself said at startup on the Mac measured here, in its own log: “AutoBugCapture is OFF - DNU:0, DP:enabled”, followed by “Unregistering periodic CloudKit upload activity” and “Unregistering CloudKit submission activity”. The upload pipeline exists, is scheduled, and then stands itself down on a machine where the feature is off. That is the honest description of this half of the daemon: a courier that is employed, equipped, and currently sitting in the depot.
Try it yourself
Two read only commands, no administrator rights needed. The live link quality score for your main interface, from the same state store this daemon subscribes to:
$ scutil <<< "show State:/Network/Interface/en0/LinkQuality"
<dictionary> {
LinkQuality : 50
}
And one hour of the daemon’s own measurements:
$ log show --last 60m --predicate 'process == "symptomsd"' --style compact | wc -l
If your Mac has been busy on Wi-Fi, expect thousands. If it has been asleep, expect none. Both answers are correct.
Apple never names it
The hedge at the end of every page in this series, verified again for this one: across the Mac User Guide pages that describe Wi-Fi Recommendations and Wireless Diagnostics, fetched in full for this page, the word symptomsd appears zero times. Apple documents the diagnosis and never names the doctor. The user guide will tell you to open the Wi-Fi menu and read the recommendations, will hand you an analysis tool that writes a compressed diagnostics file into /var/tmp whose name starts with WirelessDiagnostics and ends in .tar.gz, a folder that was empty on the Mac measured here because nothing has gone wrong, and will do all of it without ever admitting there is a daemon taking the pulse. Which is, arguably, the correct amount of naming. A symptom is only useful if somebody is watching. Now you know who.
- What Is mDNSResponder on Mac?, the resolver whose flows appear in this daemon’s log 151 times a day, from the other side
- What Is configd on Mac?, the daemon whose dynamic store holds the LinkQuality keys this daemon subscribes to
- Why is my Mac running so slow?, where this daemon joins the measured list of background processes, and what its bursts mean
- What Is nsurlsessiond on Mac?, the other daemon that watches network flows, one URL request at a time
Questions
What is symptomsd on Mac?
It is the daemon that collects what Apple calls symptoms, meaning measurements of network health: Wi-Fi signal strength and noise, link quality on every interface, and per-flow statistics for the apps using the network. Its manual names it the Symptom framework service daemon, and it runs as the reserved user _networkd, the account macOS keeps for network services. On the Mac measured here it used about one minute and 51 seconds of processor time a day and wrote roughly 50,000 log lines, nearly all of them radio and TCP measurements.
Why is symptomsd using so much CPU?
On the Mac measured here, it was not. 50 minutes and 2 seconds of processor time across 26 days and 23 hours of uptime works out at about one minute 51 seconds a day, around a tenth of one per cent of a single core. The work comes in bursts tied to network activity: its busiest measured hour wrote 4,749 log lines and the hours the Mac spent asleep wrote none at all. If Activity Monitor shows symptomsd genuinely pegged for a sustained period, look at the network first. A flapping Wi-Fi link, an interface cycling up and down, or a VPN changing routes will each wake it repeatedly, and its log names the interface and the reason every time. One naming trap while you are in that tab: the row doing the counting underneath everything is [sysmond](/guides/sysmond-mac), the daemon that gathers the per-process statistics Activity Monitor displays, so if a daemon called sysmond is busy, that one is a separate page.
Is symptomsd spying on my network traffic?
It watches flows, not content. Its log lines record process names, bundle identifiers and IP endpoints, for example a UDP flow for mDNSResponder or a helper attributed to a VPN agent, but nothing about what is sent. The privacy posture is visible in its own output: 1,964 lines in a day were redacted to the marker private, including the name of the Wi-Fi network itself in the daemon's own local log. The separate root daemon that can upload diagnostics, symptomsd-diag, reported AutoBugCapture is OFF on this Mac and unregistered its CloudKit upload activities, and its scheduled uploads are gated to run only on power, while the screen is asleep, and on an inexpensive connection.
What are symptomsd-diag and symptomsd-distributed?
They are the other two binaries in /usr/libexec. symptomsd-distributed is the user side agent, launched on demand by a notification, with its own manual page dated January 31 2025 that repeats the main daemon's text word for word. It had run zero times on the Mac measured here. symptomsd-diag is a root daemon for the diagnostics pipeline: it had launched 23 times since boot, roughly once per maintenance window, and its last exit was the friendly kind, idle memory reclaim. It is the only one of the three with no manual page at all.
Can I quit or disable symptomsd?
There is no supported way and no reason to want one. The manual says there are no configuration options and users should not run it manually, there is no row for it in System Settings, and its memory is reclaimed on demand through pressured exit, which is why its footprint moved between 7.6 and 9.3 MB across three measurements on an idle Mac. The one file it watches for settings, /Library/Preferences/com.apple.symptoms.plist, did not even exist on the Mac measured here. The real switches are the features around it: the Wi-Fi Recommendations menu it feeds, and the Analytics and Improvements settings that govern the diagnostic half.
Ready? Buy Ribbon for $15, or read all the guides.