bgpreport

Network · data from 2026-11-12

AS13855 Cedar Falls Utilities

Registry name: CFU-NET - The Municipal Communications Utility of the City of Cedar Falls, Iowa, US · PeeringDB

10IPv4 routes 80.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No 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 AS13855, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13855, 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.
67.212.96.0/19 No ROA Other IRR onlyRADB 671 100% 68
69.57.192.0/20 No ROA Other IRR onlyRADB 671 100% 68
24.149.0.0/19 Valid RIR databaseARIN, RADB 671 100% 68
64.191.8.0/22 Valid RIR databaseARIN, RADB 671 100% 68
142.147.101.0/24 Valid RIR databaseARIN, RADB 671 100% 68
168.203.8.0/22 Valid RIR databaseARIN, RADB 671 100% 68
192.101.160.0/24 Valid RIR databaseARIN, RADB 671 100% 68
192.111.20.0/22 Valid RIR databaseARIN, RADB 671 100% 68
199.168.104.0/22 Valid RIR databaseARIN, RADB 671 100% 68
209.40.80.0/22 Valid RIR databaseARIN, RADB 671 100% 68
2607:f070::/32 Valid RIR databaseARIN, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS13855: RADB::AS13855:AS-ALL. 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 (AS13855 isn't in the set, or no route object for AS13855 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 objectsAS13855 in itNot covered
RADB::AS13855:AS-ALL RADB1 member set in no database: AS400528:AS-SET-MAIN 173134 Yes 0

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

  • ROA: none2
  • Route object: RIR2
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
ROA: none67.212.96.0/19No ROA covers it. Add a ROA for AS13855, maxLength 19.671 of 673
Route object: RIR67.212.96.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.57.192.0/20No ROA covers it. Add a ROA for AS13855, maxLength 20.671 of 673
Route object: RIR69.57.192.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
AS-SET: missing memberRADB::AS13855:AS-ALLAS13855:AS-ALL (RADB) lists AS400528:AS-SET-MAIN; no IRR database read has it.

Route objects not announced

Every route object with origin AS13855 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.