Routing security
AS44534 YANDEX-OFFICE
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS44534 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 84.252.160.0/24 | RPKI invalid · length | IRR covering | 3 |
| 2a02:6bf:8000::/34 | RPKI valid | IRR | 34 |
| 2a02:6bf:8000::/35 | RPKI valid | IRR | 31 |
| 2a02:6bf:8005::/48 | RPKI valid | IRR | 31 |
| 2a02:6bf:8006::/48 | RPKI valid | IRR | 31 |
| 2a02:6bf:a000::/35 | RPKI valid | IRR | 31 |
| 2a02:6bf:a005::/48 | RPKI valid | IRR | 31 |
| 2a02:6bf:a008::/48 | RPKI valid | IRR | 31 |
| 5.45.214.0/24 | RPKI valid | IRR | 52 |
| 5.45.219.0/24 | RPKI valid | IRR | 52 |
| 5.45.241.0/24 | RPKI valid | IRR | 53 |
| 5.45.243.0/24 | RPKI valid | IRR | 52 |
| 5.45.252.0/22 | RPKI valid | IRR | 53 |
| 5.255.203.0/24 | RPKI valid | IRR | 1 |
| 5.255.205.0/24 | RPKI valid | IRR | 52 |
| 37.9.75.0/24 | RPKI valid | IRR | 53 |
| 37.9.86.0/24 | RPKI valid | IRR | 52 |
| 37.9.98.0/24 | RPKI valid | IRR | 52 |
| 77.88.6.0/24 | RPKI valid | IRR | 52 |
| 77.88.12.0/23 | RPKI valid | IRR | 53 |
| 84.252.160.0/20 | RPKI valid | IRR | 52 |
| 87.250.240.0/24 | RPKI valid | IRR | 53 |
| 93.158.144.0/22 | RPKI valid | IRR | 52 |
| 93.158.184.0/21 | RPKI valid | IRR | 52 |
| 93.158.184.0/24 | RPKI valid | IRR | 4 |
| 93.158.185.0/24 | RPKI valid | IRR | 4 |
| 93.158.186.0/24 | RPKI valid | IRR | 4 |
| 93.158.187.0/24 | RPKI valid | IRR | 52 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS44534 may originate these prefixes, up to the maximum length shown.
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS8359 | MTS PJSC | Declared | Observed |
| AS9002 | RETN Limited | Declared | Observed |
| AS31133 | PJSC MegaFon | Declared | Observed |
| AS57304 | JSC "RetnNet" | Declared | Observed |
| AS31500 | Global Network Management Inc | not declared | Observed |
| AS12389 | PJSC Rostelecom | not declared | Observed |
| AS20485 | Joint Stock Company TransTeleCom | not declared | Observed |
| AS37721 | Virtual Technologies & Solutions | not declared | Observed |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | not declared | Observed |
| AS3216 | PJSC "Vimpelcom" | not declared | Observed |
| AS50673 | Serverius Holding B.V. | not declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS44534 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 5.45.209.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-08 | Not announced |
| 5.255.232.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-27 | Not announced |
| 37.140.168.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-08 | Not announced |
| 77.88.42.0/23 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-08 | Not announced |
| 77.88.61.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-08 | Not announced |
| 84.252.160.0/19 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-18 | Not announced |
| 87.250.232.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-08 | Not announced |
| 87.250.238.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-08 | Not announced |
| 90.156.179.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2022-05-17 | Not announced |
| 90.156.180.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2022-07-20 | Not announced |
| 90.156.181.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-01-23 | Not announced |
| 90.156.183.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-02-06 | Not announced |
| 90.156.184.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-03-20 | Not announced |
| 90.156.185.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-03-20 | Not announced |
| 90.156.186.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-08-07 | Not announced |
| 93.158.155.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-08 | Not announced |
| 93.158.168.0/22 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-02 | Not announced |
| 93.158.182.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-10-27 | Not announced |
| 95.108.168.0/22 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-08 | Not announced |
| 95.108.170.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-10-17 | Not announced |
| 178.154.152.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-11-08 | Not announced |
| 2a02:6bf:8001::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:8004::/48 | RIPE | Yandex network | YANDEX-MNT | 2023-11-27 | Not announced |
| 2a02:6bf:8007::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:8008::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:8009::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:800a::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:800b::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:800c::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:8011::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-14 | Not announced |
| 2a02:6bf:8012::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:8013::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:8015::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-15 | Not announced |
| 2a02:6bf:80a4::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:80ab::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:80ae::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-08-08 | Not announced |
| 2a02:6bf:a01f::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:a030::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-08 | Not announced |
| 2a02:6bf:a0ac::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-08-08 | Not announced |
| 5.45.214.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-02 | Announced |
| 5.45.219.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-02 | Announced |
| 5.45.241.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-17 | Announced |
| 5.45.243.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-02 | Announced |
| 5.45.252.0/22 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-17 | Announced |
| 5.255.203.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-08-13 | Announced |
| 5.255.205.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-02 | Announced |
| 37.9.75.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-17 | Announced |
| 37.9.86.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-02 | Announced |
| 37.9.98.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-02 | Announced |
| 77.88.6.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-08-06 | Announced |
| 77.88.12.0/23 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-17 | Announced |
| 84.252.160.0/20 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-25 | Announced |
| 87.250.240.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-17 | Announced |
| 93.158.144.0/22 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-09-02 | Announced |
| 93.158.184.0/21 | RIPE | Yandex enterprise network | YANDEX-MNT | 2026-04-07 | Announced |
| 93.158.184.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-09-20 | Announced |
| 93.158.185.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-09-20 | Announced |
| 93.158.186.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-09-20 | Announced |
| 93.158.187.0/24 | RIPE | Yandex enterprise network | YANDEX-MNT | 2023-09-20 | Announced |
| 2a02:6bf:8000::/34 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-06-30 | Announced |
| 2a02:6bf:8000::/35 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-08-01 | Announced |
| 2a02:6bf:8005::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-01 | Announced |
| 2a02:6bf:8006::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-01 | Announced |
| 2a02:6bf:a000::/35 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-08-01 | Announced |
| 2a02:6bf:a005::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-16 | Announced |
| 2a02:6bf:a008::/48 | RIPE | Yandex enterprise network | YANDEX-MNT | 2025-07-16 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS44534 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-DATAIX | RIPE | Lists AS44534 as a direct member |
AS-GLOBAL-NET | RIPE | Lists AS44534 as a direct member |
AS-GLOBAL-NET-V6 | RIPE | Lists AS44534 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS44534 as a direct member |
AS-MF-MGSM | RIPE | Lists AS44534 as a direct member |
AS-MSK | RIPE | Lists AS44534 as a direct member |
AS-MTU | RIPE | Lists AS44534 as a direct member |
AS-MTU2 | RIPE | Lists AS44534 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS44534 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS44534 as a direct member |
AS-ROSTELECOM | RIPE | Lists AS44534 as a direct member |
AS57304:AS-RETN-RU | RIPE | Lists AS44534 as a direct member |
AS57304:AS-RETN6-RU | RIPE | Lists AS44534 as a direct member |
RPKI from rpki-client, validated 2026-10-24 19:55 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-24. Cross-check on bgp.he.net.