Engineering · How a Release Is Built
Multi-source BGP, allocation, geofeed, and active RTT verification pipeline
Every ipscope snapshot is compiled from five independent measurement streams and must beat the active release on a disjoint ground-truth holdout set before promotion.
Signal sources5 streamsBGP, Allocations, Geofeed, rDNS, Active RTT
BGP collectors40+ peersGlobal route collector full-table feeds
Holdout gateAutomatedBlocks regressions before publication
Snapshot swapZero-downtimeAtomic pointer swap with SHA-256 check
5-Stage Compilation Pipeline
Corroborating registration declarations against physical network physics
No single registration table is authoritative for physical geography. Administrative records list corporate headquarters addresses, while operator geofeeds can contain typos or stale announcements. Our compiler cross-examines every claim against active routing and latency measurements.
- 1. BGP & RPKI Ingestion: Full DFZ IPv4 and IPv6 RIB dumps every 15 minutes establish canonical prefix boundaries and origin ASNs.
- 2. Allocation & Registration Normalization: Global internet delegation tables provide declared country and organization lineage.
- 3. RFC 8805 Geofeed Verification: Operator CSV geofeeds are ingested only when authenticated by netblock remarks and RPKI origin validation.
- 4. Active RTT & rDNS Triangulation: Multi-region probe nodes verify that claimed city locations satisfy speed-of-light latency bounds.
- 5. Holdout Quality Gate: Candidate snapshots are scored against verified ground-truth landmarks and VPN exits before atomic promotion.
{
"active_version": "2026-10-27T00:00:00Z.crawl-1793088000000",
"previous_version": "2026-10-26T00:00:00Z.crawl-1793001600000",
"snapshots": [
{
"snapshot_version": "2026-10-27T00:00:00Z.crawl-1793088000000",
"digest": "sha256:9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08",
"ruleset_version": "2026.10.2",
"ipv4_prefix_count": 28410200,
"ipv6_prefix_count": 6912400
}
]
}Signal weighting & conflict resolution
How the compiler resolves disagreements between registry paperwork and active probes.
| Scenario | Declared Signal | Physical Signal | Compiler Resolution |
|---|---|---|---|
| Local ISP broadband | Declared country matches RTT probe country | RTT within 15 ms of regional PoP | location_type: "physical", is_virtual_location: false |
| Cross-border cloud subnet | Allocation registered in US | BGP + 2 ms RTT to Frankfurt PoP | declared: "US", physical: "DE", is_virtual_location: true |
| Global CDN / DNS anycast | Multiple PoPs announce same /24 | Low RTT from 3+ continents simultaneously | location_type: "anycast" |
| Unverified geofeed claim | CSV claims Tokyo | RTT from Tokyo > 180 ms, Amsterdam < 4 ms | Geofeed rejected; physical_country_code set to NL |
Start with 30K free lookups a month.
No card, no trial clock. Upgrade when your traffic does, or download the database when you would rather keep it in-house.