Network · data from 2026-11-12
AS201150 Didehabnnet Didehban Net Company PJS
Registry name: Didehabnnet Didehban Net Company PJS, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201150, 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.
| 5.202.18.0/24 | Valid | Nonecovered by 5.202.18.0/23 | 671 100% |
| 5.202.19.0/24 | Valid | Nonecovered by 5.202.18.0/23 | 671 100% |
| 5.202.20.0/24 | Valid | Nonecovered by 5.202.20.0/23 | 671 100% |
| 5.202.21.0/24 | Valid | Nonecovered by 5.202.20.0/23 | 671 100% |
| 5.202.30.0/24 | Valid | Nonecovered by 5.202.28.0/22 | 671 100% |
| 5.202.31.0/24 | Valid | Nonecovered by 5.202.28.0/22 | 671 100% |
| 5.202.62.0/23 | Valid | Other origin onlycovered by 5.202.60.0/22 | 671 100% |
| 46.249.120.0/22 | Valid | Nonecovered by 46.249.120.0/21 | 671 100% |
| 46.249.124.0/22 | Valid | Nonecovered by 46.249.120.0/21 | 671 100% |
| 45.84.158.0/23 | Valid | Nonecovered by 45.84.156.0/22 | 670 100% |
| 45.84.156.0/24 | Valid | Nonecovered by 45.84.156.0/22 | 669 99% |
| 45.84.157.0/24 | Valid | Nonecovered by 45.84.156.0/22 | 669 99% |
| 5.202.18.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 5.202.20.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 5.202.24.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 5.202.28.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 5.202.28.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.202.60.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 5.202.96.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 46.249.120.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 45.132.32.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.134.99.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS201150 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 29 are in fix.csv.
- Route object: none12
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.202.18.0/24 | No route object for it. A route object for 5.202.18.0/23 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 5.202.19.0/24 | No route object for it. A route object for 5.202.18.0/23 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 5.202.20.0/24 | No route object for it. A route object for 5.202.20.0/23 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 5.202.21.0/24 | No route object for it. A route object for 5.202.20.0/23 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 5.202.30.0/24 | No route object for it. A route object for 5.202.28.0/22 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 5.202.31.0/24 | No route object for it. A route object for 5.202.28.0/22 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 5.202.62.0/23 | Route objects for it name AS49100. A route object for 5.202.60.0/22 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 46.249.120.0/22 | No route object for it. A route object for 46.249.120.0/21 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 46.249.124.0/22 | No route object for it. A route object for 46.249.120.0/21 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 45.84.158.0/23 | No route object for it. A route object for 45.84.156.0/22 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 45.84.156.0/24 | No route object for it. A route object for 45.84.156.0/22 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
| Route object: none | 45.84.157.0/24 | No route object for it. A route object for 45.84.156.0/22 with origin AS201150 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201150 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201150 whose prefix no peer sees AS201150 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.202.0.0/19 | RIPE | Valid |
| 5.202.16.0/20 | RIPE | Valid |
| 5.202.16.0/22 | RIPE | Invalid: maxLength |
| 5.202.20.0/22 | RIPE | Invalid: maxLength |
| 5.202.60.0/23 | RIPE | Invalid: maxLength |
| 45.84.156.0/22 | RIPE | Valid |
| 46.249.120.0/23 | RIPE | Valid |
| 46.249.122.0/23 | RIPE | Valid |
| 46.249.124.0/23 | RIPE | Valid |
| 46.249.126.0/23 | RIPE | Valid |
| 79.132.210.0/24 | RIPE | Invalid: origin |
| 185.103.128.0/22 | RIPE | Valid |
| 185.169.20.0/22 | RIPE | Valid |
| 185.169.36.0/22 | RIPE | Valid |
| 185.180.52.0/22 | RIPE | Valid |
| 194.50.169.0/24 | RIPE | No ROA |
| 2a00:4c60::/32 | 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.