KINGS-NET
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 137 blocks across 38 clusters |
| Cluster ID | 192179053 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.72.176.0/22 | KINGS | APNIC | ASSIGNED PORTABLE | ● high |
| 62.245.143.16/29 | KINGS-NET | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:b98::/48 | KINGS-GROUP-LTD | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (1)
These blocks are registered to KINGS-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a00:2381:b98::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
MA1006-AP
MA1006-AP
MAINT-IN-IRINN
MNET-MNT