bgpreport

Network · data from 2026-11-12

AS44284 TRONIC

Registry name: TRONIC-AS P.H.U TRONIC, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44284, 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.194.199.134/32 No ROA Nonecovered by 91.194.198.0/23 7 1%low visibility 11
195.93.162.1/32 No ROA Nonecovered by 195.93.162.0/23 7 1%low visibility 11
195.93.162.14/32 No ROA Nonecovered by 195.93.162.0/23 7 1%low visibility 11
195.93.162.16/32 No ROA Nonecovered by 195.93.162.0/23 7 1%low visibility 11
195.93.162.54/32 No ROA Nonecovered by 195.93.162.0/23 7 1%low visibility 11
91.194.198.0/23 No ROA RIR databaseRIPE 672 100% 66
195.93.162.0/23 No ROA RIR databaseRIPE 672 100% 66
82.177.36.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS44284's PeeringDB record names no 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 12 are in fix.csv.

  • ROA: none7
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none91.194.199.134/32No ROA covers it. Add a ROA for AS44284, maxLength 32.7 of 673
Route object: none91.194.199.134/32No route object for it. A route object for 91.194.198.0/23 with origin AS44284 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS44284 in the RIR database for the space.7 of 673
ROA: none195.93.162.1/32No ROA covers it. Add a ROA for AS44284, maxLength 32.7 of 673
Route object: none195.93.162.1/32No route object for it. A route object for 195.93.162.0/23 with origin AS44284 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS44284 in the RIR database for the space.7 of 673
ROA: none195.93.162.14/32No ROA covers it. Add a ROA for AS44284, maxLength 32.7 of 673
Route object: none195.93.162.14/32No route object for it. A route object for 195.93.162.0/23 with origin AS44284 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS44284 in the RIR database for the space.7 of 673
ROA: none195.93.162.16/32No ROA covers it. Add a ROA for AS44284, maxLength 32.7 of 673
Route object: none195.93.162.16/32No route object for it. A route object for 195.93.162.0/23 with origin AS44284 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS44284 in the RIR database for the space.7 of 673
ROA: none195.93.162.54/32No ROA covers it. Add a ROA for AS44284, maxLength 32.7 of 673
Route object: none195.93.162.54/32No route object for it. A route object for 195.93.162.0/23 with origin AS44284 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS44284 in the RIR database for the space.7 of 673
ROA: none91.194.198.0/23No ROA covers it. Add a ROA for AS44284, maxLength 23.672 of 673
ROA: none195.93.162.0/23No ROA covers it. Add a ROA for AS44284, maxLength 23.672 of 673

Route objects not announced

Every route object with origin AS44284 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.