bgpreport

Network · data from 2026-11-12

AS60922 AS_KKM_IT Variti+ LLC

Registry name: AS_KKM_IT Variti+ LLC, RU · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
4No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS60922, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS60922, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

91.191.183.0/24 No ROA RIR databaseRIPE 673 100% 67
185.203.72.0/24 No ROA RIR databaseRIPE 673 100% 67
195.144.0.0/24 No ROA RIR databaseRIPE 673 100% 67
185.165.123.0/24 No ROA RIR databaseRIPE 425 63% 64

AS-SET

AS60922 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 11 are in fix.csv.

  • ROA: none4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none91.191.183.0/24No ROA covers it. Add a ROA for AS60922, maxLength 24.673 of 673
ROA: none185.203.72.0/24No ROA covers it. Add a ROA for AS60922, maxLength 24.673 of 673
ROA: none195.144.0.0/24No ROA covers it. Add a ROA for AS60922, maxLength 24.673 of 673
ROA: none185.165.123.0/24No ROA covers it. Add a ROA for AS60922, maxLength 24.425 of 673

Route objects not announced

Route objects with origin AS60922 whose prefix no peer sees AS60922 announce. Many are kept on purpose (backup routes, space announced only in some places).

151.236.80.0/24RIPEInvalid: origin
185.165.120.0/24RIPENo ROA
185.165.121.0/24RIPENo ROA
185.203.73.0/24RIPENo ROA
185.203.74.0/24RIPENo ROA
185.203.75.0/24RIPENo ROA
2a0a:e440::/48RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.