bgpreport

Network · data from 2026-11-12

AS26317 Lisa Communications

Registry name: AS26317 - Lisa Communications Ltd, TT · PeeringDB

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

Announced routes

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

190.97.96.0/24 No ROA None 672 100% 67
190.97.97.0/24 No ROA None 672 100% 67
200.3.176.0/24 No ROA Other origin onlycovered by 200.3.176.0/21 672 100% 67
200.3.177.0/24 No ROA Other origin onlycovered by 200.3.176.0/21 672 100% 67
200.3.178.0/24 No ROA Other origin onlycovered by 200.3.176.0/21 672 100% 67
200.3.179.0/24 No ROA Other origin onlycovered by 200.3.176.0/21 672 100% 67
200.3.180.0/24 No ROA Other origin onlycovered by 200.3.176.0/21 672 100% 67
200.3.182.0/24 No ROA Other origin onlycovered by 200.3.176.0/21 672 100% 67
200.3.183.0/24 No ROA Other origin onlycovered by 200.3.176.0/21 672 100% 67
200.3.181.0/24 No ROA Other origin onlycovered by 200.3.176.0/21 671 100% 67

AS-SET

AS26317'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 22 are in fix.csv.

  • ROA: none10
  • Route object: none10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none190.97.96.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.672 of 673
Route object: none190.97.96.0/24No route object for it. Add a route object with origin AS26317 in the RIR database for the space.672 of 673
ROA: none190.97.97.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.672 of 673
Route object: none190.97.97.0/24No route object for it. Add a route object with origin AS26317 in the RIR database for the space.672 of 673
ROA: none200.3.176.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.672 of 673
Route object: none200.3.176.0/24Route objects for it name AS32034. A route object for 200.3.176.0/21 with origin AS26317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26317 in the RIR database for the space.672 of 673
ROA: none200.3.177.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.672 of 673
Route object: none200.3.177.0/24Route objects for it name AS32034. A route object for 200.3.176.0/21 with origin AS26317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26317 in the RIR database for the space.672 of 673
ROA: none200.3.178.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.672 of 673
Route object: none200.3.178.0/24Route objects for it name AS32034. A route object for 200.3.176.0/21 with origin AS26317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26317 in the RIR database for the space.672 of 673
ROA: none200.3.179.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.672 of 673
Route object: none200.3.179.0/24Route objects for it name AS32034. A route object for 200.3.176.0/21 with origin AS26317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26317 in the RIR database for the space.672 of 673
ROA: none200.3.180.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.672 of 673
Route object: none200.3.180.0/24Route objects for it name AS32034. A route object for 200.3.176.0/21 with origin AS26317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26317 in the RIR database for the space.672 of 673
ROA: none200.3.182.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.672 of 673
Route object: none200.3.182.0/24Route objects for it name AS32034. A route object for 200.3.176.0/21 with origin AS26317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26317 in the RIR database for the space.672 of 673
ROA: none200.3.183.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.672 of 673
Route object: none200.3.183.0/24Route objects for it name AS32034. A route object for 200.3.176.0/21 with origin AS26317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26317 in the RIR database for the space.672 of 673
ROA: none200.3.181.0/24No ROA covers it. Add a ROA for AS26317, maxLength 24.671 of 673
Route object: none200.3.181.0/24Route objects for it name AS32034. A route object for 200.3.176.0/21 with origin AS26317 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26317 in the RIR database for the space.671 of 673

Route objects not announced

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

66.178.87.0/24RADBNo ROA
200.3.176.0/21RADBNo 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.