AS10704 ML Telecom

🇧🇷

Org handle: 122400

LACNICallocated

Announced Prefixes (BGP)

41total

41 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)32,768

Announced (BGP)58,112

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

100

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2000-09-14

Announced Prefixes

(BGP)41

Prefix	RPKI	IRR	Last Seen
200.234.128.0/18	Valid	Other IRR	2026-10-10
200.234.128.0/22	Valid	-	2026-10-10
200.234.132.0/22	Valid	-	2026-10-10
200.234.136.0/22	Valid	-	2026-10-10
200.234.140.0/22	Valid	-	2026-10-10
200.234.144.0/22	Valid	-	2026-10-10
200.234.148.0/22	Valid	-	2026-10-10
200.234.152.0/22	Valid	-	2026-10-10
200.234.156.0/22	Valid	-	2026-10-10
200.234.156.0/23	Valid	-	2026-10-10

1-10 of 41

1 / 5

(RIR)2

Prefix	Country	RIR	Status
200.234.128.0/18	🇧🇷 BR	LACNIC	allocated
200.239.192.0/18	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

Networks AS10704 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 AS10704 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/10704" | jq