NL-PROSERVE-IPV6-CUST-ID-330

BGP inherited

Cluster stats

Netblocks	1
All fragments	63 blocks across 58 clusters
Cluster ID	206007040
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 3 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
2001:828:102:15::/64	NL-PROSERVE-IPV6-CUST-ID-330	RIPE	ASSIGNED	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “NL PROSERVE IPV6 CUST ID” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Combined view of all 58 name-family clusters →

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Proserve Ipv6 Cust Id 1098 via Signet B.V. sub-allocation
Proserve Ipv6 Cust Id 1060 via Signet B.V. sub-allocation
Proserve Ipv6 Cust Id 186 via Signet B.V. sub-allocation
Proserve Ipv6 Cust Id 322 via Signet B.V. sub-allocation
Proserve Ipv6 Cust Id 750 via Signet B.V. sub-allocation
Proserve Ipv6 Cust Id 752 via Signet B.V. sub-allocation
Proserve Ipv6 Cust Id 583 via Signet B.V. sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE PROSERVE-MNT