Durham County Council
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 19 blocks across 9 clusters |
| Cluster ID | 204998475 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 9 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 217.23.224.0/20 | Durham County Council | BGP | ANNOUNCED | ● high |
| 62.252.145.208/29 | DURHAM-COUNTY-COUNCIL | RIPE | ASSIGNED PA | ● low |
| 217.23.224.0/20 | Durham County Council | RIPE | ALLOCATED PA | ● low |
| 2a00:2381:f058::/48 | DURHAM-COUNTY-COUNCIL | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(2 of 4)
Possible discrepancies (1)
These blocks are registered to Durham County Council 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:f058::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
AS15770
AS5089-MNT
BTNET-MNT
DERWENTSIDE-MNT
DERWENTSIDE-MNT
DUMY-RIPE
DUMY-RIPE
ORG-DDC1-RIPE
RIPE-NCC-HM-MNT