Skip to main content

AS25526

LambdaNetUA

UA

Registry

Authoritative registration data

AS number
25526
Name
LambdaNetUA
Organisation
UA
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS25526
109.197.216.0/21 IPv4 /21 not checked
193.254.220.0/23 IPv4 /23 not checked
195.39.242.0/23 IPv4 /23 not checked
2001:678:b44::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS25526
Address families
Giganet IXN: Global exchange 10,000 Mbps IPv4 · IPv6
UA-IX 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS25526 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS25526 in AS paths

Observed upstreams
Families
AS29491 276 839
v4 v6
AS12963 113 435
v4
AS6939 HURRICANE 93 124
v6
AS3303 SWISSCOM 10 43
v4 v6
AS24482 SGGS-AS-AP 2 28
v4 v6
AS30886 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS25526 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 8
v4 v6
AS48919 1 4
v4 v6
AS209823 1 4
v4 v6
AS59514 1 3
v4

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.