BT IP VPN
Aggregated across every cluster whose name starts with "BT IP VPN" — a single company can be split across many separate clusters (per-datacenter, per-country, or per-subsidiary naming), so this view sums the true total rather than understating it with a single cluster's count.
14
Total ranges
13
Matched clusters
Matched clusters
Ranges (14)
showing 1–14 of 14 — ⬇ export CSV| CIDR | Org name | Cluster | Registry | Status | Confidence |
|---|---|---|---|---|---|
| 62.180.59.160/28 | BT-IP-VPN-DUESSELDORF | BT-IP-VPN-DUESSELDORF | RIPE | ASSIGNED PA | ● medium |
| 62.180.76.224/27 | BT-IP-VPN-HAMBURG | BT-IP-VPN-HAMBURG | RIPE | ASSIGNED PA | ● medium |
| 62.180.81.160/28 | BT-IP-VPN-HANNOVER | BT-IP-VPN-HANNOVER | RIPE | ASSIGNED PA | ● medium |
| 62.180.92.96/28 | BT-IP-VPN-KOELN | BT-IP-VPN-KOELN | RIPE | ASSIGNED PA | ● medium |
| 62.180.96.160/28 | BT-IP-VPN-LEIPZIG | BT-IP-VPN-LEIPZIG | RIPE | ASSIGNED PA | ● medium |
| 62.180.111.16 – 62.180.111.47 | BT-IP-VPN-MUENCHEN | BT-IP-VPN-MUENCHEN | RIPE | ASSIGNED PA | ● medium |
| 62.180.114.192/28 | BT-IP-VPN-NUERNBERG | BT-IP-VPN-NUERNBERG | RIPE | ASSIGNED PA | ● medium |
| 62.180.126.80/28 | BT-IP-VPN-STUTTGART | BT-IP-VPN-STUTTGART | RIPE | ASSIGNED PA | ● medium |
| 62.180.130.80/28 | BT-IP-VPN-ESSEN | BT-IP-VPN-ESSEN | RIPE | ASSIGNED PA | ● medium |
| 62.180.136.64/28 | BT-IP-VPN-KARLSRUHE | BT-IP-VPN-KARLSRUHE | RIPE | ASSIGNED PA | ● medium |
| 62.180.140.32/27 | BT-IP-VPN-MANNHEIM | BT-IP-VPN-MANNHEIM | RIPE | ASSIGNED PA | ● low |
| 62.180.143.193 – 62.180.143.222 | BT-IP-VPN-MANNHEIM | BT-IP-VPN-MANNHEIM | RIPE | ASSIGNED PA | ● low |
| 62.180.230.80/28 | BT-IP-VPN-FRANKFURT | BT-IP-VPN-FRANKFURT | RIPE | ASSIGNED PA | ● medium |
| 62.180.230.96/28 | BT-IP-VPN-FRANKFURT2 | BT-IP-VPN-FRANKFURT2 | RIPE | ASSIGNED PA | ● medium |
← Previous
Next →
Uses the REST API.