Network · data from 2026-11-12
AS27321 ISC F-ROOT OAK1
Registry name: ISC-F-AS - Internet Systems Consortium, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27321, 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.
| 149.20.0.0/24 | Valid | RIR databaseARIN | 655 97% |
| 149.20.2.0/24 | Valid | RIR databaseARIN, RADB | 654 97% |
| 149.20.3.0/24 | Valid | RIR databaseARIN | 654 97% |
| 149.20.4.0/24 | Valid | RIR databaseARIN | 654 97% |
| 149.20.57.0/24 | Valid | RIR databaseARIN | 654 97% |
| 149.20.66.0/24 | Valid | RIR databaseARIN, RADB | 654 97% |
| 192.158.248.0/24 | Valid | RIR databaseARIN, RADB | 654 97% |
| 192.158.249.0/24 | Valid | RIR databaseARIN | 654 97% |
| 2001:500:6b::/48 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS27321: RADB::AS-ISC-OAK1. 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 (AS27321 isn't in the set, or no route object for AS27321 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.
| Name | Database | ASNs | Sets | AS27321 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS-ISC-OAK1 | RADB | 2 | 1 | Yes | 0 |
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 AS27321 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.