Network · data from 2026-11-12
AS50558 Rayaneh Pardazan Baran Co.
Registry name: SYSTEC-AS Rayaneh Pardazan Baran Co. Ltd., IR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50558, 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.
| 37.32.112.0/24 | Valid | Nonecovered by 37.32.112.0/23 | 672 100% |
| 37.32.113.0/24 | Valid | Nonecovered by 37.32.112.0/23 | 672 100% |
| 37.32.114.0/24 | Valid | Nonecovered by 37.32.114.0/23 | 672 100% |
| 37.32.115.0/24 | Valid | Nonecovered by 37.32.114.0/23 | 672 100% |
| 37.32.118.0/24 | Valid | Nonecovered by 37.32.118.0/23 | 672 100% |
| 37.32.119.0/24 | Valid | Nonecovered by 37.32.118.0/23 | 672 100% |
| 37.32.112.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 37.32.116.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.32.120.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.32.122.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.32.123.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.32.112.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 185.49.96.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.49.97.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.49.98.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.49.99.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 37.32.121.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.32.124.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.32.125.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.32.126.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.32.127.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a01:9180::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS50558'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.
- Route object: none6
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 37.32.112.0/24 | No route object for it. A route object for 37.32.112.0/23 with origin AS50558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50558 in the RIR database for the space. |
| Route object: none | 37.32.113.0/24 | No route object for it. A route object for 37.32.112.0/23 with origin AS50558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50558 in the RIR database for the space. |
| Route object: none | 37.32.114.0/24 | No route object for it. A route object for 37.32.114.0/23 with origin AS50558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50558 in the RIR database for the space. |
| Route object: none | 37.32.115.0/24 | No route object for it. A route object for 37.32.114.0/23 with origin AS50558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50558 in the RIR database for the space. |
| Route object: none | 37.32.118.0/24 | No route object for it. A route object for 37.32.118.0/23 with origin AS50558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50558 in the RIR database for the space. |
| Route object: none | 37.32.119.0/24 | No route object for it. A route object for 37.32.118.0/23 with origin AS50558 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50558 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS50558 whose prefix no peer sees AS50558 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.32.112.0/23 | RIPE | Valid |
| 37.32.114.0/23 | RIPE | Valid |
| 37.32.118.0/23 | RIPE | Valid |
| 37.32.120.0/21 | RIPE | Valid |
| 37.32.120.0/23 | RIPE | Valid |
| 37.32.122.0/23 | RIPE | Valid |
| 37.32.124.0/23 | RIPE | Valid |
| 37.32.126.0/23 | RIPE | Valid |
| 185.49.96.0/22 | RIPE | Valid |
| 185.49.96.0/23 | RIPE | Valid |
| 185.49.98.0/23 | 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.