AS270606 R3 TELECOM

🇧🇷

Org handle: 311351

LACNICallocated

Announced Prefixes (BGP)

9total

6 IPv43 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)2,816

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)1.5×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2020-04-08

Announced Prefixes

(BGP)9

Prefix	RPKI	IRR	Last Seen
177.37.16.0/22	Valid	Other IRR	2026-10-11
177.37.16.0/23	Valid	Other IRR	2026-10-11
177.37.16.0/24	Valid	-	2026-10-11
177.37.17.0/24	Valid	-	2026-10-11
177.37.18.0/23	Valid	Other IRR	2026-10-11
177.37.18.0/24	Valid	-	2026-10-11
2804:6e94::/32	Valid	Other IRR	2026-10-11
2804:6e94::/33	Valid	-	2026-10-11
2804:6e94:8000::/33	Valid	-	2026-10-11

(RIR)2

Prefix	Country	RIR	Status
177.37.16.0/22	🇧🇷 BR	LACNIC	allocated
2804:6e94::/32	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

Networks AS270606 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 AS270606 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/270606" | jq