Network · data from 2026-11-12
AS26209 Network Tool and Die Company
Registry name: NETWORK-TOOL - Network Tool and Die Company, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26209, 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.
| 69.44.136.0/23 | No ROA | None | 670 100% |
| 69.44.138.0/24 | No ROA | None | 670 100% |
| 69.71.112.0/23 | No ROA | RIR databaseARIN | 670 100% |
| 69.71.114.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 69.71.116.0/23 | No ROA | RIR databaseARIN | 670 100% |
| 69.71.119.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 69.71.120.0/21 | No ROA | RIR databaseARIN | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS26209: AS26209: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 (AS26209 isn't in the set, or no route object for AS26209 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 | AS26209 in it | Not covered |
|---|---|---|---|---|---|
| AS26209:AS-ALL | ARIN | 3 | 2 | Yes | 2 |
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 10 are in fix.csv.
- ROA: none7
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.44.136.0/23 | No ROA covers it. Add a ROA for AS26209, maxLength 23. |
| Route object: none | 69.44.136.0/23 | No route object for it. Add a route object with origin AS26209 in the RIR database for the space. |
| ROA: none | 69.44.138.0/24 | No ROA covers it. Add a ROA for AS26209, maxLength 24. |
| Route object: none | 69.44.138.0/24 | No route object for it. Add a route object with origin AS26209 in the RIR database for the space. |
| ROA: none | 69.71.112.0/23 | No ROA covers it. Add a ROA for AS26209, maxLength 23. |
| ROA: none | 69.71.114.0/24 | No ROA covers it. Add a ROA for AS26209, maxLength 24. |
| ROA: none | 69.71.116.0/23 | No ROA covers it. Add a ROA for AS26209, maxLength 23. |
| ROA: none | 69.71.119.0/24 | No ROA covers it. Add a ROA for AS26209, maxLength 24. |
| ROA: none | 69.71.120.0/21 | No ROA covers it. Add a ROA for AS26209, maxLength 21. |
Route objects not announced
Route objects with origin AS26209 whose prefix no peer sees AS26209 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2605:840::/32 | ARIN | 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.