IPASK in numbers
Counters from our own logs. They are not audited by a third party — we publish them because the alternative is telling you nothing.
Usage
Checks = requests to /api/v1/lookup and /api/v1/verify, from server access logs. Batch rows are counted per request.
Networks checked most (30 days)
| ASN | Network | Checks | Flagged |
|---|---|---|---|
| AS13335 | Cloudflare | 44 | 0 |
| AS20473 | Vultr | 21 | 21 |
| AS7922 | Comcast | 20 | 0 |
| AS15169 | Google Cloud | 11 | 11 |
| AS60729 | Zwiebelfreunde | 3 | 3 |
| AS8068 | Microsoft Azure | 1 | 1 |
| AS16509 | AWS | 1 | 1 |
| AS45102 | Alibaba Cloud | 1 | 1 |
“Flagged” means the check produced a caution or avoid verdict (hosting, CDN, VPN, Tor).
Most visited pages (7 days)
| Path | Views |
|---|---|
| / | 812 |
| /ip/<ip>/ | 706 |
| /sitemap.xml | 142 |
| /zh/ | 119 |
| /de/ | 110 |
| /ja/ | 109 |
| /pricing/ | 87 |
| /ru/ | 77 |
Accuracy audit
Average match against reference sets: 100% (5 checks, last run 2026-11-01).
- Cloud ranges → datacenter — 100% (60/60)
- Cloudflare ranges → CDN — 100% (15/15)
- DROP ranges → blacklist hit — 100% (50/50)
- Tor exit list → Tor verdict — 100% (50/50)
- Consumer ISP samples → not flagged as hosting — 100% (20/20)
These are consistency checks against public reference data, not marketplace outcomes. Methodology.
Outcome signals (90 days)
1 reports · 1 worked · 0 rejected.
| Platform | Worked | Rejected | Rate |
|---|---|---|---|
| amazon | 1 | 0 | 100% |
Self-reported and self-selected: people who answer are not a random sample. Treat it as a signal, not a measurement.
Corrections
0 verdict disputes received. We re-check each one by hand; corrections are recorded in the changelog.
If a verdict looks wrong, report it — no account needed.