Accuracy & methodology
Every number on this page is computed live from the same database that serves every lookup — nothing here is a marketing snapshot. The methodology behind it is on the data page.
Clustering benchmark
A hand-audited set of 78 labeled pairs of real registry records — pairs that must belong to the same organisation, and adversarial pairs that must never be merged (name collisions like Virgin Media vs Virgin Atlantic, national operating companies of shared brands, carriers vs their customers). The clustering output is scored against every label on every request; each label was added after a real investigation, and any algorithm change that regresses one blocks release.
8 labeled cases currently failing — fixes are validated and applied at the next weekly recluster. Shown rather than hidden: this page reports the live state, not the best week.
Independent corroboration
Attribution checked against ranges major cloud/CDN providers publish about themselves — external ground truth we didn't infer, re-checked every pipeline run.
| Provider | Blocks | Correctly attributed |
|---|---|---|
| microsoft | 59,933 | 100.0% |
| aws | 10,815 | 100.0% |
| github | 7,788 | 100.0% |
| 1,144 | 100.0% | |
| oracle | 1,089 | 100.0% |
| cloudflare | 22 | 100.0% |
| fastly | 21 | 100.0% |
Global coverage
Address-weighted share of all delegated IPv4 space, per attribution confidence — the full per-registry table (including IPv6 and the honest "not indexed" column) is on the data page.
What we deliberately don't claim
No public dataset can attribute literally every IP address — unregistered, unrouted, and carrier-NATed space is invisible to everyone. Where our evidence is an inference (a block attributed to its announcing carrier) rather than a registry record, it is labeled as such on every page and counted separately above. Ranges related to an organisation without merge-grade evidence appear in a separate "possibly related" section on its page, never in its own footprint.