bgpreport

Network · data from 2026-11-12

AS24607 Ignitis grupės paslaugų centras

Registry name: LENET UAB "Ignitis grupes paslaugu centras", LT · PeeringDB

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

Announced routes

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

81.16.228.52/32 No ROA Nonecovered by 81.16.224.0/21 5 1%low visibility 10
81.16.228.58/32 No ROA Nonecovered by 81.16.224.0/21 5 1%low visibility 10
81.16.228.136/32 No ROA Nonecovered by 81.16.224.0/21 5 1%low visibility 10
81.16.228.138/32 No ROA Nonecovered by 81.16.224.0/21 5 1%low visibility 10
81.16.228.139/32 No ROA Nonecovered by 81.16.224.0/21 5 1%low visibility 10
81.16.228.148/32 No ROA Nonecovered by 81.16.224.0/21 5 1%low visibility 10
81.16.224.0/21 No ROA RIR databaseRIPE 672 100% 66

AS-SET

AS24607'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 14 are in fix.csv.

  • ROA: none7
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none81.16.228.52/32No ROA covers it. Add a ROA for AS24607, maxLength 32.5 of 673
Route object: none81.16.228.52/32No route object for it. A route object for 81.16.224.0/21 with origin AS24607 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24607 in the RIR database for the space.5 of 673
ROA: none81.16.228.58/32No ROA covers it. Add a ROA for AS24607, maxLength 32.5 of 673
Route object: none81.16.228.58/32No route object for it. A route object for 81.16.224.0/21 with origin AS24607 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24607 in the RIR database for the space.5 of 673
ROA: none81.16.228.136/32No ROA covers it. Add a ROA for AS24607, maxLength 32.5 of 673
Route object: none81.16.228.136/32No route object for it. A route object for 81.16.224.0/21 with origin AS24607 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24607 in the RIR database for the space.5 of 673
ROA: none81.16.228.138/32No ROA covers it. Add a ROA for AS24607, maxLength 32.5 of 673
Route object: none81.16.228.138/32No route object for it. A route object for 81.16.224.0/21 with origin AS24607 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24607 in the RIR database for the space.5 of 673
ROA: none81.16.228.139/32No ROA covers it. Add a ROA for AS24607, maxLength 32.5 of 673
Route object: none81.16.228.139/32No route object for it. A route object for 81.16.224.0/21 with origin AS24607 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24607 in the RIR database for the space.5 of 673
ROA: none81.16.228.148/32No ROA covers it. Add a ROA for AS24607, maxLength 32.5 of 673
Route object: none81.16.228.148/32No route object for it. A route object for 81.16.224.0/21 with origin AS24607 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS24607 in the RIR database for the space.5 of 673
ROA: none81.16.224.0/21No ROA covers it. Add a ROA for AS24607, maxLength 21.672 of 673

Route objects not announced

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

2a02:25d0::/32RIPENo 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.