bgpreport

Network · data from 2026-11-12

AS13567 KMB1 - Kimberly-Clark Corporation

Registry name: KMB1 - Kimberly-Clark Corporation, US · not in PeeringDB

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

Announced routes

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

192.136.16.0/24 No ROA Other IRR onlyRADB 673 100% 67
205.203.64.0/19 No ROA Other IRR onlyRADB 673 100% 67
192.206.119.0/24 Valid RIR databaseARIN 673 100% 67
205.203.68.0/24 Valid RIR databaseARIN 673 100% 67
205.203.69.0/24 Valid RIR databaseARIN 673 100% 67
205.203.77.0/24 Valid RIR databaseARIN 673 100% 67
205.203.79.0/24 Valid RIR databaseARIN 673 100% 70
205.203.82.0/24 Valid RIR databaseARIN 673 100% 67
205.203.91.0/24 Valid RIR databaseARIN 673 100% 67
205.203.92.0/24 Valid RIR databaseARIN 673 100% 67
205.203.94.0/24 Valid RIR databaseARIN 673 100% 67
205.203.95.0/24 Valid RIR databaseARIN 673 100% 67
205.203.64.0/23 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

AS13567 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 10 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none192.136.16.0/24No ROA covers it. Add a ROA for AS13567, maxLength 24.673 of 673
Route object: RIR192.136.16.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.203.64.0/19No ROA covers it. Add a ROA for AS13567, maxLength 19.673 of 673
Route object: RIR205.203.64.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

165.28.0.0/16RADBNo ROA
165.28.0.0/24RADBNo ROA
165.28.72.0/21RADBNo ROA
165.28.216.0/21RADBNo ROA
165.28.228.0/23RADBNo ROA
192.216.119.0/24RADBNo 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.