Network · data from 2026-11-12
AS29068 UT-AS University of Tehran
Registry name: UT-AS University of Tehran, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29068, 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.
| 80.66.176.0/23 | No ROA | Nonecovered by 80.66.176.0/21 | 672 100% |
| 80.66.178.0/23 | No ROA | Nonecovered by 80.66.176.0/21 | 672 100% |
| 188.118.64.0/22 | No ROA | Nonecovered by 188.118.64.0/21 | 672 100% |
| 188.118.68.0/22 | No ROA | Nonecovered by 188.118.64.0/21 | 672 100% |
| 188.118.80.0/23 | No ROA | Nonecovered by 188.118.64.0/19 | 672 100% |
| 188.118.85.0/24 | No ROA | Nonecovered by 188.118.64.0/19 | 671 100% |
| 80.66.176.0/22 | No ROA | Nonecovered by 80.66.176.0/21 | 670 100% |
| 188.118.72.0/21 | No ROA | Nonecovered by 188.118.64.0/19 | 670 100% |
| 188.118.90.0/24 | No ROA | Nonecovered by 188.118.64.0/19 | 670 100% |
| 188.118.64.0/18 | No ROA | RIR databaseRIPE | 672 100% |
| 80.66.176.0/20 | No ROA | RIR databaseRIPE | 670 100% |
| 185.197.112.0/22 | No ROA | RIR databaseRIPE | 670 100% |
AS-SET
AS29068 isn't in PeeringDB, where networks name their 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 38 are in fix.csv.
- ROA: none12
- Route object: none9
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 80.66.176.0/23 | No ROA covers it. Add a ROA for AS29068, maxLength 23. |
| Route object: none | 80.66.176.0/23 | No route object for it. A route object for 80.66.176.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space. |
| ROA: none | 80.66.178.0/23 | No ROA covers it. Add a ROA for AS29068, maxLength 23. |
| Route object: none | 80.66.178.0/23 | No route object for it. A route object for 80.66.176.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space. |
| ROA: none | 188.118.64.0/22 | No ROA covers it. Add a ROA for AS29068, maxLength 22. |
| Route object: none | 188.118.64.0/22 | No route object for it. A route object for 188.118.64.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space. |
| ROA: none | 188.118.68.0/22 | No ROA covers it. Add a ROA for AS29068, maxLength 22. |
| Route object: none | 188.118.68.0/22 | No route object for it. A route object for 188.118.64.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space. |
| ROA: none | 188.118.80.0/23 | No ROA covers it. Add a ROA for AS29068, maxLength 23. |
| Route object: none | 188.118.80.0/23 | No route object for it. A route object for 188.118.64.0/19 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space. |
| ROA: none | 188.118.85.0/24 | No ROA covers it. Add a ROA for AS29068, maxLength 24. |
| Route object: none | 188.118.85.0/24 | No route object for it. A route object for 188.118.64.0/19 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space. |
| ROA: none | 80.66.176.0/22 | No ROA covers it. Add a ROA for AS29068, maxLength 22. |
| Route object: none | 80.66.176.0/22 | No route object for it. A route object for 80.66.176.0/21 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space. |
| ROA: none | 188.118.72.0/21 | No ROA covers it. Add a ROA for AS29068, maxLength 21. |
| Route object: none | 188.118.72.0/21 | No route object for it. A route object for 188.118.64.0/19 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space. |
| ROA: none | 188.118.90.0/24 | No ROA covers it. Add a ROA for AS29068, maxLength 24. |
| Route object: none | 188.118.90.0/24 | No route object for it. A route object for 188.118.64.0/19 with origin AS29068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29068 in the RIR database for the space. |
| ROA: none | 188.118.64.0/18 | No ROA covers it. Add a ROA for AS29068, maxLength 18. |
| ROA: none | 80.66.176.0/20 | No ROA covers it. Add a ROA for AS29068, maxLength 20. |
| ROA: none | 185.197.112.0/22 | No ROA covers it. Add a ROA for AS29068, maxLength 22. |
Route objects not announced
Route objects with origin AS29068 whose prefix no peer sees AS29068 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.66.176.0/21 | RADB, RIPE | No ROA |
| 80.66.184.0/21 | RIPE | No ROA |
| 80.66.191.0/24 | RIPE | No ROA |
| 94.184.160.0/21 | RIPE | Invalid: origin |
| 94.184.168.0/21 | RIPE | Invalid: origin |
| 188.118.64.0/19 | RIPE | No ROA |
| 188.118.64.0/21 | RADB, RIPE | No ROA |
| 188.118.74.0/23 | RIPE | No ROA |
| 188.118.96.0/19 | RIPE | No ROA |
| 188.118.96.0/24 | RIPE | No ROA |
| 188.118.110.0/23 | RIPE | No ROA |
| 188.118.112.0/21 | RIPE | No ROA |
| 194.225.8.0/21 | RIPE | Invalid: origin |
| 194.225.8.0/22 | RIPE | Invalid: origin |
| 194.225.12.0/22 | RIPE | Invalid: origin |
| 194.225.14.0/24 | RIPE | Invalid: origin |
| 2001:14e8:9::/48 | RIPE | Invalid: origin |
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.