AS267398 mega ip connect

🇧🇷

Org handle: 282277

LACNICallocated

Announced Prefixes (BGP)

9total

6 IPv43 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)4,096

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)1.5×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2018-04-13

Announced Prefixes

(BGP)9

Prefix	RPKI	IRR	Last Seen
45.235.20.0/22	Valid	Other IRR	2026-10-11
45.235.20.0/23	Valid	-	2026-10-11
45.235.22.0/23	Valid	-	2026-10-11
205.164.248.0/22	Valid	Other IRR	2026-10-11
205.164.248.0/23	Valid	-	2026-10-11
205.164.250.0/23	Valid	-	2026-10-11
2804:4ce0::/32	Valid	-	2026-10-11
2804:4ce0::/33	Valid	-	2026-10-11
2804:4ce0:8000::/33	Valid	-	2026-10-11

(RIR)2

Prefix	Country	RIR	Status
45.235.20.0/22	🇧🇷 BR	LACNIC	allocated
2804:4ce0::/32	🇧🇷 BR	LACNIC	allocated

(seen in AS paths)

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

Networks whose own prefixes AS267398 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 AS267398 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/267398" | jq