Network · data from 2026-11-12

AS35874 KRESA-ASN - Kalamazoo RESA

Registry name: KRESA-ASN - Kalamazoo RESA, US · not in PeeringDB

15IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS35874, seen from no peer

Announced routes

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


69.58.32.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.33.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.36.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.37.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.38.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.39.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.41.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.42.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.43.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.48.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.49.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.50.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.51.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.52.0/24	Valid	RIR databaseARIN	668 99%	68
69.58.53.0/24	Valid	RIR databaseARIN	668 99%	68

AS-SET

AS35874 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS35874 is announced.

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.