AS272610 ISPBR TELECOM

🇧🇷

Org handle: 311254

LACNICallocated

Announced Prefixes (BGP)

18total

3 IPv415 IPv6

IPv4 Addresses

Allocated (RIR)0

Announced (BGP)1,024

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)3.1×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2022-02-21

Announced Prefixes

(BGP)18

Prefix	RPKI	IRR	Last Seen
38.252.148.0/23	Valid	ARINOther IRR	2026-10-11
38.252.148.0/24	Valid	-	2026-10-11
38.252.149.0/24	Valid	Other IRR	2026-10-11
2804:85f4::/32	Valid	Other IRR	2026-10-11
2804:85f4::/33	Valid	-	2026-10-11
2804:85f4::/34	Valid	-	2026-10-11
2804:85f4::/35	Valid	-	2026-10-11
2804:85f4:2000::/35	Valid	-	2026-10-11
2804:85f4:4000::/34	Valid	-	2026-10-11
2804:85f4:4000::/35	Valid	-	2026-10-11

1-10 of 18

1 / 2

(RIR)1

Prefix	Country	RIR	Status
2804:85f4::/32	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

Networks AS272610 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 AS272610 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/272610" | jq