OFCOM

BGP inherited
Cluster stats
Netblocks10
All fragments 12 blocks across 3 clusters
Cluster ID208888192
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.254.155.240/29 OFCOM RIPE ASSIGNED PA ● low
80.195.119.160/27 OFCOM RIPE ASSIGNED PA ● low
81.187.216.200/32 OFCOM RIPE ASSIGNED PA ● low
90.155.54.0/28 OFCOM RIPE ASSIGNED PA ● low
90.155.54.16/32 OFCOM RIPE ASSIGNED PA ● low
90.155.54.20/32 OFCOM-LTD RIPE ASSIGNED PA ● low
90.155.54.21/32 OFCOM-LTD RIPE ASSIGNED PA ● low
213.104.197.168/29 OFCOM RIPE ASSIGNED PA ● low
217.34.130.160/28 OFCOM RIPE ASSIGNED PA ● low
217.40.119.40/29 Ofcom RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “OFCOM” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

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