Network · data from 2026-11-12
AS398766 TriCoLink, Inc.
Registry name: TRICOLINK - TriCoLink, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS398766, 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.
| 162.118.104.0/24 | Valid | Nonecovered by 162.118.96.0/19 | 672 100% |
| 162.118.96.0/24 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.97.0/24 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.98.0/23 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.100.0/22 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.105.0/24 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.107.0/24 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.108.0/23 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.110.0/23 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.112.0/24 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.116.0/22 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.120.0/22 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 162.118.126.0/24 | Valid | Nonecovered by 162.118.96.0/19 | 671 100% |
| 23.252.16.0/20 | Valid | RIR databaseARIN, RADB | 673 100% |
| 23.252.20.0/22 | Valid | RIR databaseARIN | 673 100% |
| 23.252.24.0/22 | Valid | RIR databaseARIN | 673 100% |
| 23.252.28.0/23 | Valid | RIR databaseARIN | 673 100% |
| 23.252.30.0/23 | Valid | RIR databaseARIN | 673 100% |
| 124.198.160.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 162.118.96.0/19 | Valid | RIR databaseARIN, RADB | 672 100% |
| 124.198.160.0/22 | Valid | RIR databaseARIN | 671 100% |
| 124.198.164.0/22 | Valid | RIR databaseARIN | 671 100% |
| 124.198.191.0/24 | Valid | RIR databaseARIN | 671 100% |
| 124.198.172.0/22 | Valid | RIR databaseARIN | 670 100% |
| 2605:eb40::/32 | Valid | RIR databaseARIN, RADB | 634 100% |
AS-SET
AS398766's PeeringDB record names no AS-SET.
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 19 are in fix.csv.
- Route object: none13
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 162.118.104.0/24 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.96.0/24 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.97.0/24 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.98.0/23 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.100.0/22 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.105.0/24 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.107.0/24 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.108.0/23 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.110.0/23 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.112.0/24 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.116.0/22 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.120.0/22 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
| Route object: none | 162.118.126.0/24 | No route object for it. A route object for 162.118.96.0/19 with origin AS398766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398766 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS398766 whose prefix no peer sees AS398766 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.252.16.0/22 | ARIN | Valid |
| 72.1.48.0/20 | RADB | No ROA |
| 124.198.168.0/22 | ARIN | Valid |
| 124.198.176.0/22 | ARIN | Valid |
| 124.198.180.0/22 | ARIN | Valid |
| 124.198.190.0/24 | ARIN | Valid |
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.