bgpreport

Network · data from 2026-11-12

AS44894 UCMA-AS Ukrchermetavtomatika LLC

Registry name: UCMA-AS Ukrchermetavtomatika LLC, UA · not in PeeringDB

33IPv4 routes 93.9% RPKI valid · 84.8% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS44894, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS44894, 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.

194.247.42.0/24 No ROA RIR databaseRIPE 671 100% 68
45.128.148.0/24 No ROA RIR databaseRIPE 670 100% 67
2a02:c6c1:c::/48 No ROA RIR databaseRIPE 629 99% 69
194.150.104.0/23 Valid None 672 100% 67
194.107.230.0/24 Valid Nonecovered by 194.107.230.0/23 671 100% 68
194.107.231.0/24 Valid Nonecovered by 194.107.230.0/23 671 100% 68
194.110.2.0/24 Valid Nonecovered by 194.110.2.0/23 671 100% 68
194.110.3.0/24 Valid Nonecovered by 194.110.2.0/23 671 100% 68
91.193.128.0/24 Valid RIR databaseRIPE 672 100% 67
91.203.61.0/24 Valid RIR databaseRIPE 672 100% 67
193.150.49.0/24 Valid RIR databaseRIPE 672 100% 67
194.150.104.0/24 Valid RIR databaseRIPE 672 100% 67
89.21.76.0/24 Valid RIR databaseRIPE 671 100% 68
89.21.77.0/24 Valid RIR databaseRIPE 671 100% 68
91.193.128.0/22 Valid RIR databaseRIPE 671 100% 68
91.193.128.0/23 Valid RIR databaseRIPE 671 100% 68
91.193.129.0/24 Valid RIR databaseRIPE 671 100% 68
91.193.130.0/23 Valid RIR databaseRIPE 671 100% 68
91.193.130.0/24 Valid RIR databaseRIPE 671 100% 68
91.193.131.0/24 Valid RIR databaseRIPE 671 100% 68
91.203.60.0/22 Valid RIR databaseRIPE 671 100% 68
91.203.60.0/23 Valid RIR databaseRIPE 671 100% 68
91.203.60.0/24 Valid RIR databaseRIPE 671 100% 68
91.203.62.0/23 Valid RIR databaseRIPE 671 100% 68
91.203.62.0/24 Valid RIR databaseRIPE 671 100% 68
91.203.63.0/24 Valid RIR databaseRIPE 671 100% 68
91.247.76.0/24 Valid RIR databaseRIPE 671 100% 68
194.107.230.0/23 Valid RIR databaseRIPE 671 100% 68
194.110.2.0/23 Valid RIR databaseRIPE 671 100% 68
194.150.105.0/24 Valid RIR databaseRIPE 671 100% 68
194.150.106.0/24 Valid RIR databaseRIPE 671 100% 68
38.244.192.0/24 Valid RIR databaseARIN, RADB 670 100% 67
130.0.232.0/21 Valid RIR databaseRIPE 668 99% 67
2001:67c:2f2c::/48 Valid RIR databaseRIPE 635 100% 69
89.21.78.0/24 Valid RIR databaseRIPE 280 42% 59

AS-SET

AS44894 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: none3
  • Route object: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none194.247.42.0/24No ROA covers it. Add a ROA for AS44894, maxLength 24.671 of 673
ROA: none45.128.148.0/24No ROA covers it. Add a ROA for AS44894, maxLength 24.670 of 673
ROA: none2a02:c6c1:c::/48No ROA covers it. Add a ROA for AS44894, maxLength 48.629 of 636
Route object: none194.150.104.0/23No route object for it. Add a route object with origin AS44894 in the RIR database for the space.672 of 673
Route object: none194.107.230.0/24No route object for it. A route object for 194.107.230.0/23 with origin AS44894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44894 in the RIR database for the space.671 of 673
Route object: none194.107.231.0/24No route object for it. A route object for 194.107.230.0/23 with origin AS44894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44894 in the RIR database for the space.671 of 673
Route object: none194.110.2.0/24No route object for it. A route object for 194.110.2.0/23 with origin AS44894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44894 in the RIR database for the space.671 of 673
Route object: none194.110.3.0/24No route object for it. A route object for 194.110.2.0/23 with origin AS44894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44894 in the RIR database for the space.671 of 673

Route objects not announced

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

89.21.79.0/24RIPENo ROA
217.70.8.0/24RIPENo ROA
2a0e:40c0:1::/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.