AS270682 TORRES CONECT TELECOMUNICACOES LTDA

🇅🇅

LACNICreserved

Announced Prefixes (BGP)

10total

7 IPv43 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)3,072

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)1.5×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇅🇅

RIR

Status

reserved

Allocated

2020-05-07

Announced Prefixes

(BGP)10

Prefix	RPKI	IRR	Last Seen
200.187.96.0/22MOAS	Invalid	-	2026-10-11
200.187.96.0/23MOAS	Invalid	-	2026-10-11
200.187.96.0/24MOAS	Invalid	-	2026-10-11
200.187.97.0/24MOAS	Invalid	-	2026-10-11
200.187.98.0/23MOAS	Invalid	-	2026-10-11
200.187.98.0/24MOAS	Invalid	-	2026-10-11
200.187.99.0/24MOAS	Invalid	-	2026-10-11
2804:6fc0::/32	No ROA	Other IRR	2026-10-11
2804:6fc0::/33	No ROA	-	2026-10-11
2804:6fc0:8000::/33	No ROA	-	2026-10-11

(RIR)2

Prefix	Country	RIR	Status
200.187.96.0/22	🇧🇷 BR	LACNIC	allocated
2804:6fc0::/32	-	LACNIC	reserved

(seen in AS paths)

Networks AS270682 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 AS270682 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/270682" | jq