bgpreport

Network · data from 2026-11-12

AS25073 INETKOM-AS LTD "KOMIN"

Registry name: INETKOM-AS LTD "KOMIN", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25073, 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.
195.140.204.0/24 No ROA None 70 10% 29
195.140.205.0/24 No ROA None 70 10% 29
195.140.206.0/24 No ROA None 70 10% 29
195.140.207.0/24 No ROA None 70 10% 29
193.109.76.0/24 No ROA RIR databaseRIPE 671 100% 68
193.109.77.0/24 No ROA RIR databaseRIPE 671 100% 68
193.109.89.0/24 No ROA RIR databaseRIPE 671 100% 68
194.145.168.0/24 No ROA RIR databaseRIPE 671 100% 68
194.145.169.0/24 No ROA RIR databaseRIPE 671 100% 68
194.145.170.0/24 No ROA RIR databaseRIPE 671 100% 68
194.145.171.0/24 No ROA RIR databaseRIPE 671 100% 68

AS-SET

AS25073 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 15 are in fix.csv.

  • ROA: none11
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none195.140.204.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.70 of 673
Route object: none195.140.204.0/24No route object for it. Add a route object with origin AS25073 in the RIR database for the space.70 of 673
ROA: none195.140.205.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.70 of 673
Route object: none195.140.205.0/24No route object for it. Add a route object with origin AS25073 in the RIR database for the space.70 of 673
ROA: none195.140.206.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.70 of 673
Route object: none195.140.206.0/24No route object for it. Add a route object with origin AS25073 in the RIR database for the space.70 of 673
ROA: none195.140.207.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.70 of 673
Route object: none195.140.207.0/24No route object for it. Add a route object with origin AS25073 in the RIR database for the space.70 of 673
ROA: none193.109.76.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.671 of 673
ROA: none193.109.77.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.671 of 673
ROA: none193.109.89.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.671 of 673
ROA: none194.145.168.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.671 of 673
ROA: none194.145.169.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.671 of 673
ROA: none194.145.170.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.671 of 673
ROA: none194.145.171.0/24No ROA covers it. Add a ROA for AS25073, maxLength 24.671 of 673

Route objects not announced

Every route object with origin AS25073 is announced.

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.