How it works
Breakdown watches the apps and services your Mac is already using, keeps compact health history, and separates failures into Wi-Fi/LAN, ISP path, and App so technical users can move straight to the right layer.
Breakdown derives targets from active app traffic, DNS activity, service endpoints, and local network context. That keeps the target set aligned to what you are actually doing instead of a static list of public hosts.
Lightweight checks build a current picture of reachability, latency, loss, jitter, and freshness. Breakdown uses the least intrusive evidence that can answer the question before reaching for deeper diagnostics.
Evidence is grouped by where the problem starts. The main UI keeps the answer simple, while Details and Explorer show the trace, app endpoint, and graph evidence when you need to inspect the underlying signal.
Trace and endpoint evidence
When a status light isn’t enough, Details and Explorer expose current trace rows, endpoint health, topology summaries, segment history, and graph views across health, latency, jitter, and shift.
Breakdown stores compact local history so intermittent problems remain visible after they pass. Free keeps enough recent history for everyday troubleshooting; Pro expands the depth for recurring incidents and long-running investigation.
Breakdown does most of its work in the background and stays quiet when you are not looking at it. In our tests, normal closed-dropdown monitoring typically uses 0.5-1% CPU.
Evidence Reports package the useful parts into a support-ready artifact: when the incident happened, which domain looked unhealthy, and what trace or endpoint evidence was visible at the time.
View sample report