BT-IPVPN
Cluster stats
| Netblocks | 49 |
| All fragments | 5,694 blocks across 915 clusters |
| Cluster ID | 191826915 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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
2 weekly snapshots · JSON
49
0 netblocks since 2026-07-05
2026-07-05
peak 49
2026-07-06
IP Ranges (49)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.6.24.0/22 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 62.6.28.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 62.6.192.0/22 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 62.7.194.0/23 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 62.7.200.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 62.172.240.0/20 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.144.0.0/20 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.144.16.0 – 81.144.21.255 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.144.22.0 – 81.144.27.255 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.144.48.0/20 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.144.111.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.144.124.0/23 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.144.126.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.144.127.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.145.0.0/21 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 81.146.128.0/19 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 212.140.205.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 212.140.213.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.120.68.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.120.150.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.120.151.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.120.153.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.121.40.0 – 213.121.42.255 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.121.49.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.121.72.0/22 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.121.152.0/23 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.121.218.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.121.219.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 213.121.224.0/21 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.105.192/26 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.106.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.107.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.119.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.190.0/23 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.224.0/22 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.228.0/23 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.232.0/22 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.236.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.242.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.249.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.32.250.0/23 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.35.176.0/21 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.36.160.0/20 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.41.178.128/25 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.41.179.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.41.181.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.41.182.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.41.183.0/24 | BT-IPVPN | RIPE | ASSIGNED PA | ● low |
| 217.41.188.0/23 | BT-IPVPN | 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
(49 of 49)
No discrepancies found among checked blocks.
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE