WILLIAM-KING

Data as of 2026-09-27
BGP inherited
This organisation
Netblocks7
IPv6 2 prefixes (largest 2a00:2381:115::/48)
Also registered under this name 8 netblocks across 2 separate records
Record ID246025129
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.7.75.128/28 WILLIAM-KING RIPE ASSIGNED PA ● low
80.195.36.112/28 WILLIAM-KING-LTD RIPE ASSIGNED PA ● low
81.131.50.240/28 WILLIAM-KING RIPE ASSIGNED PA ● low
194.72.156.64/28 WILLIAM-KING RIPE ASSIGNED PA ● low
217.33.20.16/28 WILLIAM-KING RIPE ASSIGNED PA ● low
2a00:2381:115::/48 WILLIAM-KING RIPE AGGREGATED-BY-LIR ● low
2a00:2381:115:100::/56 WILLIAM-KING RIPE ASSIGNED ● low

IPv6 ranges (2)

Footprint over time

14 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-09-27

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS5089-MNT BTNET-MNT DUMY-RIPE DUMY-RIPE