Network · data from 2026-11-12
AS21947 Blackfoot Communications Inc
Registry name: BCI - Blackfoot Telephone Cooperative, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21947, 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.
| 198.60.195.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 205.167.162.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 64.25.128.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 66.109.128.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 69.51.64.0/18 | Valid | RIR databaseARIN, RADB | 673 100% |
| 69.165.112.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.150.152.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.225.176.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 199.195.120.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 209.137.224.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 209.200.192.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 216.14.224.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 216.47.48.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 204.11.244.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 2001:1940::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
| 2604:300::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
| 2607:f8e0::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS21947: AS-BLACKFOOT. 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 (AS21947 isn't in the set, or no route object for AS21947 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 | AS21947 in it | Not covered |
|---|---|---|---|---|---|
| AS-BLACKFOOT | RADB | 37 | 1 | Yes | 1 |
| ARIN (also) | 6 | 1 | Yes | 1 |
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 6 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 198.60.195.0/24 | ROAs covering it name AS402103, not AS21947. If AS21947 should announce it, add a ROA for AS21947. |
| Route object: none | 198.60.195.0/24 | Route objects for it name AS402103. Add a route object with origin AS21947 in the RIR database for the space. |
| ROA: none | 205.167.162.0/23 | No ROA covers it. Add a ROA for AS21947, maxLength 23. |
| Route object: RIR | 205.167.162.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS21947 whose prefix no peer sees AS21947 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.129.0.0/24 | RADB | No ROA |
| 170.173.16.0/22 | RADB | No ROA |
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.