VIP Support
BGP inherited
Cluster stats
| Netblocks | 31 · 4,045 IPv4 addresses |
| Registered in | Poland (12) · France (10) · Russia (3) · Italy (2) · Thailand (1) · China (1) |
| Cluster ID | 208946613 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 22 shared RIR contact/maintainer handles |
| Registry names | 20 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
35
+25 netblocks since 2026-07-05
2026-07-05
peak 35
2026-07-19
IP Ranges (31)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.39.18.32/28 | VIP Support | RIPE | ASSIGNED PA | ● high |
| 5.39.54.32/28 | VIP Support | RIPE | ASSIGNED PA | ● high |
| 51.83.217.208/28 | VIP Support | RIPE | LEGACY | ● high |
| 54.37.105.176/28 | VIP Support | RIPE | LEGACY | ● high |
| 91.134.144.144/28 | VIP Support | RIPE | ASSIGNED PA | ● high |
| 137.74.244.192/28 | VIP Support | RIPE | ASSIGNED PA | ● high |
| 141.94.86.48/28 | VIP Support | RIPE | ASSIGNED PA | ● high |
| 151.80.162.144/28 | VIP Support | RIPE | LEGACY | ● high |
| 162.19.177.224/28 | VIP Support | RIPE | LEGACY | ● high |
| 176.31.34.176/29 | VIP Support | RIPE | ASSIGNED PA | ● high |
| 185.51.152.0/24 | vip-subnet1 | RIPE | ASSIGNED PA | ● high |
| 37.29.48.160/29 | VIP-LAN | RIPE | ASSIGNED PA | ● low |
| 49.231.12.160/27 | VIP-By-SBN | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 59.37.43.0/24 | VIP-ZX | APNIC | Allocated non-portable | ● low |
| 81.116.70.96/28 | VIP-S-R-L | RIPE | ASSIGNED PA | ● low |
| 81.116.70.240/28 | VIP-S-R-L | RIPE | ASSIGNED PA | ● low |
| 89.186.2.0/24 | VIP-NET2 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.4.0/24 | VIP-NET4 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.5.0/24 | VIP-NET5 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.6.0/24 | VIP-NET6 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.7.0/24 | VIP-NET7 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.8.0/24 | VIP-NET8 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.9.0/24 | VIP-NET9 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.11.0/24 | VIP-NET11 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.12.0/24 | VIP-NET12 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.13.0/24 | VIP-NET13 | RIPE | LIR-PARTITIONED PA | ● low |
| 89.186.15.0/24 | VIP-NET15 | RIPE | LIR-PARTITIONED PA | ● low |
| 95.167.2.156/30 | VIP_R | RIPE | ASSIGNED PA | ● low |
| 95.167.9.176/30 | VIP_R | RIPE | ASSIGNED PA | ● low |
| 185.86.188.0/23 | VIP-SVC-NET01 | RIPE | ASSIGNED PA | ● low |
| 213.241.23.200/30 | VIP-CAR | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?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.
- TWOSUPPORT sub-allocation
- GRAFISK-SUPPORTDK via TDC Holding A/S sub-allocation
- TRAININGSUPPORT via Virgin Media Limited sub-allocation
- VICTIMSUPPORT via Eircom Limited sub-allocation
- SUPPORTKEY via Vodafone Group PLC sub-allocation
- SUPPORT-NETC sub-allocation
- SUPPORT-NETB sub-allocation
- SUPPORT-NETA sub-allocation
Network trust
what's this?
RPKI hygiene: B
how networks compare →
90.3%
of checked blocks have valid RPKI ROA coverage
(28 of 31)
Possible discrepancies (2)
These blocks are registered to VIP Support but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 185.86.188.0/23 /23 | authorized for AS203759 — INTAC Services GmbH |
| 59.37.43.0/24 /24 | authorized for AS140319 — China Telecom |
NIC Handles
AA1419-AP
DUMY-RIPE
DUMY-RIPE
HY-AP
IC83-AP
ITCARE-MNT
MAINT-AWN-CO-LTD-TH
MAINT-CHINANET-GD
MNT-MF-NWGSM
MNT-amer1
NETIA-MNT
NI36-AP
+10 more