Network · data from 2026-11-12
AS16973 TAG Systems
Registry name: AS16973 - T-Four Services S.A, CR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16973, 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.247.112.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 168.205.64.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 168.205.65.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 168.205.66.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 190.4.88.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 190.4.89.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 190.4.90.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 190.4.91.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 190.4.92.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 190.4.93.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 190.4.94.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 190.4.95.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 168.205.67.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 190.4.88.0/21 | Valid | RIR databaseLACNIC, RADB | 666 99% |
| 168.205.64.0/22 | Valid | RIR databaseLACNIC, RADB | 665 99% |
| 2803:3100::/32 | Valid | RIR databaseLACNIC, RADB | 635 100% |
AS-SET
AS16973'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 17 are in fix.csv.
- ROA: none1
- Route object: RIR13
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.247.112.0/22 | No ROA covers it. Add a ROA for AS16973, maxLength 22. |
| Route object: RIR | 38.247.112.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.205.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.205.65.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.205.66.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.4.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.4.89.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.4.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.4.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.4.92.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.4.93.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.4.94.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.4.95.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.205.67.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16973 whose prefix no peer sees AS16973 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 181.119.252.0/24 | RADB | Valid |
| 186.176.5.0/24 | LACNIC, RADB | Valid |
| 186.177.22.0/23 | LACNIC, RADB | 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.