Network · data from 2026-11-12
AS56616 Sharif-AS Tarahan Shabake Sharif LTD
Registry name: Sharif-AS Tarahan Shabake Sharif LTD, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56616, 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.
| 2.188.168.0/21 | Valid | Other origin only | 670 100% |
| 31.7.88.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 31.7.89.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 31.7.90.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 31.7.91.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.116.20.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.116.21.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.116.22.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.116.23.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS56616 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 5 are in fix.csv.
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2.188.168.0/21 | Route objects for it name AS12880. Add a route object with origin AS56616 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56616 whose prefix no peer sees AS56616 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.7.88.0/23 | RIPE | Valid |
| 31.7.90.0/23 | RIPE | Valid |
| 185.116.20.0/22 | RIPE | Valid |
| 2a0a:d340::/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.