bgpreport

Network · data from 2026-11-12

AS17826 SATNET India

Registry name: SATATANET-ID - Jl. Raya Pasar Minggu no 99D, ID · PeeringDB

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

Announced routes

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

2405:5100::/32 Valid None 636 100% 70
202.149.64.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
202.149.65.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.149.75.0/24 Valid Other IRR onlyNTTCOM 673 100% 68
202.149.78.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
202.149.66.0/23 Valid Other IRR onlyNTTCOM 672 100% 69
202.149.68.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
202.149.72.0/21 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.149.80.0/21 Valid Other IRR onlyNTTCOM 672 100% 68
202.149.88.0/23 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
202.149.90.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.149.91.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.149.92.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
202.149.64.0/21 Valid Other IRR onlyNTTCOM 671 100% 67
202.149.67.0/24 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 28
202.149.68.0/23 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 29
202.149.68.0/24 Valid Other IRR onlyNTTCOM 35 5%low visibility 28
202.149.69.0/24 Valid Other IRR onlyNTTCOM 35 5%low visibility 28
202.149.70.0/23 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 29
202.149.70.0/24 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 28
202.149.71.0/24 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 28
202.149.72.0/23 Valid Other IRR onlyNTTCOM 35 5%low visibility 29
202.149.74.0/23 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 29
202.149.76.0/23 Valid Other IRR onlyNTTCOM 35 5%low visibility 29
202.149.78.0/23 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 29
202.149.80.0/23 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 29
202.149.82.0/23 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 29
202.149.84.0/23 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 29
202.149.86.0/23 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 29
202.149.92.0/23 Valid Other IRR onlyNTTCOM 35 5%low visibility 29
202.149.94.0/23 Valid Other IRR onlyNTTCOM, RADB 35 5%low visibility 29

AS-SET

AS17826'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 141 are in fix.csv.

  • Route object: none1
  • Route object: RIR30
  • Route object: not announced110
ChangePrefix or setDetailFull-table peers
Route object: none2405:5100::/32No route object for it. Add a route object with origin AS17826 in the RIR database for the space.636 of 636
Route object: RIR202.149.64.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.149.65.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.149.75.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.149.78.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.149.66.0/23Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR202.149.68.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.149.72.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.149.80.0/21Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR202.149.88.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.149.90.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.149.91.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.149.92.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.149.64.0/21Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR202.149.67.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.68.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.68.0/24Route object only in NTTCOM. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.69.0/24Route object only in NTTCOM. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.70.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.70.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.71.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.72.0/23Route object only in NTTCOM. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.74.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.76.0/23Route object only in NTTCOM. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.78.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.80.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.82.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.84.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.86.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.92.0/23Route object only in NTTCOM. Add it in the RIR database for the space.35 of 673
Route object: RIR202.149.94.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.35 of 673

Route objects not announced

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

27.111.42.0/24APNICInvalid: origin
27.111.43.0/24APNICInvalid: origin
117.103.48.0/20NTTCOMNo ROA
117.103.48.0/24NTTCOMNo ROA
117.103.49.0/24NTTCOMNo ROA
117.103.51.0/24NTTCOMNo ROA
117.103.52.0/24NTTCOMNo ROA
117.103.53.0/24NTTCOMNo ROA
117.103.54.0/24NTTCOMNo ROA
117.103.55.0/24NTTCOMNo ROA
117.103.56.0/24NTTCOMNo ROA
117.103.57.0/24NTTCOMNo ROA
117.103.58.0/24NTTCOMNo ROA
117.103.59.0/24NTTCOMNo ROA
117.103.60.0/24NTTCOMNo ROA
117.103.61.0/24NTTCOMNo ROA
117.103.62.0/24NTTCOMNo ROA
117.103.63.0/24NTTCOMNo ROA
121.50.120.0/24NTTCOMNo ROA
121.50.121.0/24NTTCOMNo ROA
121.50.122.0/24NTTCOMNo ROA
121.50.123.0/24NTTCOMNo ROA
121.50.124.0/24NTTCOMNo ROA
121.50.125.0/24NTTCOMNo ROA
121.50.126.0/24NTTCOMNo ROA
121.50.127.0/24NTTCOMNo ROA
121.50.128.0/24NTTCOMNo ROA
121.50.129.0/24NTTCOMNo ROA
121.50.130.0/24NTTCOMNo ROA
121.50.131.0/24NTTCOMNo ROA
121.50.132.0/24NTTCOMNo ROA
121.50.133.0/24NTTCOMNo ROA
121.50.134.0/24NTTCOMNo ROA
121.50.135.0/24NTTCOMNo ROA
202.62.8.0/21NTTCOMNo ROA
202.62.8.0/22NTTCOMNo ROA
202.62.8.0/23NTTCOMNo ROA
202.62.8.0/24NTTCOMNo ROA
202.62.9.0/24NTTCOMNo ROA
202.62.10.0/23NTTCOMNo ROA
202.62.10.0/24NTTCOMNo ROA
202.62.11.0/24NTTCOMNo ROA
202.72.192.0/20NTTCOMNo ROA
202.72.197.0/24NTTCOMNo ROA
202.72.200.0/24NTTCOMNo ROA
202.91.24.0/21NTTCOM, RADBNo ROA
202.91.24.0/22NTTCOM, RADBNo ROA
202.91.24.0/23NTTCOM, RADBNo ROA
202.91.26.0/23NTTCOM, RADBNo ROA
202.91.28.0/22NTTCOM, RADBNo ROA
202.91.28.0/23NTTCOM, RADBNo ROA
202.91.30.0/23NTTCOM, RADBNo ROA
202.122.174.0/24NTTCOM, RADBNo ROA
202.149.64.0/19APNIC, NTTCOM, RADBValid
202.149.64.0/20NTTCOM, RADBValid
202.149.64.0/22NTTCOMValid
202.149.64.0/23NTTCOMValid
202.149.66.0/24NTTCOM, RADBValid
202.149.72.0/22NTTCOMValid
202.149.72.0/24NTTCOM, RADBValid
202.149.73.0/24NTTCOM, RADBValid
202.149.74.0/24NTTCOM, RADBValid
202.149.76.0/22NTTCOMValid
202.149.76.0/24NTTCOMValid
202.149.77.0/24NTTCOMValid
202.149.79.0/24NTTCOM, RADBValid
202.149.80.0/20NTTCOM, RADBValid
202.149.80.0/22NTTCOM, RADBValid
202.149.80.0/24NTTCOM, RADBValid
202.149.81.0/24NTTCOM, RADBValid
202.149.82.0/24NTTCOM, RADBValid
202.149.83.0/24NTTCOM, RADBValid
202.149.84.0/22NTTCOM, RADBValid
202.149.84.0/24NTTCOM, RADBValid
202.149.85.0/24NTTCOM, RADBValid
202.149.86.0/24NTTCOM, RADBValid
202.149.87.0/24NTTCOM, RADBValid
202.149.88.0/21NTTCOM, RADBValid
202.149.88.0/22NTTCOM, RADBValid
202.149.88.0/24NTTCOM, RADBValid
202.149.89.0/24NTTCOMValid
202.149.90.0/23NTTCOMValid
202.149.92.0/24NTTCOMValid
202.149.93.0/24NTTCOMValid
202.149.94.0/24NTTCOM, RADBValid
202.149.95.0/24NTTCOM, RADBValid
202.154.176.0/20NTTCOMNo ROA
203.190.36.0/24NTTCOMNo ROA
203.190.184.0/22NTTCOMNo ROA
203.190.184.0/24NTTCOMNo ROA
203.190.185.0/24NTTCOMNo ROA
203.190.186.0/24NTTCOMNo ROA
203.190.187.0/24NTTCOMNo ROA
210.23.64.0/20NTTCOMNo ROA
210.23.64.0/24NTTCOMNo ROA
210.23.65.0/24NTTCOMNo ROA
210.23.66.0/24NTTCOMNo ROA
210.23.67.0/24NTTCOMNo ROA
210.23.68.0/24NTTCOMNo ROA
210.23.69.0/24NTTCOMNo ROA
210.23.70.0/24NTTCOMNo ROA
210.23.71.0/24NTTCOMNo ROA
210.23.72.0/24NTTCOMNo ROA
210.23.73.0/24NTTCOMNo ROA
210.23.74.0/24NTTCOMNo ROA
210.23.75.0/24NTTCOMNo ROA
210.23.76.0/24NTTCOMNo ROA
210.23.77.0/24NTTCOMNo ROA
210.23.78.0/24NTTCOMNo ROA
210.23.79.0/24NTTCOMNo 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.