READING-BOROUGH-COUNCIL
BGP inherited
Cluster stats
Netblocks9
All fragments 19 blocks across 2 clusters
Cluster ID192276376
RegistryRIPE
Customersfind customers using 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

Footprint over time

2 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-06

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.30.161.8/29 Reading-Borough-Council RIPE ASSIGNED PA ● low
62.253.85.48/29 READING-BOROUGH-COUNCIL RIPE ASSIGNED PA ● low
62.255.37.160/29 READING-BOROUGH-COUNCIL RIPE ASSIGNED PA ● low
62.255.244.32/27 READING-BOROUGH-COUNCIL RIPE ASSIGNED PA ● low
81.105.172.64/26 READING-BOROUGH-COUNCIL RIPE ASSIGNED PA ● low
212.250.169.32/28 READING-BOROUGH-COUNCIL RIPE ASSIGNED PA ● low
213.105.79.56/29 READING-BOROUGH-COUNCIL RIPE ASSIGNED PA ● low
213.105.167.184/29 READING-BOROUGH-COUNCIL RIPE ASSIGNED PA ● low
2a00:2381:d0c::/48 READING-BOROUGH-COUNCIL RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (1)

These blocks are registered to READING-BOROUGH-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:d0c::/48 /48 authorized for AS2856 — British Telecommunications PLC

NIC Handles

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