Network · data from 2026-11-12
AS59962 ShirazUniversity_ASN Shiraz University
Registry name: ShirazUniversity_ASN Shiraz University, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59962, 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.
| 151.232.113.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 151.232.115.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.173.152.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.173.154.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.173.156.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.173.157.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.173.158.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.64.176.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.64.178.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 46.209.38.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.209.39.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.56.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.57.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.58.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.59.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.60.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.61.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.62.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.63.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 151.232.112.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 151.232.114.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 178.173.153.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 178.173.155.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 178.173.159.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.209.32.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 46.209.34.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 46.209.36.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 87.107.176.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 87.107.177.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 87.107.178.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 87.107.179.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 87.107.180.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 87.107.181.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 87.107.182.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 87.107.183.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS59962 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 28 are in fix.csv.
- Route object: not announced28
Route objects not announced
Route objects with origin AS59962 whose prefix no peer sees AS59962 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.160.249.0/24 | RIPE | Invalid: origin |
| 5.160.250.0/23 | RIPE | Invalid: origin |
| 5.160.250.0/24 | RIPE | Invalid: origin |
| 5.160.251.0/24 | RIPE | Invalid: origin |
| 5.160.254.0/23 | RIPE | Invalid: origin |
| 5.160.254.0/24 | RIPE | Invalid: origin |
| 5.190.164.0/24 | RIPE | Invalid: origin |
| 46.209.32.0/21 | RIPE | Invalid: origin |
| 46.209.33.0/24 | RIPE | Valid |
| 46.209.35.0/24 | RIPE | Valid |
| 46.209.37.0/24 | RIPE | Valid |
| 46.209.168.0/21 | RIPE | Invalid: origin |
| 46.209.168.0/24 | RIPE | Valid |
| 46.209.169.0/24 | RIPE | Valid |
| 46.209.170.0/24 | RIPE | Valid |
| 46.209.171.0/24 | RIPE | Valid |
| 46.209.172.0/24 | RIPE | Valid |
| 46.209.173.0/24 | RIPE | Valid |
| 46.209.174.0/24 | RIPE | Valid |
| 46.209.175.0/24 | RIPE | Valid |
| 87.107.56.0/21 | RIPE | Valid |
| 87.107.176.0/21 | RIPE | Valid |
| 151.234.205.0/24 | RIPE | Invalid: origin |
| 151.234.206.0/24 | RIPE | Invalid: origin |
| 151.234.207.0/24 | RIPE | Invalid: origin |
| 178.173.152.0/21 | RIPE | No ROA |
| 194.33.104.0/24 | RIPE | Invalid: origin |
| 2a04:fb40::/29 | RIPE | 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.