bgpreport

Network · data from 2026-11-12

AS2698 Iowa State University

Registry name: IASTATE-AS - Iowa State University of Science and Technology, US · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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 AS2698, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS2698, 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.
64.113.64.0/19 Valid RIR databaseARIN 671 100% 69
65.110.224.0/19 Valid RIR databaseARIN 671 100% 69
192.188.159.0/24 Valid RIR databaseARIN 671 100% 69
192.188.160.0/22 Valid RIR databaseARIN 671 100% 69
192.245.179.0/24 Valid RIR databaseARIN 671 100% 69
205.237.112.0/20 Valid RIR databaseARIN 671 100% 69
129.186.0.0/16 Valid RIR databaseARIN 669 99% 69
2610:130:100::/40 Valid RIR databaseALTDB, ARIN 632 99% 69
2602:f43f::/36 Valid RIR databaseARIN 631 99% 69

AS-SET

PeeringDB's irr_as_set for AS2698: ARIN::AS2698:AS-IAST-CONE ARIN::AS2698:RS-IASTATE-CONE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS2698 isn't in the set, or no route object for AS2698 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS2698 in itNot covered
ARIN::AS2698:AS-IAST-CONE ARIN 221113 Yes 0
ARIN::AS2698:RS-IASTATE-CONE A route-set, not an AS-SET; route-sets aren't expanded.

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 AS2698 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.