BT-MEDIA

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

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.121.25.144/29 BT-MEDIA RIPE ASSIGNED PA ● low
81.128.198.0/29 BT-MEDIA RIPE ASSIGNED PA ● low
81.131.57.0/29 BT-MEDIA RIPE ASSIGNED PA ● low
81.145.233.72/29 BT-MEDIA RIPE ASSIGNED PA ● low
2a00:2381:36e:4400::/56 BT-MEDIA RIPE ASSIGNED ● low
2a00:2381:2912:200::/56 BT-MEDIA RIPE ASSIGNED ● low
2a00:2381:2912:300::/56 BT-MEDIA RIPE ASSIGNED ● low
2a00:2381:2912:800::/56 BT-MEDIA RIPE ASSIGNED ● low
2a00:2381:ecc6::/48 BT-MEDIA RIPE AGGREGATED-BY-LIR ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “BT MEDIA” — 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 (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE