Vidanet, C.A.
Data as of 2026-09-06
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
This organisation
| Netblocks | 3 · 257 IPv4 addresses |
| IPv6 | 1 prefix (largest 2801:18d:0:1000::10/128) |
| Record ID | 237311327 |
| Registry | PEERINGDB |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 9 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.100.10/32 | Vidanet, C.A. | PEERINGDB | ASSIGNED | ● high |
| 2801:18d:0:1000::10/128 | Vidanet, C.A. | PEERINGDB | ASSIGNED | ● high |
| 45.7.140.0/24 | VIDANET CA | LACNIC | REALLOCATED | ● low |
IPv6 ranges (1)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to Vidanet, C.A. 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.
| 45.7.140.0/24 /24 | authorized for AS271816 — AS271816 |
NIC Handles
AS271816
MOC31
MOC31
MOC31
MOC31
MOC31
MOC31
VE-VICA6-LACNIC
VE-VICA6-LACNIC