AS263072 VERO S.A

🇧🇷

Org handle: 330814

LACNICallocated

Announced Prefixes (BGP)

38total

35 IPv43 IPv6

IPv4 Addresses

Allocated (RIR)5,120

Announced (BGP)18,944

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

100

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2012-03-27

Announced Prefixes

(BGP)38

Prefix	RPKI	IRR	Last Seen
168.121.16.0/22	Valid	-	2026-10-10
168.121.16.0/23	Valid	-	2026-10-10
168.121.16.0/24	Valid	-	2026-10-10
168.121.17.0/24	Valid	-	2026-10-10
168.121.18.0/23	Valid	-	2026-10-10
168.121.18.0/24	Valid	-	2026-10-10
168.121.19.0/24	Valid	-	2026-10-10
186.195.80.0/20	Valid	-	2026-10-10
186.195.80.0/22	Valid	-	2026-10-10
186.195.80.0/24	Valid	-	2026-10-10

1-10 of 38

1 / 4

(RIR)3

Prefix	Country	RIR	Status
168.121.16.0/22	🇧🇷 BR	LACNIC	allocated
186.195.80.0/20	🇧🇷 BR	LACNIC	allocated
2804:950::/32	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

Networks AS263072 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

External Links

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS263072 should publish an ASPA object
IPv4 transfers in the LACNIC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/263072" | jq