Skip to main content

AS13238

YANDEX

YANDEX LLC

Registry

Authoritative registration data

AS number
13238
Name
YANDEX
Organisation
YANDEX LLC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

30

IPv6 prefixes

17

Total announced

47

Announced prefixes

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

Prefixes announced by AS13238
95.108.128.0/17 IPv4 /17 not checked
141.8.128.0/18 IPv4 /18 RPKI valid
37.140.128.0/18 IPv4 /18 RPKI valid
37.9.64.0/18 IPv4 /18 RPKI valid
5.255.192.0/18 IPv4 /18 RPKI valid
5.45.192.0/18 IPv4 /18 RPKI valid
77.88.0.0/18 IPv4 /18 RPKI valid
93.158.128.0/18 IPv4 /18 RPKI valid
178.154.128.0/19 IPv4 /19 RPKI valid
178.154.160.0/19 IPv4 /19 RPKI valid
213.180.192.0/19 IPv4 /19 RPKI valid
84.252.160.0/19 IPv4 /19 RPKI valid
87.250.224.0/19 IPv4 /19 RPKI valid
92.255.112.0/20 IPv4 /20 RPKI valid
141.8.134.0/24 IPv4 /24 not checked
178.154.131.0/24 IPv4 /24 not checked
185.32.187.0/24 IPv4 /24 not checked
213.180.199.0/24 IPv4 /24 not checked
37.9.112.0/24 IPv4 /24 RPKI valid
37.9.64.0/24 IPv4 /24 not checked
37.9.87.0/24 IPv4 /24 RPKI valid
5.255.197.0/24 IPv4 /24 not checked
5.255.255.0/24 IPv4 /24 RPKI valid
5.45.202.0/24 IPv4 /24 RPKI valid
5.45.205.0/24 IPv4 /24 RPKI valid
5.45.215.0/24 IPv4 /24 RPKI valid
77.88.44.0/24 IPv4 /24 not checked
77.88.55.0/24 IPv4 /24 RPKI valid
77.88.8.0/24 IPv4 /24 not checked
87.250.247.0/24 IPv4 /24 not checked
2a02:6b8::/29 IPv6 /29 RPKI valid
2a02:6b8::/32 IPv6 /32 RPKI valid
2a02:6b8:20::/48 IPv6 /48 not checked
2a02:6b8:215::/48 IPv6 /48 RPKI valid
2a02:6b8:21::/48 IPv6 /48 RPKI valid
2a02:6b8:22::/48 IPv6 /48 RPKI valid
2a02:6b8:23::/48 IPv6 /48 not checked
2a02:6b8:24::/48 IPv6 /48 not checked
2a02:6b8:4::/48 IPv6 /48 not checked
2a02:6b8:5::/48 IPv6 /48 not checked
2a02:6b8:6::/48 IPv6 /48 not checked
2a02:6b8:8::/48 IPv6 /48 RPKI valid
2a02:6b8:a::/48 IPv6 /48 RPKI valid
2a02:6b8:b::/48 IPv6 /48 RPKI valid
2a02:6b8:c::/48 IPv6 /48 RPKI valid
2a02:6b8:d::/48 IPv6 /48 RPKI valid
2a02:6b8:e::/48 IPv6 /48 RPKI valid

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 AS13238
Address families
CLOUD-IX MSK 100,000 Mbps IPv4 · IPv6
Eurasia Peering IX: Peering LAN 100,000 Mbps IPv4 · IPv6
GNM-IX 200,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 600,000 Mbps IPv4 · IPv6
MSK-IX Saint-Petersburg: MSK-IX Saint-Petersburg peering network 200,000 Mbps IPv4 · IPv6
PITER-IX Moscow: MSK_PEERING_VLAN 800,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 300,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 AS13238 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS13238 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 145 2,023
v4 v6
AS57304 RETNRU-AS 63 550
v4 v6
AS25091 IP-Max 19 474
v4 v6
AS20764 RASCOM-AS 122 266
v4 v6
AS34927 iFog-GmbH 4 87
v4
AS41327 FIBERTELECOM-AS 4 80
v4 v6
AS61049 EXASCALE 4 62
v4
AS49434 FBWNETWORKS 4 61
v4
AS3216 SOVAM-AS 37 53
v4
AS43727 KVANT-TELECOM 36 47
v4
AS9198 KAZTELECOM-AS 1 42
v4 v6
AS12389 ROSTELECOM-AS 1 2
v4
AS62261 MSK-IX-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS13238 in AS paths

Observed downstreams
Families
AS207304 Y-KZ 102 189
v4 v6
AS215013 YCCDN 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 527
v4 v6
AS28917 Fiord-AS 2 65
v4 v6
AS28910 INTAL-ASN 2 49
v4 v6
AS36236 NETACTUATE 2 49
v4 v6
AS41722 MIRAN-AS 2 49
v4 v6
AS49673 TRUENETWORK 3 32
v4
AS35598 INETCOM 2 31
v4
AS37721 ORG-VTS1-AFRINIC 2 31
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.