bgpreport

Network · data from 2026-11-12

AS201150 Didehabnnet Didehban Net Company PJS

Registry name: Didehabnnet Didehban Net Company PJS, IR · not in PeeringDB

22IPv4 routes 100.0% RPKI valid · 45.5% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 12 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS201150, seen from no peer

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% 66
5.202.19.0/24 Valid Nonecovered by 5.202.18.0/23 671 100% 66
5.202.20.0/24 Valid Nonecovered by 5.202.20.0/23 671 100% 66
5.202.21.0/24 Valid Nonecovered by 5.202.20.0/23 671 100% 66
5.202.30.0/24 Valid Nonecovered by 5.202.28.0/22 671 100% 66
5.202.31.0/24 Valid Nonecovered by 5.202.28.0/22 671 100% 66
5.202.62.0/23 Valid Other origin onlycovered by 5.202.60.0/22 671 100% 66
46.249.120.0/22 Valid Nonecovered by 46.249.120.0/21 671 100% 66
46.249.124.0/22 Valid Nonecovered by 46.249.120.0/21 671 100% 66
45.84.158.0/23 Valid Nonecovered by 45.84.156.0/22 670 100% 66
45.84.156.0/24 Valid Nonecovered by 45.84.156.0/22 669 99% 66
45.84.157.0/24 Valid Nonecovered by 45.84.156.0/22 669 99% 66
5.202.18.0/23 Valid RIR databaseRIPE 671 100% 66
5.202.20.0/23 Valid RIR databaseRIPE 671 100% 66
5.202.24.0/22 Valid RIR databaseRIPE 671 100% 66
5.202.28.0/22 Valid RIR databaseRIPE 671 100% 66
5.202.28.0/24 Valid RIR databaseRIPE 671 100% 67
5.202.60.0/22 Valid RIR databaseRIPE 671 100% 66
5.202.96.0/22 Valid RIR databaseRIPE 671 100% 67
46.249.120.0/21 Valid RIR databaseRIPE 671 100% 66
45.132.32.0/24 Valid RIR databaseRIPE 670 100% 66
45.134.99.0/24 Valid RIR databaseRIPE 670 100% 67

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
ChangePrefix or setDetailFull-table peers
Route object: none5.202.18.0/24No 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.671 of 673
Route object: none5.202.19.0/24No 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.671 of 673
Route object: none5.202.20.0/24No 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.671 of 673
Route object: none5.202.21.0/24No 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.671 of 673
Route object: none5.202.30.0/24No 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.671 of 673
Route object: none5.202.31.0/24No 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.671 of 673
Route object: none5.202.62.0/23Route 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.671 of 673
Route object: none46.249.120.0/22No 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.671 of 673
Route object: none46.249.124.0/22No 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.671 of 673
Route object: none45.84.158.0/23No 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.670 of 673
Route object: none45.84.156.0/24No 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.669 of 673
Route object: none45.84.157.0/24No 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.669 of 673

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/19RIPEValid
5.202.16.0/20RIPEValid
5.202.16.0/22RIPEInvalid: maxLength
5.202.20.0/22RIPEInvalid: maxLength
5.202.60.0/23RIPEInvalid: maxLength
45.84.156.0/22RIPEValid
46.249.120.0/23RIPEValid
46.249.122.0/23RIPEValid
46.249.124.0/23RIPEValid
46.249.126.0/23RIPEValid
79.132.210.0/24RIPEInvalid: origin
185.103.128.0/22RIPEValid
185.169.20.0/22RIPEValid
185.169.36.0/22RIPEValid
185.180.52.0/22RIPEValid
194.50.169.0/24RIPENo ROA
2a00:4c60::/32RIPEValid

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.