bgpreport

Network · data from 2026-11-12

AS26306 THE-KARCHER-GROUP - The Karcher Group Inc.

Registry name: THE-KARCHER-GROUP - The Karcher Group Inc., US · not in PeeringDB

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

Announced routes

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

12.229.4.0/23 No ROA Other origin only 671 100% 69
12.191.32.0/23 No ROA Other IRR onlyALTDB 671 100% 68
12.191.50.0/23 No ROA Other IRR onlyALTDB 671 100% 68
63.119.26.0/24 No ROA Other IRR onlyALTDB 671 100% 68
65.42.56.0/23 No ROA Other IRR onlyALTDB 671 100% 68
68.23.202.0/23 No ROA Other IRR onlyALTDB 671 100% 68
68.73.74.0/24 No ROA Other IRR onlyALTDB 671 100% 68
69.208.26.0/24 No ROA Other IRR onlyALTDB 671 100% 68
71.158.102.0/23 No ROA Other IRR onlyALTDB 671 100% 68

AS-SET

AS26306 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 24 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none12.229.4.0/23No ROA covers it. Add a ROA for AS26306, maxLength 23.671 of 673
Route object: none12.229.4.0/23Route objects for it name AS19009, AS23119. Add a route object with origin AS26306 in the RIR database for the space.671 of 673
ROA: none12.191.32.0/23No ROA covers it. Add a ROA for AS26306, maxLength 23.671 of 673
Route object: RIR12.191.32.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none12.191.50.0/23No ROA covers it. Add a ROA for AS26306, maxLength 23.671 of 673
Route object: RIR12.191.50.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none63.119.26.0/24No ROA covers it. Add a ROA for AS26306, maxLength 24.671 of 673
Route object: RIR63.119.26.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none65.42.56.0/23No ROA covers it. Add a ROA for AS26306, maxLength 23.671 of 673
Route object: RIR65.42.56.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none68.23.202.0/23No ROA covers it. Add a ROA for AS26306, maxLength 23.671 of 673
Route object: RIR68.23.202.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none68.73.74.0/24No ROA covers it. Add a ROA for AS26306, maxLength 24.671 of 673
Route object: RIR68.73.74.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none69.208.26.0/24No ROA covers it. Add a ROA for AS26306, maxLength 24.671 of 673
Route object: RIR69.208.26.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none71.158.102.0/23No ROA covers it. Add a ROA for AS26306, maxLength 23.671 of 673
Route object: RIR71.158.102.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

12.199.24.0/22ALTDBNo ROA
63.84.214.0/24ALTDBNo ROA
65.42.56.0/24ALTDBNo ROA
67.109.86.0/24ALTDBNo ROA
99.16.32.0/21ALTDBNo ROA
208.50.70.0/23ALTDBNo 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.