AS270494 JNET TELECOM

🇧🇷

Org handle: 311598

LACNICallocated

Announced Prefixes (BGP)

10total

5 IPv45 IPv6

IPv4 Addresses

Allocated (RIR)0

Announced (BGP)1,792

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)1.5×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2020-03-12

Announced Prefixes

(BGP)10

Prefix	RPKI	IRR	Last Seen
24.152.4.0/23MOAS	No ROA	-	2026-10-11
24.152.4.0/24MOAS	No ROA	-	2026-10-11
24.152.6.0/23MOAS	No ROA	-	2026-10-11
24.152.6.0/24MOAS	No ROA	-	2026-10-11
24.152.7.0/24MOAS	No ROA	-	2026-10-11
2804:6cd0::/32	No ROA	Other IRR	2026-10-11
2804:6cd0::/34	No ROA	Other IRR	2026-10-11
2804:6cd0:4000::/34	No ROA	Other IRR	2026-10-11
2804:6cd0:8000::/34	No ROA	Other IRR	2026-10-11
2804:6cd0:c000::/34	No ROA	Other IRR	2026-10-11

(RIR)1

Prefix	Country	RIR	Status
2804:6cd0::/32	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

Networks AS270494 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 AS270494 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/270494" | jq