BVNET S.A.

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks9 · 58,369 IPv4 addresses
IPv6 1 prefix (largest 2001:13c7:6009::1/128)
Record ID238248761
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 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 (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
200.14.37.1/32 BVNET PEERINGDB ASSIGNED ● high
2001:13c7:6009::1/128 BVNET PEERINGDB ASSIGNED ● high
170.231.76.0/22 BVNET S.A. LACNIC ALLOCATED ● low
181.197.192.0/18 BVNET S.A. LACNIC ALLOCATED ● low
190.1.0.0/19 BVNET S.A. LACNIC ALLOCATED ● low
190.1.32.0/19 BVNET S.A. LACNIC ALLOCATED ● low
190.97.0.0/19 BVNET S.A. LACNIC ALLOCATED ● low
190.97.32.0/19 BVNET S.A. LACNIC ALLOCATED ● low
190.211.192.0/19 BVNET S.A. LACNIC ALLOCATED ● low

IPv6 ranges (1)

Footprint over time

9 weekly snapshots · JSON
9 -48 netblocks since 2026-07-05
2026-07-05 peak 57 2026-09-06

Domains hosted in this network

what's this?

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (7)

These blocks are registered to BVNET S.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.

181.197.192.0/18 /18 authorized for AS27833 — AS27833
190.97.32.0/19 /19 authorized for AS27833 — AS27833
190.97.0.0/19 /19 authorized for AS27833 — AS27833
190.1.32.0/19 /19 authorized for AS27833 — AS27833
190.1.0.0/19 /19 authorized for AS27833 — AS27833
190.211.192.0/19 /19 authorized for AS27833 — AS27833
170.231.76.0/22 /22 authorized for AS27833 — AS27833

NIC Handles

AR-BVSA1-LACNIC AS27833 ROA10 ROA10 ROA10