Home ASN LookupAS25526

AS25526 LambdaNetUA LAMBDA LLC

🇺🇦

Org handle: ORG-LL380-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

4total

3 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)3,072

Announced (BGP)3,072

IPv6 Addresses

Allocated (RIR)1.2×10²⁴

Announced (BGP)1.2×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇺🇦 UA

RIR

RIPE NCC

Status

allocated

Allocated

2002-12-23

Announced Prefixes

(BGP)4

Prefix	RPKI	IRR	Last Seen
109.197.216.0/21	Valid	RIPE	2026-10-10
193.254.220.0/23	Valid	RIPE	2026-10-10
195.39.242.0/23	Valid	RIPE	2026-10-10
2001:678:b44::/48	Valid	RIPE	2026-10-10

Allocated Prefixes

(RIR)4

Prefix	Country	RIR	Status
109.197.216.0/21	🇺🇦 UA	RIPENCC	assigned
193.254.220.0/23	🇺🇦 UA	RIPENCC	assigned
195.39.242.0/23	🇺🇦 UA	RIPENCC	assigned
2001:678:b44::/48	🇺🇦 UA	RIPENCC	assigned

All 4 announced prefixes of AS25526 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS12963VOLZ "SCIENTIFIC INDUSTRIAL FIRM "VOLZ" LIMITED LIABILITY COMPANY3
AS15645AS15645 DE "Ukrainian Internet Exchange" (UA IX)1

Transfer History

Registry transfers of AS25526 between organisations.

AS25526Transfer · 2021-01-05
TOV Lambda Net
RIPE NCC
→
LAMBDA LLC
RIPE NCC

Date	Resource	From	To	Type
2021-01-05	AS25526	TOV Lambda Net RIPE NCC	LAMBDA LLC RIPE NCC	Transfer

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

Learn more

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 AS25526 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Open

GEThttps://api.ipctl.io/v1/asn/25526

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/25526" | jq