Network · data from 2026-11-12
AS21713 BULLOCH
Registry name: BULLOCH - Bulloch County Rural Telephone Cooperative, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21713, 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.
| 72.162.196.0/24 | No ROA | Nonecovered by 72.162.196.0/23 | 667 99% |
| 72.162.197.0/24 | No ROA | Nonecovered by 72.162.196.0/23 | 667 99% |
| 72.162.196.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.189.250.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 66.172.64.0/19 | Valid | RIR databaseARIN, RADB | 672 100% |
| 104.160.48.0/20 | Valid | RIR databaseARIN, RADB | 672 100% |
| 168.182.64.0/18 | Valid | RIR databaseARIN, RADB | 672 100% |
| 209.166.98.0/23 | Valid | RIR databaseARIN, RADB | 672 100% |
| 209.166.98.0/24 | Valid | RIR databaseARIN | 672 100% |
| 209.166.99.0/24 | Valid | RIR databaseARIN | 672 100% |
| 216.14.64.0/20 | Valid | RIR databaseARIN, RADB | 672 100% |
| 66.172.64.0/20 | Valid | RIR databaseARIN, RADB | 670 100% |
| 66.172.80.0/20 | Valid | RIR databaseARIN, RADB | 670 100% |
| 104.160.48.0/21 | Valid | RIR databaseARIN, RADB | 670 100% |
| 104.160.56.0/21 | Valid | RIR databaseARIN, RADB | 670 100% |
| 168.182.64.0/19 | Valid | RIR databaseARIN, RADB | 670 100% |
| 168.182.96.0/19 | Valid | RIR databaseARIN, RADB | 670 100% |
| 216.14.64.0/21 | Valid | RIR databaseARIN, RADB | 670 100% |
| 216.14.72.0/21 | Valid | RIR databaseARIN, RADB | 670 100% |
| 216.14.66.0/24 | Valid | RIR databaseARIN, RADB | 668 99% |
| 2605:c380::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS21713: AS21713:AS-BULLOCH. 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 (AS21713 isn't in the set, or no route object for AS21713 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 | AS21713 in it | Not covered |
|---|---|---|---|---|---|
| AS21713:AS-BULLOCH | RADB | 1 | 1 | Yes | 0 |
| ARIN (also) | 1 | 1 | 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: none3
- Route object: none2
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 72.162.196.0/24 | No ROA covers it. Add a ROA for AS21713, maxLength 24. |
| Route object: none | 72.162.196.0/24 | No route object for it. A route object for 72.162.196.0/23 with origin AS21713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21713 in the RIR database for the space. |
| ROA: none | 72.162.197.0/24 | No ROA covers it. Add a ROA for AS21713, maxLength 24. |
| Route object: none | 72.162.197.0/24 | No route object for it. A route object for 72.162.196.0/23 with origin AS21713 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21713 in the RIR database for the space. |
| ROA: none | 72.162.196.0/23 | No ROA covers it. Add a ROA for AS21713, maxLength 23. |
| Route object: RIR | 72.162.196.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS21713 whose prefix no peer sees AS21713 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 76.78.174.0/24 | ARIN | No ROA |
| 76.78.175.0/24 | ARIN | No ROA |
| 165.166.254.0/23 | 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.