bgpreport

Network · data from 2026-11-12

AS394111 Foothills Rural Telephone Cooperative Corporation, Inc.

Registry name: FRTCCNET - Foothills Rural Telephone Cooperative Corporation, Inc., US · PeeringDB

8IPv4 routes 87.5% 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
1No 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 AS394111, seen from no peer

Announced routes

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

38.110.132.0/22 No ROA Other IRR onlyRADB 673 100% 67
64.147.224.0/20 Valid Other IRR onlyRADB 673 100% 67
172.97.16.0/20 Valid Other IRR onlyRADB 673 100% 67
192.225.240.0/20 Valid Other IRR onlyRADB 673 100% 67
206.72.212.0/22 Valid Other IRR onlyRADB 673 100% 67
207.174.144.0/21 Valid Other IRR onlyRADB 673 100% 67
216.213.0.0/20 Valid Other IRR onlyRADB 673 100% 67
2607:6f00::/32 Valid Other IRR onlyRADB 635 100% 68
38.20.144.0/22 Valid RIR databaseARIN 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS394111: RADB::AS-394111. 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 (AS394111 isn't in the set, or no route object for AS394111 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 objectsAS394111 in itNot covered
RADB::AS-394111 RADB 3119 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 9 are in fix.csv.

  • ROA: none1
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none38.110.132.0/22No ROA covers it. Add a ROA for AS394111, maxLength 22.673 of 673
Route object: RIR38.110.132.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR64.147.224.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR172.97.16.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.225.240.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR206.72.212.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR207.174.144.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR216.213.0.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2607:6f00::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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