AS268272 TBN TELECOMUNICACOES LTDA ME

🇧🇷

Org handle: 276319

LACNICallocated

Announced Prefixes (BGP)

9total

5 IPv44 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)2,304

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)3.7×10²⁷

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2018-05-29

Announced Prefixes

(BGP)9

Prefix	RPKI	IRR	Last Seen
45.237.120.0/22	Valid	Other IRR	2026-10-10
45.237.120.0/23	Valid	Other IRR	2026-10-10
45.237.123.0/24	Valid	Other IRR	2026-10-10
209.61.10.0/24	No ROA	Other IRR	2026-10-10
209.61.11.0/24	No ROA	-	2026-10-10
2804:4e9c::/38	Valid	-	2026-10-10
2804:4e9c::/39	Valid	-	2026-10-10
2804:4e9c:200::/39	Valid	-	2026-10-10
2804:4e9c:400::/38	Valid	-	2026-10-10

(RIR)2

Prefix	Country	RIR	Status
45.237.120.0/22	🇧🇷 BR	LACNIC	allocated
2804:4e9c::/32	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

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

Networks whose own prefixes AS268272 passes on: usually its customers.

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 AS268272 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/268272" | jq