A one-shot, no-UI CLI that captures live traffic and figures out whether your slowdown is your ISP, your own device, or one flaky destination — with its reasoning shown, not a black-box score.
capture + report
need no payment and no account. The one-shot paid-report command
— capture, analyze, and get a report in a single call, mainly built for
automation and agents — is $5 by card, no wallet or crypto
required, or payable with E3D Token if you already hold it.
npm install -g e3d-netdoctor e3d-netdoctor preflight e3d-netdoctor capture en0 30 e3d-netdoctor report ./capture.pcap
Full source, docs, and the --card/--wallet paid flow:
github.com/spacepacket1/e3d-netdoctor
Every network engineer and Wireshark user has had this conversation: “Is it my wifi, or is it Comcast again?” That question is answerable from a single packet capture — if you know to group retransmissions and RTT outliers by destination and by local device, and weigh provider diversity instead of raw destination count. Most people don't do that math by hand. netdoctor does, every time, and shows its work.
| Verdict | Means |
|---|---|
| Likely Upstream/ISP | Signal spread across many unrelated destinations and providers — not one device |
| Likely Local | Signal concentrated on one local device (MAC) across many destinations — bad wifi, flaky NIC, bad cabling |
| Likely Destination/Path-Specific | Signal confined to one or two destinations while everything else is clean |
500 credits = 1 paid-report run. Pay with a card below, or use
e3d-netdoctor paid-report --card from the CLI directly — same
checkout, no browser round-trip needed.