VEGA CESAR AUGUSTO

VEGA CESAR AUGUSTO (I-TIC)
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
Netblocks3 · 257 IPv4 addresses
IPv6 1 prefix (largest 2801:168:1::9/128)
Record ID238788638
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 (3)

⬇ export CSV
CIDR Org name Registry Status Confidence
138.204.255.9/32 VEGA CESAR AUGUSTO (I-TIC) PEERINGDB ASSIGNED ● high
2801:168:1::9/128 VEGA CESAR AUGUSTO (I-TIC) PEERINGDB ASSIGNED ● high
45.226.58.0/24 VEGA CESAR AUGUSTO (I-TIC) ARIN ALLOCATED ● 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 VEGA CESAR AUGUSTO (I-TIC) 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.226.58.0/24 /24 authorized for AS265865 — AS265865

NIC Handles

AR-VCAI-LACNIC AS265865 DNV6 DNV6 DNV6