bgpreport

Network · data from 2026-11-12

AS44534 yandex-office YANDEX LLC

Registry name: yandex-office YANDEX LLC, RU · not in PeeringDB

22IPv4 routes 95.5% RPKI valid · 95.5% with a route object
10IPv6 routes 100.0% RPKI valid · 90.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
0No ROA 2 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
36Route objects not announced registered with origin AS44534, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS44534, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

84.252.160.0/24 Invalid: maxLength Nonecovered by 84.252.160.0/20 71 11% 34
2a02:6bf:80b0::/48 Valid Nonecovered by 2a02:6bf:8000::/35 104 16% 32
5.45.214.0/24 Valid RIR databaseRIPE 673 100% 66
5.45.219.0/24 Valid RIR databaseRIPE 673 100% 66
5.255.205.0/24 Valid RIR databaseRIPE 673 100% 66
77.88.12.0/23 Valid RIR databaseRIPE 673 100% 66
87.250.240.0/24 Valid RIR databaseRIPE 673 100% 66
93.158.144.0/22 Valid RIR databaseRIPE 673 100% 66
93.158.184.0/21 Valid RIR databaseRIPE 673 100% 66
93.158.187.0/24 Valid RIR databaseRIPE 673 100% 66
37.9.75.0/24 Valid RIR databaseRIPE 672 100% 66
77.88.6.0/24 Valid RIR databaseRIPE 672 100% 66
5.45.241.0/24 Valid RIR databaseRIPE 671 100% 66
5.45.243.0/24 Valid RIR databaseRIPE 671 100% 66
5.45.252.0/22 Valid RIR databaseRIPE 671 100% 66
84.252.160.0/20 Valid RIR databaseRIPE 671 100% 66
37.9.86.0/24 Valid RIR databaseRIPE 670 100% 66
37.9.98.0/24 Valid RIR databaseRIPE 670 100% 66
2a02:6bf:8000::/34 Valid RIR databaseRIPE 636 100% 69
2a02:6bf:8000::/35 Valid RIR databaseRIPE 635 100% 67
2a02:6bf:a000::/35 Valid RIR databaseRIPE 635 100% 67
2a02:6bf:a005::/48 Valid RIR databaseRIPE 635 100% 67
2a02:6bf:8005::/48 Valid RIR databaseRIPE 634 100% 67
2a02:6bf:8006::/48 Valid RIR databaseRIPE 634 100% 67
2a02:6bf:a008::/48 Valid RIR databaseRIPE 634 100% 67
93.158.184.0/24 Valid RIR databaseRIPE 72 11% 37
93.158.185.0/24 Valid RIR databaseRIPE 72 11% 37
93.158.186.0/24 Valid RIR databaseRIPE 72 11% 37
5.255.203.0/24 Valid RIR databaseRIPE 6 1%low visibility 3
2a02:6bf:80ae::/48 Valid RIR databaseRIPE 3 0%low visibility 2
2a02:6bf:a0ac::/48 Valid RIR databaseRIPE 3 0%low visibility 2
93.158.168.0/22 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS44534 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 39 are in fix.csv.

  • ROA: maxLength1
  • Route object: none2
  • Route object: not announced36
ChangePrefix or setDetailFull-table peers
ROA: maxLength84.252.160.0/24ROA 84.252.160.0/19 AS44534 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 84.252.160.0/24.71 of 673
Route object: none84.252.160.0/24No route object for it. A route object for 84.252.160.0/20 with origin AS44534 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44534 in the RIR database for the space.71 of 673
Route object: none2a02:6bf:80b0::/48No route object for it. A route object for 2a02:6bf:8000::/35 with origin AS44534 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44534 in the RIR database for the space.104 of 636

Route objects not announced

Route objects with origin AS44534 whose prefix no peer sees AS44534 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.45.209.0/24RIPEValid
5.255.232.0/24RIPEValid
37.140.168.0/24RIPEValid
77.88.42.0/23RIPEValid
77.88.61.0/24RIPEValid
84.252.160.0/19RIPEValid
87.250.232.0/24RIPEValid
87.250.238.0/24RIPEValid
90.156.179.0/24RIPEValid
90.156.180.0/24RIPEValid
90.156.181.0/24RIPEValid
90.156.183.0/24RIPEValid
90.156.184.0/24RIPEValid
90.156.185.0/24RIPEValid
90.156.186.0/24RIPEValid
93.158.155.0/24RIPEValid
93.158.182.0/24RIPEValid
95.108.168.0/22RIPEValid
95.108.170.0/24RIPEValid
178.154.152.0/24RIPEValid
2a02:6bf:8001::/48RIPEValid
2a02:6bf:8004::/48RIPEValid
2a02:6bf:8007::/48RIPEValid
2a02:6bf:8008::/48RIPEValid
2a02:6bf:8009::/48RIPEValid
2a02:6bf:800a::/48RIPEValid
2a02:6bf:800b::/48RIPEValid
2a02:6bf:800c::/48RIPEValid
2a02:6bf:8011::/48RIPEValid
2a02:6bf:8012::/48RIPEValid
2a02:6bf:8013::/48RIPEValid
2a02:6bf:8015::/48RIPEValid
2a02:6bf:80a4::/48RIPEValid
2a02:6bf:80ab::/48RIPEValid
2a02:6bf:a01f::/48RIPEValid
2a02:6bf:a030::/48RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.