AS263634 TACNET TELECOM

🇧🇷

Org handle: 133606

LACNICallocated

Announced Prefixes (BGP)

31total

20 IPv411 IPv6

IPv4 Addresses

Allocated (RIR)3,072

Announced (BGP)9,216

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)1.1×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2013-09-30

Announced Prefixes

(BGP)31

Prefix	RPKI	IRR	Last Seen
170.81.48.0/22	Valid	Other IRR	2026-10-11
170.81.48.0/23	Valid	Other IRR	2026-10-11
170.81.48.0/24	Valid	-	2026-10-11
170.81.49.0/24	Valid	-	2026-10-11
170.81.50.0/23	Valid	Other IRR	2026-10-11
170.81.50.0/24	Valid	Other IRR	2026-10-11
170.81.51.0/24	Valid	-	2026-10-11
179.125.112.0/21	Valid	Other IRR	2026-10-11
179.125.112.0/23	Valid	Other IRR	2026-10-11
179.125.112.0/24	Valid	-	2026-10-11

1-10 of 31

1 / 4

(RIR)3

Prefix	Country	RIR	Status
170.81.48.0/22	🇧🇷 BR	LACNIC	allocated
179.125.112.0/21	🇧🇷 BR	LACNIC	allocated
2804:1068::/32	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

Networks AS263634 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 AS263634 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/263634" | jq