bgpreport

Network · data from 2026-11-12

AS39501 NGSAS-NedaGostarSaba Parvaresh Dadeha Co. Private Joint Stock

Registry name: NGSAS-NedaGostarSaba Parvaresh Dadeha Co. Private Joint Stock, IR · not in PeeringDB

73IPv4 routes 98.6% RPKI valid · 93.2% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
61Route objects not announced registered with origin AS39501, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS39501, 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.

188.158.0.0/15 No ROA None 669 99% 67
89.43.96.0/21 Valid None 672 100% 66
89.46.94.0/23 Valid None 672 100% 66
89.165.0.0/18 Valid Nonecovered by 89.165.0.0/17 672 100% 66
89.165.16.0/21 Valid Nonecovered by 89.165.16.0/20 672 100% 66
85.204.30.0/23 Valid RIR databaseRIPE 672 100% 66
85.204.76.0/23 Valid RIR databaseRIPE 672 100% 66
85.204.104.0/23 Valid RIR databaseRIPE 672 100% 66
86.104.232.0/21 Valid RIR databaseRIPE 672 100% 66
89.32.196.0/23 Valid RIR databaseRIPE 672 100% 66
89.33.18.0/23 Valid RIR databaseRIPE 672 100% 66
89.33.204.0/23 Valid RIR databaseRIPE 672 100% 66
89.33.234.0/23 Valid RIR databaseRIPE 672 100% 66
89.33.240.0/23 Valid RIR databaseRIPE 672 100% 66
89.34.20.0/23 Valid RIR databaseRIPE 672 100% 66
89.34.88.0/23 Valid RIR databaseRIPE 672 100% 66
89.34.94.0/23 Valid RIR databaseRIPE 672 100% 66
89.34.168.0/23 Valid RIR databaseRIPE 672 100% 66
89.34.176.0/23 Valid RIR databaseRIPE 672 100% 66
89.34.200.0/23 Valid RIR databaseRIPE 672 100% 66
89.35.58.0/23 Valid RIR databaseRIPE 672 100% 66
89.35.132.0/23 Valid RIR databaseRIPE 672 100% 66
89.35.156.0/23 Valid RIR databaseRIPE 672 100% 66
89.35.176.0/23 Valid RIR databaseRIPE 672 100% 66
89.35.194.0/23 Valid RIR databaseRIPE 672 100% 66
89.36.16.0/23 Valid RIR databaseRIPE 672 100% 66
89.36.194.0/23 Valid RIR databaseRIPE 672 100% 66
89.36.226.0/23 Valid RIR databaseRIPE 672 100% 66
89.37.30.0/23 Valid RIR databaseRIPE 672 100% 66
89.37.42.0/23 Valid RIR databaseRIPE 672 100% 66
89.37.102.0/23 Valid RIR databaseRIPE 672 100% 66
89.37.198.0/23 Valid RIR databaseRIPE 672 100% 66
89.37.218.0/23 Valid RIR databaseRIPE 672 100% 66
89.38.24.0/23 Valid RIR databaseRIPE 672 100% 66
89.38.102.0/23 Valid RIR databaseRIPE 672 100% 66
89.38.242.0/23 Valid RIR databaseRIPE 672 100% 66
89.39.186.0/23 Valid RIR databaseRIPE 672 100% 66
89.40.78.0/23 Valid RIR databaseRIPE 672 100% 66
89.40.90.0/23 Valid RIR databaseRIPE 672 100% 66
89.40.106.0/23 Valid RIR databaseRIPE 672 100% 66
89.40.128.0/23 Valid RIR databaseRIPE 672 100% 66
89.41.8.0/21 Valid RIR databaseRIPE 672 100% 66
89.41.16.0/21 Valid RIR databaseRIPE 672 100% 66
89.41.16.0/22 Valid RIR databaseRIPE 672 100% 66
89.41.20.0/22 Valid RIR databaseRIPE 672 100% 66
89.41.32.0/23 Valid RIR databaseRIPE 672 100% 66
89.41.240.0/21 Valid RIR databaseRIPE 672 100% 66
89.42.32.0/23 Valid RIR databaseRIPE 672 100% 66
89.42.68.0/23 Valid RIR databaseRIPE 672 100% 66
89.42.150.0/23 Valid RIR databaseRIPE 672 100% 66
89.42.228.0/23 Valid RIR databaseRIPE 672 100% 66
89.43.36.0/23 Valid RIR databaseRIPE 672 100% 66
89.43.70.0/23 Valid RIR databaseRIPE 672 100% 66
89.43.88.0/21 Valid RIR databaseRIPE 672 100% 66
89.43.182.0/23 Valid RIR databaseRIPE 672 100% 66
89.43.188.0/23 Valid RIR databaseRIPE 672 100% 66
89.43.204.0/23 Valid RIR databaseRIPE 672 100% 66
89.44.146.0/23 Valid RIR databaseRIPE 672 100% 66
89.44.190.0/23 Valid RIR databaseRIPE 672 100% 66
89.44.202.0/23 Valid RIR databaseRIPE 672 100% 66
89.45.80.0/23 Valid RIR databaseRIPE 672 100% 66
89.45.230.0/23 Valid RIR databaseRIPE 672 100% 66
89.46.44.0/23 Valid RIR databaseRIPE 672 100% 66
89.46.60.0/23 Valid RIR databaseRIPE 672 100% 66
89.165.0.0/17 Valid RIR databaseRIPE 672 100% 66
89.165.56.0/21 Valid RIR databaseRIPE 672 100% 66
94.176.32.0/21 Valid RIR databaseRIPE 672 100% 66
94.177.72.0/21 Valid RIR databaseRIPE 672 100% 66
188.158.0.0/16 Valid RIR databaseRIPE 672 100% 66
188.159.64.0/19 Valid RIR databaseRIPE 672 100% 66
188.159.96.0/19 Valid RIR databaseRIPE 672 100% 66
188.159.128.0/19 Valid RIR databaseRIPE 672 100% 66
188.159.192.0/19 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS39501 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 67 are in fix.csv.

  • ROA: none1
  • Route object: none5
  • Route object: not announced61
ChangePrefix or setDetailFull-table peers
ROA: none188.158.0.0/15No ROA covers it. Add a ROA for AS39501, maxLength 15.669 of 673
Route object: none188.158.0.0/15No route object for it. Add a route object with origin AS39501 in the RIR database for the space.669 of 673
Route object: none89.43.96.0/21No route object for it. Add a route object with origin AS39501 in the RIR database for the space.672 of 673
Route object: none89.46.94.0/23No route object for it. Add a route object with origin AS39501 in the RIR database for the space.672 of 673
Route object: none89.165.0.0/18No route object for it. A route object for 89.165.0.0/17 with origin AS39501 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39501 in the RIR database for the space.672 of 673
Route object: none89.165.16.0/21No route object for it. A route object for 89.165.16.0/20 with origin AS39501 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39501 in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS39501 whose prefix no peer sees AS39501 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.140.28.0/22RIPEValid
89.36.252.0/23RIPEValid
89.40.38.0/23RIPEValid
89.40.110.0/23RIPEValid
89.41.58.0/23RIPEValid
89.42.56.0/23RIPEValid
89.44.112.0/23RIPEInvalid: origin
89.44.118.0/23RIPEInvalid: origin
89.165.0.0/19RIPEInvalid: maxLength
89.165.0.0/20RIPEInvalid: maxLength
89.165.0.0/22RIPEInvalid: maxLength
89.165.1.0/24RIPEInvalid: maxLength
89.165.16.0/20RIPEInvalid: maxLength
89.165.32.0/21RIPEInvalid: maxLength
89.165.40.0/21RIPEInvalid: maxLength
89.165.40.0/22RIPEInvalid: maxLength
89.165.44.0/22RIPEInvalid: maxLength
89.165.48.0/20RIPEInvalid: maxLength
89.165.48.0/21RIPEInvalid: maxLength
89.165.64.0/21RIPEInvalid: maxLength
89.165.72.0/21RIPEInvalid: maxLength
89.165.80.0/22RIPEInvalid: maxLength
89.165.84.0/22RIPEInvalid: maxLength
89.165.88.0/22RIPEInvalid: maxLength
89.165.92.0/22RIPEInvalid: maxLength
89.165.96.0/22RIPEInvalid: maxLength
89.165.100.0/22RIPEInvalid: maxLength
89.165.102.0/23RIPEInvalid: maxLength
89.165.104.0/21RIPEInvalid: maxLength
89.165.112.0/21RIPEInvalid: maxLength
89.165.120.0/23RIPEInvalid: maxLength
188.158.0.0/19RIPEValid
188.158.0.0/20RIPEInvalid: maxLength
188.158.32.0/19RIPEValid
188.158.32.0/20RIPEValid
188.158.48.0/21RIPEInvalid: maxLength
188.158.64.0/19RIPEValid
188.158.96.0/19RIPEValid
188.158.96.0/20RIPEValid
188.158.96.0/21RIPEValid
188.158.104.0/21RIPEInvalid: maxLength
188.158.112.0/21RIPEInvalid: maxLength
188.158.128.0/18RIPEValid
188.158.192.0/19RIPEValid
188.158.224.0/19RIPEValid
188.158.224.0/21RIPEInvalid: maxLength
188.159.64.0/21RIPEInvalid: maxLength
188.159.96.0/20RIPEInvalid: maxLength
188.159.112.0/20RIPEInvalid: maxLength
188.159.120.0/21RIPEInvalid: maxLength
188.159.128.0/18RIPEValid
188.159.128.0/20RIPEInvalid: maxLength
188.159.184.0/23RIPEInvalid: maxLength
188.159.186.0/23RIPEInvalid: maxLength
188.159.188.0/23RIPEInvalid: maxLength
188.159.190.0/23RIPEInvalid: maxLength
188.159.200.0/21RIPEInvalid: maxLength
188.159.208.0/20RIPEInvalid: maxLength
188.159.220.0/23RIPEInvalid: maxLength
188.214.120.0/23RIPENo ROA
2a00:1fe0::/32RIPENo ROA

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.