AS64114 TECNOWEB PERU SAC

🇵🇪

Org handle: 275938

LACNICallocated

Announced Prefixes (BGP)

48total

15 IPv433 IPv6

IPv4 Addresses

Allocated (RIR)1,024

Announced (BGP)3,840

IPv6 Addresses

Allocated (RIR)1.5×10²⁹

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

Prefix Limit (IPv6)

100

Country

RIR

Status

allocated

Allocated

2018-12-27

Announced Prefixes

(BGP)48

Prefix	RPKI	IRR	Last Seen
45.169.100.0/24	Valid	Other IRR	2026-10-11
45.169.101.0/24	Valid	Other IRR	2026-10-11
45.169.102.0/24	Valid	Other IRR	2026-10-11
45.169.103.0/24	Valid	Other IRR	2026-10-11
45.191.0.0/24	Valid	Other IRR	2026-10-11
45.191.1.0/24	Valid	Other IRR	2026-10-11
45.191.2.0/24	Valid	-	2026-10-11
177.126.36.0/24	Valid	-	2026-10-11
177.126.37.0/24	Valid	-	2026-10-11
177.126.38.0/24	Valid	-	2026-10-11

1-10 of 48

1 / 5

(RIR)3

Prefix	Country	RIR	Status
45.169.100.0/22	🇵🇪 PE	LACNIC	allocated
2803:7da0::/32	🇵🇪 PE	LACNIC	allocated
2803:e190::/32	🇦🇷 AR	LACNIC	allocated

(seen in AS paths)

Networks AS64114 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 AS64114 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/64114" | jq