KENT
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 127 blocks across 44 clusters |
| Cluster ID | 192189654 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 9 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 202.163.8.0/28 | Kent | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 202.163.8.16/28 | Kent | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 84.45.245.192/28 | KENT | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:fe1d::/56 | KENT | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to KENT 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:fe1d::/56 /56 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
AA2573-AP
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
ENTANET-MNT
KK1486-AP
KK1486-AP
MAINT-ARELION-AP
MNT-CITYFIBRE