SERVERS TECH FZCO
VDSINA
Cluster stats
| Netblocks | 250 |
| Cluster ID | 191682365 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
250
0 netblocks since 2026-07-05
2026-07-05
peak 250
2026-07-06
IP Ranges (250)
showing 50 of 250 — see all — ⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 80.249.215.206/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 109.239.136.218/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 109.239.136.219/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.224.9/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.224.11/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.224.72/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.224.144/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.224.187/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.225.206/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.226.27/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.19/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.40/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.43/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.220/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 178.18.236.223/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 185.1.222.242/32 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1:0:a500:21:6071:1/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b7::a520:7651:1/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2001:b28:3ff::32b2:0:1/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2001:b28:3ff::32b2:0:2/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::224:9/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::224:11/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::224:72/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::224:144/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::224:187/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::225:206/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::226:27/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::236:19/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::236:40/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::236:43/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::236:220/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4:2::236:223/128 | VDSINA | PEERINGDB | ASSIGNED | ● high |
| 62.113.112.0/24 | VDSINA-NET | RIPE | ASSIGNED PA | ● low |
| 62.113.113.0/24 | VDSINA-NET | RIPE | ASSIGNED PA | ● low |
| 62.113.114.0/24 | VDSINA-NET | RIPE | ASSIGNED PA | ● low |
| 62.113.115.0/24 | VDSINA-NET | RIPE | ASSIGNED PA | ● low |
| 62.113.116.0/24 | VDSINA-NET | RIPE | ASSIGNED PA | ● low |
| 62.113.117.0/24 | VDSINA-NET | RIPE | ASSIGNED PA | ● low |
| 62.113.118.0/24 | VDSINA-NET | RIPE | ASSIGNED PA | ● low |
| 62.113.119.0/24 | VDSINA-NET | RIPE | ASSIGNED PA | ● low |
| 77.238.224.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
| 77.238.225.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
| 77.238.226.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
| 77.238.227.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
| 77.238.228.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
| 77.238.229.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
| 77.238.230.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
| 77.238.231.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
| 77.238.232.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
| 77.238.233.0/24 | VDSINA | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
94.0%
of checked blocks have valid RPKI ROA coverage
(235 of 250)
Possible discrepancies (169)
These blocks are registered to VDSINA but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 80.85.244.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 80.85.245.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 80.85.246.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 80.85.247.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 109.234.33.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.224.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.225.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.226.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.227.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.228.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.229.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.230.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.231.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.232.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
| 77.238.233.0/24 /24 | authorized for AS216071 — SERVERS TECH FZCO |
+154 more — see the REST API
NIC Handles
AS216071
DUMY-RIPE
DUMY-RIPE
HTL31-RIPE
ru-vdsina-1-mnt
servers-tech-mnt
vdsina-mnt