VIPNET Conexão

Data as of 2026-08-30
BGP inherited
Cluster stats
Netblocks7 · 1,027 IPv4 addresses
IPv6 3 prefixes (largest 2001:12f8:1:23::20/128)
Cluster ID233786337
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 · report an issue

Footprint over time

10 weekly snapshots · JSON
7 -12 netblocks since 2026-07-05
2026-07-05 peak 19 2026-08-30

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
187.16.200.5/32 VIPNET Conexão PEERINGDB ASSIGNED ● high
187.16.200.20/32 VIPNET Conexão PEERINGDB ASSIGNED ● high
187.16.218.141/32 VIPNET Conexão PEERINGDB ASSIGNED ● high
2001:12f8::218:141/128 VIPNET Conexão PEERINGDB ASSIGNED ● high
2001:12f8:1:23::5/128 VIPNET Conexão PEERINGDB ASSIGNED ● high
2001:12f8:1:23::20/128 VIPNET Conexão PEERINGDB ASSIGNED ● high
45.181.104.0/22 VIPNET Conexão ARIN ALLOCATED ● low

IPv6 ranges (3)

CIDR
2001:12f8:1:23::20/128
2001:12f8:1:23::5/128
2001:12f8::218:141/128

Network trust

what's this?
RPKI hygiene: C how networks compare →
71.4% of checked blocks have valid RPKI ROA coverage (5 of 7)
Possible discrepancies (1)

These blocks are registered to VIPNET Conexão 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.181.104.0/22 /22 authorized for AS269180 — AS269180

NIC Handles

20302836000158 AS269180 HARJU16 HARJU16 HARJU16