BT-CORE

Data as of 2026-08-30
BGP inherited
This organisation
Netblocks9 · 504 IPv4 addresses
Record ID233930041
RegistryRIPE
Customerssee who runs inside 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 · report an issue

Footprint over time

10 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-08-30

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
213.120.208.32/29 BT-CORE RIPE ASSIGNED PA ● low
213.120.208.40/30 BT-CORE RIPE ASSIGNED PA ● low
213.120.208.44/30 BT-CORE RIPE ASSIGNED PA ● low
213.120.208.48/30 BT-CORE RIPE ASSIGNED PA ● low
213.120.208.60/30 BT-CORE RIPE ASSIGNED PA ● low
213.120.208.64/27 BT-CORE RIPE ASSIGNED PA ● low
213.120.208.128/25 BT-CORE RIPE ASSIGNED PA ● low
217.32.180.0/24 BT-CORE RIPE ASSIGNED PA ● low
217.32.248.0/26 BT-CORE RIPE ASSIGNED PA ● 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)
No discrepancies found among checked blocks.

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE