Skip to main content

AS44534

yandex-office

YANDEX LLC

Registry

Authoritative registration data

AS number
44534
Name
yandex-office
Organisation
YANDEX LLC
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

20

IPv6 prefixes

7

Total announced

27

Announced prefixes

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

Prefixes announced by AS44534
84.252.160.0/20 IPv4 /20 not checked
93.158.184.0/21 IPv4 /21 not checked
5.45.252.0/22 IPv4 /22 not checked
93.158.144.0/22 IPv4 /22 not checked
93.158.168.0/22 IPv4 /22 not checked
77.88.12.0/23 IPv4 /23 not checked
37.9.75.0/24 IPv4 /24 not checked
37.9.86.0/24 IPv4 /24 not checked
37.9.98.0/24 IPv4 /24 not checked
5.255.205.0/24 IPv4 /24 not checked
5.45.214.0/24 IPv4 /24 not checked
5.45.219.0/24 IPv4 /24 not checked
5.45.241.0/24 IPv4 /24 not checked
5.45.243.0/24 IPv4 /24 not checked
77.88.6.0/24 IPv4 /24 not checked
84.252.160.0/24 IPv4 /24 not checked
87.250.240.0/24 IPv4 /24 not checked
93.158.184.0/24 IPv4 /24 not checked
93.158.186.0/24 IPv4 /24 not checked
93.158.187.0/24 IPv4 /24 not checked
2a02:6bf:8000::/34 IPv6 /34 not checked
2a02:6bf:8000::/35 IPv6 /35 not checked
2a02:6bf:a000::/35 IPv6 /35 not checked
2a02:6bf:8005::/48 IPv6 /48 not checked
2a02:6bf:8006::/48 IPv6 /48 not checked
2a02:6bf:a005::/48 IPv6 /48 not checked
2a02:6bf:a008::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS44534 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS44534 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 289 3,488
v4 v6
AS57304 RETNRU-AS 119 1,456
v4 v6
AS20485 TRANSTELECOM 314 1,272
v4
AS31500 GNM-AS 143 817
v4 v6
AS12389 ROSTELECOM-AS 184 624
v4 v6
AS31133 MF-MGSM-AS 237 556
v4 v6
AS41327 FIBERTELECOM-AS 2 14
v4 v6
AS8359 MTS 6 12
v4 v6
AS15958 CETIN_doo_AS 1 5
v4
AS60171 AFRIX-AS 1 5
v4 v6
AS50673 Serverius-as 2 4
v4

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS44534 in AS paths

Observed downstreams
Families
AS13238 YANDEX 20 22
v4
AS35598 INETCOM 1 2
v4
AS64999 1 2
v4

No rows match “”.

Showing of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS47692 NESSUS 1 18
v4 v6
AS44901 belcloud 1 9
v4 v6
AS209823 ENKI-AS 1 9
v4 v6
AS13004 SOX 1 5
v4
AS35598 INETCOM 1 5
v4
AS37721 ORG-VTS1-AFRINIC 1 5
v4
AS200612 GulfBridgeInternational 1 5
v4
AS208972 1 5
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.