BVNET S.A.

BGP inherited
Cluster stats
Netblocks8 · 57,338 IPv4 addresses
Cluster ID214583247
RegistryPEERINGDB
Customersfind customers using 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

Footprint over time

4 weekly snapshots · JSON
8 -49 netblocks since 2026-07-05
2026-07-05 peak 57 2026-07-26

IP Ranges (8)

⬇ 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
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

Network trust

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

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

NIC Handles

AR-BVSA1-LACNIC AS27833 ROA10 ROA10 ROA10