bgpreport

Network · data from 2026-11-12

AS19793 LINIVO - Linivo LLC

Registry name: LINIVO - Linivo LLC, US · not in PeeringDB

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

Announced routes

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

94.183.231.0/24 Invalid: origin Other origin only 3 0%low visibility 1
93.152.230.0/24 Invalid: origin Other origin only 2 0%low visibility 2
94.183.230.0/24 Invalid: origin Other origin only 1 0%low visibility 1
124.42.132.0/24 No ROA None 11 2%low visibility 7
124.42.133.0/24 No ROA None 11 2%low visibility 7
124.42.134.0/24 No ROA None 11 2%low visibility 7
124.42.135.0/24 No ROA None 11 2%low visibility 7
207.170.152.0/22 No ROA None 11 2%low visibility 7
207.170.156.0/22 No ROA None 11 2%low visibility 7
207.170.164.0/22 No ROA None 11 2%low visibility 7
207.170.180.0/22 No ROA None 11 2%low visibility 7
207.170.188.0/23 No ROA None 11 2%low visibility 7
113.20.56.0/22 Valid RIR databaseAPNIC 673 100% 67
155.103.140.0/22 Valid RIR databaseARIN 673 100% 67
207.170.168.0/23 Valid RIR databaseARIN 673 100% 67
207.170.190.0/23 Valid RIR databaseARIN 673 100% 67
223.29.132.0/22 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS19793 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 26 are in fix.csv.

  • ROA: origin3
  • ROA: none9
  • Route object: none12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin94.183.231.0/24ROAs covering it name AS205536, not AS19793. If AS19793 should announce it, add a ROA for AS19793.3 of 673
Route object: none94.183.231.0/24Route objects for it name AS205536. Add a route object with origin AS19793 in the RIR database for the space.3 of 673
ROA: origin93.152.230.0/24ROAs covering it name AS25211, not AS19793. If AS19793 should announce it, add a ROA for AS19793.2 of 673
Route object: none93.152.230.0/24Route objects for it name AS25211. Add a route object with origin AS19793 in the RIR database for the space.2 of 673
ROA: origin94.183.230.0/24ROAs covering it name AS213915, not AS19793; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS19793 should announce it, add a ROA for AS19793.1 of 673
Route object: none94.183.230.0/24Route objects for it name AS213915. Add a route object with origin AS19793 in the RIR database for the space.1 of 673
ROA: none124.42.132.0/24No ROA covers it. Add a ROA for AS19793, maxLength 24.11 of 673
Route object: none124.42.132.0/24No route object for it. Add a route object with origin AS19793 in the RIR database for the space.11 of 673
ROA: none124.42.133.0/24No ROA covers it. Add a ROA for AS19793, maxLength 24.11 of 673
Route object: none124.42.133.0/24No route object for it. Add a route object with origin AS19793 in the RIR database for the space.11 of 673
ROA: none124.42.134.0/24No ROA covers it. Add a ROA for AS19793, maxLength 24.11 of 673
Route object: none124.42.134.0/24No route object for it. Add a route object with origin AS19793 in the RIR database for the space.11 of 673
ROA: none124.42.135.0/24No ROA covers it. Add a ROA for AS19793, maxLength 24.11 of 673
Route object: none124.42.135.0/24No route object for it. Add a route object with origin AS19793 in the RIR database for the space.11 of 673
ROA: none207.170.152.0/22No ROA covers it. Add a ROA for AS19793, maxLength 22.11 of 673
Route object: none207.170.152.0/22No route object for it. Add a route object with origin AS19793 in the RIR database for the space.11 of 673
ROA: none207.170.156.0/22No ROA covers it. Add a ROA for AS19793, maxLength 22.11 of 673
Route object: none207.170.156.0/22No route object for it. Add a route object with origin AS19793 in the RIR database for the space.11 of 673
ROA: none207.170.164.0/22No ROA covers it. Add a ROA for AS19793, maxLength 22.11 of 673
Route object: none207.170.164.0/22No route object for it. Add a route object with origin AS19793 in the RIR database for the space.11 of 673
ROA: none207.170.180.0/22No ROA covers it. Add a ROA for AS19793, maxLength 22.11 of 673
Route object: none207.170.180.0/22No route object for it. Add a route object with origin AS19793 in the RIR database for the space.11 of 673
ROA: none207.170.188.0/23No ROA covers it. Add a ROA for AS19793, maxLength 23.11 of 673
Route object: none207.170.188.0/23No route object for it. Add a route object with origin AS19793 in the RIR database for the space.11 of 673

Route objects not announced

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

199.7.210.0/24ARINValid
199.7.211.0/24ARINValid

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.