AS267818 OPTVE TELECOMUNICACIONES SpA

🇨🇱

Org handle: 289676

LACNICallocated

Announced Prefixes (BGP)

10total

10 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)2,048

Announced (BGP)4,096

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2019-03-29

Announced Prefixes

(BGP)10

Prefix	RPKI	IRR	Last Seen
45.173.120.0/22	Valid	LACNICOther IRR	2026-10-10
45.173.120.0/24	Valid	Other IRR	2026-10-10
45.173.121.0/24	Valid	Other IRR	2026-10-10
45.173.122.0/24	Valid	Other IRR	2026-10-10
45.173.123.0/24	Valid	Other IRR	2026-10-10
190.97.172.0/22	Valid	LACNIC	2026-10-10
190.97.172.0/24	Valid	-	2026-10-10
190.97.173.0/24	Valid	-	2026-10-10
190.97.174.0/24	Valid	-	2026-10-10
190.97.175.0/24	Valid	-	2026-10-10

(RIR)3

Prefix	Country	RIR	Status
45.173.120.0/22	🇨🇱 CL	LACNIC	allocated
190.97.172.0/22	🇨🇱 CL	LACNIC	allocated
2803:8860::/32	🇨🇱 CL	LACNIC	allocated

(seen in AS paths)

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

Networks whose own prefixes AS267818 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 AS267818 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/267818" | jq