AS262671 VERO S.A

🇧🇷

Org handle: 330814

LACNICallocated

Announced Prefixes (BGP)

36total

35 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)5,120

Announced (BGP)21,248

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

100

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2009-07-01

Announced Prefixes

(BGP)36

Prefix	RPKI	IRR	Last Seen
170.82.136.0/22	Valid	-	2026-10-11
170.82.136.0/23	Valid	-	2026-10-11
170.82.136.0/24	Valid	-	2026-10-11
170.82.137.0/24	Valid	-	2026-10-11
170.82.138.0/23	Valid	-	2026-10-11
170.82.138.0/24	Valid	-	2026-10-11
170.82.139.0/24	Valid	-	2026-10-11
187.73.16.0/20	Valid	-	2026-10-11
187.73.16.0/21	Valid	-	2026-10-11
187.73.16.0/22	Valid	-	2026-10-11

1-10 of 36

1 / 4

(RIR)3

Prefix	Country	RIR	Status
170.82.136.0/22	🇧🇷 BR	LACNIC	allocated
187.73.16.0/20	🇧🇷 BR	LACNIC	allocated
2804:37e8::/32	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

Networks AS262671 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 AS262671 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/262671" | jq