Routing security
AS50427 ORIONNET-ABK
Residential RIPE
Announcements
What this network originates
Every prefix observed with AS50427 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a05:7400:8000::/34 | RPKI valid | IRR | 31 |
| 86.62.4.0/23 | RPKI valid | IRR | 53 |
| 86.62.4.0/24 | RPKI valid | IRR | 53 |
| 86.62.5.0/24 | RPKI valid | IRR | 53 |
| 109.226.248.0/24 | RPKI valid | IRR | 53 |
| 176.116.184.0/21 | RPKI valid | IRR | 53 |
| 176.116.184.0/22 | RPKI valid | IRR | 53 |
| 176.116.184.0/23 | RPKI valid | IRR | 53 |
| 176.116.186.0/23 | RPKI valid | IRR | 53 |
| 176.116.188.0/22 | RPKI valid | IRR | 53 |
| 176.116.188.0/23 | RPKI valid | IRR | 53 |
| 176.116.190.0/23 | RPKI valid | IRR | 53 |
| 185.84.174.0/23 | RPKI valid | IRR | 53 |
| 185.84.174.0/24 | RPKI valid | IRR | 53 |
| 185.84.175.0/24 | RPKI valid | IRR | 53 |
| 185.112.224.0/22 | RPKI valid | IRR | 53 |
| 185.112.224.0/23 | RPKI valid | IRR | 53 |
| 185.112.224.0/24 | RPKI valid | IRR | 53 |
| 185.112.225.0/24 | RPKI valid | IRR | 53 |
| 185.112.226.0/23 | RPKI valid | IRR | 53 |
| 185.112.226.0/24 | RPKI valid | IRR | 53 |
| 185.112.227.0/24 | RPKI valid | IRR | 53 |
| 193.106.168.0/22 | RPKI valid | IRR | 53 |
| 193.106.168.0/24 | RPKI valid | IRR | 53 |
| 193.106.169.0/24 | RPKI valid | IRR | 53 |
| 193.106.170.0/24 | RPKI valid | IRR | 53 |
| 193.106.171.0/24 | RPKI valid | IRR | 53 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS50427 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 86.62.4.0/23 | /23 | RIPENCC |
| 86.62.4.0/24 | /24 | RIPENCC |
| 86.62.5.0/24 | /24 | RIPENCC |
| 109.226.248.0/24 | /24 | RIPENCC |
| 176.116.184.0/21 | /23 | RIPENCC |
| 176.116.184.0/22 | /23 | RIPENCC |
| 176.116.184.0/23 | /23 | RIPENCC |
| 176.116.186.0/23 | /23 | RIPENCC |
| 176.116.188.0/22 | /23 | RIPENCC |
| 176.116.188.0/23 | /23 | RIPENCC |
| 176.116.190.0/23 | /23 | RIPENCC |
| 185.84.174.0/23 | /23 | RIPENCC |
| 185.84.174.0/24 | /24 | RIPENCC |
| 185.84.175.0/24 | /24 | RIPENCC |
| 185.112.224.0/22 | /24 | RIPENCC |
| 193.106.168.0/22 | /22 | RIPENCC |
| 193.106.168.0/24 | /24 | RIPENCC |
| 193.106.169.0/24 | /24 | RIPENCC |
| 193.106.170.0/24 | /24 | RIPENCC |
| 193.106.171.0/24 | /24 | RIPENCC |
| 2a05:7400:8000::/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 |
| AS12389 | PJSC Rostelecom | Declared | Observed |
| AS31133 | PJSC MegaFon | Declared | Observed |
| AS31257 | Orion Telecom LLC | Declared | Observed |
| AS43298 | Storm Networks LLC | Declared | Observed |
| AS48858 | JSC "ER-Telecom Holding" | Declared | Observed |
| AS13094 | JSC "ER-Telecom Holding" | 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 AS50427 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 |
|---|---|---|---|---|---|
| 86.62.4.0/23 | RIPE | — | MNT-ABAKANNET | 2022-09-15 | Announced |
| 86.62.4.0/24 | RIPE | Orion telecom, Abakan | MNT-ABAKANNET | 2021-02-12 | Announced |
| 86.62.5.0/24 | RIPE | Orion telecom, Abakan | MNT-ABAKANNET | 2021-02-12 | Announced |
| 109.226.248.0/24 | RIPE | Orion telecom, Abakan | MNT-ABAKANNET | 2021-02-12 | Announced |
| 176.116.184.0/21 | RIPE | Orion Telecom LLC | MNT-ABAKANNET | 2026-07-22 | Announced |
| 176.116.184.0/22 | RIPE | Orion Telecom LLC | MNT-ABAKANNET | 2026-07-22 | Announced |
| 176.116.184.0/23 | RIPE | Orion Telecom LLC | MNT-ABAKANNET | 2026-07-22 | Announced |
| 176.116.186.0/23 | RIPE | Orion Telecom LLC | MNT-ABAKANNET | 2026-07-22 | Announced |
| 176.116.188.0/22 | RIPE | Orion Telecom LLC | MNT-ABAKANNET | 2026-07-22 | Announced |
| 176.116.188.0/23 | RIPE | Orion Telecom LLC | MNT-ABAKANNET | 2026-07-22 | Announced |
| 176.116.190.0/23 | RIPE | Orion Telecom LLC | MNT-ABAKANNET | 2026-07-22 | Announced |
| 185.84.174.0/23 | RIPE | ORIONNET | MORNING-MNT | 2016-12-08 | Announced |
| 185.84.174.0/24 | RIPE | — | MORNING-MNT | 2019-03-07 | Announced |
| 185.84.175.0/24 | RIPE | — | MORNING-MNT | 2019-03-07 | Announced |
| 185.112.224.0/22 | RIPE | Abakan city | RU-ORION-1-MNT | 2019-09-16 | Announced |
| 185.112.224.0/23 | RIPE | Abakan city | RU-ORION-1-MNT | 2019-09-16 | Announced |
| 185.112.224.0/24 | RIPE | Abakan City | RU-ORION-1-MNT | 2019-10-09 | Announced |
| 185.112.225.0/24 | RIPE | Abakan City | RU-ORION-1-MNT | 2019-10-09 | Announced |
| 185.112.226.0/23 | RIPE | Chernogorsk City | RU-ORION-1-MNT | 2019-09-16 | Announced |
| 185.112.226.0/24 | RIPE | Chernogorsk City | RU-ORION-1-MNT | 2019-10-09 | Announced |
| 185.112.227.0/24 | RIPE | Chernogorsk City | RU-ORION-1-MNT | 2019-10-09 | Announced |
| 193.106.168.0/22 | RIPE | Orion telecom, Abakan | MNT-ABAKANNET | 2021-02-12 | Announced |
| 193.106.168.0/24 | RIPE | Orion telecom, Abakan | MNT-ABAKANNET | 2021-02-12 | Announced |
| 193.106.169.0/24 | RIPE | Orion telecom, Abakan | MNT-ABAKANNET | 2021-02-12 | Announced |
| 193.106.170.0/24 | RIPE | Orion telecom, Abakan | MNT-ABAKANNET | 2021-02-12 | Announced |
| 193.106.171.0/24 | RIPE | Orion telecom, Abakan | MNT-ABAKANNET | 2021-02-12 | Announced |
| 2a05:7400:8000::/34 | RIPE | Orion Telecom, Abakan | MNT-ABAKANNET | 2024-11-18 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS50427 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-ABAKANNET | RIPE | Lists AS50427 as a direct member |
AS-HURRICANE | RADB | Lists AS50427 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS50427 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS50427 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS50427 as a direct member |
AS-SIBNET | RIPE | Lists AS50427 as a direct member |
AS-STORMWALL-SET | RADB | Lists AS50427 as a direct member |
AS-STORMWALL-SET | RIPE | Lists AS50427 as a direct member |
AS209141:AS-RUCUST | RADB | Lists AS50427 as a direct member |
AS3491:AS-CUSTOMERS-EU | RADB | Lists AS50427 as a direct member |
AS50022:AS-ORIONNET | RIPE | Lists AS50427 as a direct member |
AS50427:AS-ORIONNET | RIPE | Lists AS50427 as a direct member |
RPKI from rpki-client, validated 2026-10-16 12:09 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-16. Cross-check on bgp.he.net.