Network · data from 2026-11-12
AS60148 ITO-AS Iran Information Technology Company PJSC
Registry name: ITO-AS Iran Information Technology Company PJSC, IR · not in PeeringDB
18IPv4 routes
94.4% RPKI valid · 22.2% with a route object
4IPv6 routes
0.0% RPKI valid · 0.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
4No ROA
18 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS60148, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS60148, 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.
| 78.39.156.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 2001:4188:17::/48 | No ROA | None | 635 100% |
| 2001:4188:18::/48 | No ROA | None | 635 100% |
| 2001:4188:19::/48 | No ROA | None | 635 100% |
| 2001:4188:1a::/48 | No ROA | None | 635 100% |
| 2.179.168.0/24 | Valid | Other origin only | 670 100% |
| 2.180.254.0/24 | Valid | None | 670 100% |
| 2.180.255.0/24 | Valid | None | 670 100% |
| 2.181.222.0/24 | Valid | None | 670 100% |
| 2.181.223.0/24 | Valid | None | 670 100% |
| 2.182.255.0/24 | Valid | None | 670 100% |
| 2.185.254.0/24 | Valid | None | 670 100% |
| 2.185.255.0/24 | Valid | None | 670 100% |
| 2.187.253.0/24 | Valid | None | 670 100% |
| 2.187.254.0/24 | Valid | None | 670 100% |
| 2.187.255.0/24 | Valid | None | 670 100% |
| 78.39.152.0/24 | Valid | None | 670 100% |
| 2.178.254.0/24 | Valid | Other origin only | 2 0%low visibility |
| 78.38.237.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 78.38.239.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 78.39.157.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.146.59.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS60148 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 27 are in fix.csv.
- ROA: origin1
- ROA: none4
- Route object: none18
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 78.39.156.0/24 | ROAs covering it name AS12880, AS42337, AS48159, AS49666, AS58224, AS202468, not AS60148. If AS60148 should announce it, add a ROA for AS60148. |
| Route object: none | 78.39.156.0/24 | Route objects for it name AS42337. Add a route object with origin AS60148 in the RIR database for the space. |
| ROA: none | 2001:4188:17::/48 | No ROA covers it. Add a ROA for AS60148, maxLength 48. |
| Route object: none | 2001:4188:17::/48 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| ROA: none | 2001:4188:18::/48 | No ROA covers it. Add a ROA for AS60148, maxLength 48. |
| Route object: none | 2001:4188:18::/48 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| ROA: none | 2001:4188:19::/48 | No ROA covers it. Add a ROA for AS60148, maxLength 48. |
| Route object: none | 2001:4188:19::/48 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| ROA: none | 2001:4188:1a::/48 | No ROA covers it. Add a ROA for AS60148, maxLength 48. |
| Route object: none | 2001:4188:1a::/48 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.179.168.0/24 | Route objects for it name AS58224. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.180.254.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.180.255.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.181.222.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.181.223.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.182.255.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.185.254.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.185.255.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.187.253.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.187.254.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.187.255.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 78.39.152.0/24 | No route object for it. Add a route object with origin AS60148 in the RIR database for the space. |
| Route object: none | 2.178.254.0/24 | Route objects for it name AS58224. Add a route object with origin AS60148 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS60148 whose prefix no peer sees AS60148 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 78.38.238.0/24 | RIPE | Valid |
| 85.185.91.0/24 | RIPE | Invalid: origin |
| 213.176.5.0/24 | RIPE | Valid |
| 2001:4188:0:6::/64 | 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.