asn.dev

Routing security

AS8920 VTC-AS Russia, Vladivostok

Unclassified RIPE

RPKI valid 0% 0 of 26 announcements
RPKI invalid 0 none
No ROA 26 not covered by any ROA
IRR registered 100% 0 missing · 0 other origin
ROAs 0 authorising this AS

Announcements

What this network originates

26 observed

Every prefix observed with AS8920 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
82.194.160.0/20No ROAIRR53
82.194.176.0/20No ROAIRR54
82.194.184.0/23No ROAIRR covering54
82.194.186.0/23No ROAIRR covering51
82.194.188.0/22No ROAIRR54
95.129.72.0/21No ROAIRR53
178.249.72.0/21No ROAIRR53
178.249.72.0/24No ROAIRR covering53
178.249.73.0/24No ROAIRR covering53
178.249.74.0/24No ROAIRR covering53
178.249.75.0/24No ROAIRR covering53
185.185.136.0/22No ROAIRR53
185.185.136.0/24No ROAIRR covering53
185.185.137.0/24No ROAIRR covering53
185.185.138.0/24No ROAIRR covering53
185.185.139.0/24No ROAIRR covering53
212.16.192.0/19No ROAIRR53
212.16.192.0/20No ROAIRR53
212.16.192.0/22No ROAIRR covering53
212.16.197.0/24No ROAIRR covering53
212.16.198.0/23No ROAIRR covering53
212.16.198.0/24No ROAIRR covering53
212.16.200.0/21No ROAIRR covering53
212.16.203.0/24No ROAIRR54
212.16.208.0/20No ROAIRR53
212.16.220.0/24No ROAIRR covering54

RPKI · ROAs

Route origin authorisations

0 ROAs

Signed statements by address holders that AS8920 may originate these prefixes, up to the maximum length shown.

No ROA names this AS as an authorised origin.

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

18 objects · 8 not announced

Route objects naming AS8920 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.

PrefixSourceDescriptionMaintainerChangedRouting
82.194.160.0/19RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
82.194.160.0/19RIPEFar Eastern Branch JSC RTComm.RUAS8920-MNT2024-09-24Not announced
212.16.202.0/24RIPECJSC VostoktelecomAS8920-MNT2010-08-10Not announced
212.16.209.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
212.16.212.0/24RIPECJSC VostoktelecomAS8920-MNT2010-08-10Not announced
212.16.218.0/24RADBProxy-registered route objectMAINT-AS34912025-03-28Not announced
212.16.218.0/24RIPECJSC VostoktelecomAS8920-MNT2010-08-10Not announced
2a02:dbc0::/29RIPECJSC VostoktelecomAS8920-MNT2013-08-14Not announced
82.194.160.0/20RIPEJSC RTComm.RUAS8920-MNT2024-04-05Announced
82.194.176.0/20RIPEJSC VostoktelecomAS8920-MNT2017-01-11Announced
82.194.188.0/22RADBProxy-registered route objectMAINT-AS34912025-03-28Announced
95.129.72.0/21RIPEJSC RTComm.RUAS8920-MNT2024-09-24Announced
178.249.72.0/21RIPEJSC RTComm.RUAS8920-MNT2024-09-24Announced
185.185.136.0/22RIPEJSC RTComm.RUAS8920-MNT2024-09-24Announced
212.16.192.0/19RIPEFar Eastern Branch JSC RTComm.RUAS8920-MNT2024-09-24Announced
212.16.192.0/20RIPEJSC RTComm.RUAS8920-MNT2024-04-09Announced
212.16.203.0/24RIPECJSC VostoktelecomAS8920-MNT2003-09-23Announced
212.16.208.0/20RIPECJSC VostoktelecomAS8920-MNT2007-10-25Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS8920 directly show who expects to carry it.

AS-setWhereRelationship
AS-BLOCK-SETRIPELists AS8920 as a direct member
AS-BLOCKED-RURIPELists AS8920 as a direct member
AS-BTN-CUSTOMERSRADBLists AS8920 as a direct member
AS-HURRICANERADBLists AS8920 as a direct member
AS-MTURIPELists AS8920 as a direct member
AS-MTU2RIPELists AS8920 as a direct member
AS-PORTALRIPELists AS8920 as a direct member
AS-ROSTELECOMRIPELists AS8920 as a direct member
AS-VTCRIPELists AS8920 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.