bgpreport

Network · data from 2026-11-12

AS154859 KINETLLC-AS-US - Kinet LLC

Registry name: KINETLLC-AS-US - Kinet LLC, US · not in PeeringDB

8IPv4 routes 87.5% RPKI valid · 50.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 4 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
20Route objects not announced registered with origin AS154859, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS154859, 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.
23.26.154.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.54.0.0/24 Valid Nonecovered by 84.54.0.0/23 673 100% 67
84.54.1.0/24 Valid Nonecovered by 84.54.0.0/23 673 100% 67
141.11.150.0/24 Valid Nonecovered by 141.11.150.0/23 671 100% 67
23.26.139.0/24 Valid RIR databaseARIN 673 100% 67
23.129.68.0/24 Valid RIR databaseARIN 673 100% 67
84.54.0.0/23 Valid RIR databaseRADB, RIPE 667 99% 67
141.11.150.0/23 Valid RIR databaseRADB, RIPE 667 99% 67
2602:faa8:260::/44 Valid RIR databaseARIN 635 100% 69

AS-SET

AS154859 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 25 are in fix.csv.

  • ROA: origin1
  • Route object: none4
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: origin23.26.154.0/24ROAs covering it name AS263812, not AS154859. If AS154859 should announce it, add a ROA for AS154859.2 of 673
Route object: none23.26.154.0/24Route objects for it name AS263812. Add a route object with origin AS154859 in the RIR database for the space.2 of 673
Route object: none84.54.0.0/24No route object for it. A route object for 84.54.0.0/23 with origin AS154859 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154859 in the RIR database for the space.673 of 673
Route object: none84.54.1.0/24No route object for it. A route object for 84.54.0.0/23 with origin AS154859 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154859 in the RIR database for the space.673 of 673
Route object: none141.11.150.0/24No route object for it. A route object for 141.11.150.0/23 with origin AS154859 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154859 in the RIR database for the space.671 of 673

Route objects not announced

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

199.244.176.0/22ARINValid
2a0f:1cc1::/32RIPEInvalid: origin
2a0f:1cc1:1000::/36RIPEInvalid: origin
2a0f:1cc1:1100::/40RIPEInvalid: origin
2a0f:1cc1:1200::/40RIPEInvalid: origin
2a0f:1cc1:1300::/40RIPEInvalid: origin
2a0f:1cc1:1400::/40RIPEInvalid: origin
2a0f:1cc1:1500::/40RIPEInvalid: origin
2a0f:1cc1:1600::/40RIPEInvalid: origin
2a0f:1cc1:1700::/40RIPEInvalid: origin
2a0f:1cc1:2000::/36RIPEInvalid: origin
2a0f:1cc1:2100::/40RIPEInvalid: origin
2a0f:1cc1:2200::/40RIPEInvalid: origin
2a0f:1cc1:3000::/36RIPEInvalid: origin
2a0f:1cc1:3100::/40RIPEInvalid: origin
2a0f:1cc1:8000::/35RIPEInvalid: origin
2a0f:1cc1:a000::/35RIPEInvalid: origin
2a0f:1cc1:c000::/35RIPEInvalid: origin
2a0f:1cc1:e000::/36RIPEInvalid: origin
2a0f:1cc1:f000::/36RIPEInvalid: origin

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.