Methodology

Source conflict resolution

How conflicting registry, routing, and geolocation signals are handled in a controlled monthly release process.

Why conflicts happen

Internet data sources describe different realities. Registry data describes delegation and ownership. BGP describes what is announced. Geographic references describe place names and hierarchy. These signals can disagree.

Resolution model

Registry context is used for ASN and RIR attribution.
Routing context is used to understand prefix-to-ASN relationships.
Geographic hierarchy is normalized through GeoNames-style country, region, and city identifiers.
Monthly snapshot rules keep output deterministic for a release month.

RIR attribution rule

RIR is derived from ASN registry context, not from the geolocation country. This prevents a network from inheriting a regional registry only because an IP row is geolocated in that region.

Output goal

The goal is not to expose every raw signal. The goal is to publish a coherent, explainable, and stable monthly dataset.