AS268323

🇅🇅

LACNICreserved

Announced Prefixes (BGP)

104total

97 IPv47 IPv6

IPv4 Addresses

Allocated (RIR)0

Announced (BGP)85,760

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)2.3×10²⁹

Prefix Limit (IPv4)

200

Prefix Limit (IPv6)

Country

🇅🇅

RIR

Status

reserved

Allocated

Announced Prefixes

(BGP)104

Prefix	RPKI	IRR	Last Seen
45.175.188.0/22	Valid	Other IRR	2026-10-11
45.175.188.0/23	Valid	Other IRR	2026-10-11
45.175.190.0/23	Valid	Other IRR	2026-10-11
45.232.88.0/22	Valid	Other IRR	2026-10-11
45.232.88.0/23	Valid	Other IRR	2026-10-11
45.232.89.0/24	Valid	Other IRR	2026-10-11
45.232.90.0/23	Valid	Other IRR	2026-10-11
45.232.91.0/24	Valid	Other IRR	2026-10-11
45.238.116.0/22	Valid	Other IRR	2026-10-11
45.238.116.0/23	Valid	Other IRR	2026-10-11

1-10 of 104

1 / 11

(seen in AS paths)

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

Networks whose own prefixes AS268323 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 AS268323 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/268323" | jq