NextDNS · home network block rate
1 JULY 2026 · window -24h
At a glance
- ✅ GREEN — 12.5% of queries blocked (8,610 of 68,657)
- 30d baseline: μ=11.6% across 16 points
- Threshold: ±2σ from baseline flips amber (needs ≥14 data points to activate)
Why this matters
A stable block-rate band means the blocklists are doing roughly the same amount of work day over day. A sudden swing can mean: (a) a blocklist became ineffective (filter not catching what it used to — investigate update cadence), (b) a device is pulling an unusual mix of traffic (new service / compromised app), or (c) overall traffic shape changed (someone came home / left).
Top block reasons in this window
| Reason | Queries |
|---|---|
| Goodbye Ads | 7,295 |
| AdGuard DNS filter | 4,571 |
| EasyPrivacy | 2,380 |
| NextDNS Ads & Trackers Blocklist | 2,143 |
| OISD | 1,620 |
| Native Tracking (Apple) | 379 |
What to do next
- Block rate within expected band. No action needed.
- Scan the top-reasons table for any new entry to add to the mental model.
Generated by dare_nextdns_audit.py --check block_rate
Source:
dare_nextdns_block_rate_2026-07-01.md · Rendered Built with — component scripts
seo_render_html.py— wraps the source.mdin the dash.gf.cx design language (+anchor_enricher.pyfor inline-link promotion & rollover thumbnails)dare_dev_reports_publish.py— bundles the day’s reports into the catalog and ships to dash.gf.cx/reports