Routing security
AS50022 ORIONNET-MNSK
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS50022 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 213.110.240.0/20 | RPKI valid | IRR | 55 |
| 213.110.253.0/24 | RPKI valid | IRR | 55 |
| 213.110.254.0/24 | RPKI valid | IRR | 55 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS50022 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 213.110.240.0/20 | /24 | RIPENCC |
| 2a05:7400:c000::/34 | /48 | RIPENCC |
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 |
|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Declared | Observed |
| AS20485 | Joint Stock Company TransTeleCom | Declared | Observed |
| AS50427 | Orion Telecom LLC | 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 AS50022 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 |
|---|---|---|---|---|---|
| 2a05:7400:c000::/34 | RIPE | Orion Telecom, Minusinsk | ORIONMNSK-MNT | 2024-11-18 | Not announced |
| 213.110.240.0/20 | RIPE | Orion telecom, Minusinsk | ORIONMNSK-MNT | 2023-01-16 | Announced |
| 213.110.253.0/24 | RIPE | — | ORIONMNSK-MNT | 2025-11-19 | Announced |
| 213.110.254.0/24 | RIPE | — | ORIONMNSK-MNT | 2025-11-19 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS50022 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-ABAKANNET | RIPE | Lists AS50022 as a direct member |
AS-HURRICANE | RADB | Lists AS50022 as a direct member |
AS-MF-KRS-IX | RIPE | Lists AS50022 as a direct member |
AS-MILECOM | RIPE | Lists AS50022 as a direct member |
AS-MILECOM-RS | RIPE | Lists AS50022 as a direct member |
AS-MTU | RIPE | Lists AS50022 as a direct member |
AS-MTU2 | RIPE | Lists AS50022 as a direct member |
AS-RED-IX-PEERS | RIPE | Lists AS50022 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS50022 as a direct member |
AS-ROSTELECOM | RIPE | Lists AS50022 as a direct member |
AS-SIBIR-IX | RIPE | Lists AS50022 as a direct member |
AS-STORMWALL-SET | RADB | Lists AS50022 as a direct member |
AS-STORMWALL-SET | RIPE | Lists AS50022 as a direct member |
AS-TTK | RIPE | Lists AS50022 as a direct member |
AS209141:AS-RUCUST | RADB | Lists AS50022 as a direct member |
AS50022:AS-ORIONNET | RIPE | Lists AS50022 as a direct member |
RPKI from rpki-client, validated 2026-10-17 12:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, collected 2026-10-17. Cross-check on bgp.he.net.