Routing security
AS41344 VOL-AS
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS41344 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 31.185.12.0/22 | No ROA | IRR covering | 55 |
| 2a06:b400::/29 | RPKI valid | IRR | 3 |
| 31.185.8.0/22 | RPKI valid | IRR | 55 |
| 89.249.224.0/21 | RPKI valid | IRR | 55 |
| 89.249.224.0/22 | RPKI valid | IRR covering | 55 |
| 89.249.228.0/22 | RPKI valid | IRR covering | 55 |
| 89.249.232.0/22 | RPKI valid | IRR | 55 |
| 89.249.236.0/23 | RPKI valid | IRR | 55 |
| 89.249.236.0/24 | RPKI valid | IRR | 55 |
| 89.249.237.0/24 | RPKI valid | IRR covering | 55 |
| 89.249.238.0/24 | RPKI valid | IRR | 55 |
| 185.124.176.0/22 | RPKI valid | IRR | 55 |
| 185.124.176.0/23 | RPKI valid | IRR covering | 55 |
| 185.124.178.0/23 | RPKI valid | IRR covering | 55 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS41344 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 31.185.8.0/22 | /22 | RIPENCC |
| 31.185.8.0/24 | /24 | RIPENCC |
| 31.185.9.0/24 | /24 | RIPENCC |
| 31.185.10.0/24 | /24 | RIPENCC |
| 31.185.11.0/24 | /24 | RIPENCC |
| 31.185.12.0/24 | /24 | RIPENCC |
| 31.185.13.0/24 | /24 | RIPENCC |
| 31.185.14.0/24 | /24 | RIPENCC |
| 31.185.15.0/24 | /24 | RIPENCC |
| 89.249.224.0/21 | /21 | RIPENCC |
| 89.249.224.0/22 | /22 | RIPENCC |
| 89.249.226.0/24 | /24 | RIPENCC |
| 89.249.228.0/22 | /22 | RIPENCC |
| 89.249.228.0/23 | /23 | RIPENCC |
| 89.249.230.0/23 | /23 | RIPENCC |
| 89.249.231.0/24 | /24 | RIPENCC |
| 89.249.232.0/22 | /22 | RIPENCC |
| 89.249.232.0/24 | /24 | RIPENCC |
| 89.249.233.0/24 | /24 | RIPENCC |
| 89.249.235.0/24 | /24 | RIPENCC |
| 89.249.236.0/23 | /23 | RIPENCC |
| 89.249.236.0/24 | /24 | RIPENCC |
| 89.249.237.0/24 | /24 | RIPENCC |
| 89.249.238.0/24 | /24 | RIPENCC |
| 185.124.176.0/22 | /22 | RIPENCC |
| 185.124.176.0/23 | /23 | RIPENCC |
| 185.124.177.0/24 | /24 | RIPENCC |
| 185.124.178.0/23 | /23 | RIPENCC |
| 2a06:b400::/29 | /29 | 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 |
|---|---|---|---|
| AS12389 | PJSC Rostelecom | Declared | Observed |
| AS43727 | JSC KVANT-TELEKOM | Declared | Observed |
| AS31133 | PJSC MegaFon | not declared | Observed |
| AS24482 | SG.GS | not declared | Observed |
| AS37721 | Virtual Technologies & Solutions | not declared | Observed |
| AS25091 | IP-Max SA | 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 AS41344 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 |
|---|---|---|---|---|---|
| 31.185.8.0/21 | RIPE | — | MNT-VISTCOM-RIPE | 2017-09-15 | Not announced |
| 31.185.8.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2017-09-15 | Not announced |
| 31.185.9.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2017-09-15 | Not announced |
| 31.185.10.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2017-09-15 | Not announced |
| 31.185.11.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2017-09-15 | Not announced |
| 31.185.12.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2017-09-15 | Not announced |
| 31.185.13.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2017-09-15 | Not announced |
| 31.185.14.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2017-09-15 | Not announced |
| 31.185.15.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2017-09-15 | Not announced |
| 89.249.226.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2019-12-10 | Not announced |
| 89.249.228.0/23 | RIPE | Unlimited networks | MNT-VISTCOM-RIPE | 2007-06-19 | Not announced |
| 89.249.228.0/24 | RIPE | Unlimited networks | MNT-VISTCOM-RIPE | 2008-02-26 | Not announced |
| 89.249.230.0/23 | RIPE | — | MNT-VISTCOM-RIPE | 2019-12-10 | Not announced |
| 185.124.177.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2019-12-10 | Not announced |
| 31.185.8.0/22 | RIPE | — | MNT-VISTCOM-RIPE | 2024-12-29 | Announced |
| 89.249.224.0/21 | RIPE | — | MNT-VISTCOM-RIPE | 2024-07-24 | Announced |
| 89.249.232.0/22 | RIPE | — | MNT-VISTCOM-RIPE | 2024-07-24 | Announced |
| 89.249.236.0/23 | RIPE | — | MNT-VISTCOM-RIPE | 2024-08-08 | Announced |
| 89.249.236.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2019-12-10 | Announced |
| 89.249.238.0/24 | RIPE | — | MNT-VISTCOM-RIPE | 2019-12-10 | Announced |
| 185.124.176.0/22 | RIPE | JSC "Vist on-line" | MNT-VISTCOM-RIPE | 2015-11-12 | Announced |
| 2a06:b400::/29 | RIPE | — | MNT-VISTCOM-RIPE | 2026-06-22 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS41344 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-HURRICANE | RADB | Lists AS41344 as a direct member |
AS-ROSTELECOM | RIPE | Lists AS41344 as a direct member |
AS-TRANSROUTE-SPEC | RIPE | Lists AS41344 as a direct member |
AS-UNICO | RIPE | Lists AS41344 as a direct member |
AS41194:AS-RASCOM | RIPE | Lists AS41344 as a direct member |
AS41344:AS-VISTCOM | RIPE | Lists AS41344 as a direct member |
RPKI from rpki-client, validated 2026-10-18 12:08 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-18. Cross-check on bgp.he.net.