bgpreport

Network · data from 2026-11-12

AS7616 JASTEL-NETWORK-IDC - JasTel Network

Registry name: JASTEL-NETWORK-IDC - JasTel Network, TH · not in PeeringDB

40IPv4 routes 60.0% RPKI valid · 80.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
8RPKI invalid 0 origin · 8 maxLength
8No ROA 8 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
118Route objects not announced registered with origin AS7616, seen from no peer

Announced routes

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

203.130.147.0/24 Invalid: maxLength Nonecovered by 203.130.144.0/20 117 17% 48
203.147.16.0/24 Invalid: maxLength Nonecovered by 203.147.16.0/21 115 17% 48
203.147.58.0/24 Invalid: maxLength Nonecovered by 203.147.48.0/20 115 17% 48
203.130.141.0/24 Invalid: maxLength Nonecovered by 203.130.128.0/20 114 17% 48
203.130.148.0/24 Invalid: maxLength Nonecovered by 203.130.144.0/20 114 17% 48
203.130.150.0/24 Invalid: maxLength Nonecovered by 203.130.144.0/20 114 17% 48
203.130.152.0/21 Invalid: maxLength Nonecovered by 203.130.144.0/20 114 17% 48
203.130.149.0/24 Invalid: maxLength Nonecovered by 203.130.144.0/20 113 17% 48
203.147.0.0/18 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.147.0.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.156.0.0/17 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.156.0.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.156.16.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.156.32.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.156.96.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.156.112.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.130.128.0/19 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.130.128.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.130.144.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.130.146.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.147.10.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.147.16.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.147.32.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.147.48.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.147.52.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.147.53.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.147.54.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.18.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.48.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.64.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.80.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.128.0/18 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.128.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.144.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.160.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.176.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.156.189.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.147.31.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
203.147.42.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
203.156.95.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
2403:bf00::/32 Valid RIR databaseAPNIC, RADB 635 100% 67

AS-SET

AS7616 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 150 are in fix.csv.

  • ROA: maxLength8
  • ROA: none8
  • Route object: none8
  • Route object: RIR8
  • Route object: not announced118
ChangePrefix or setDetailFull-table peers
ROA: maxLength203.130.147.0/24ROA 203.130.128.0/19 AS7616 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 203.130.147.0/24.117 of 673
Route object: none203.130.147.0/24No route object for it. A route object for 203.130.144.0/20 with origin AS7616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7616 in the RIR database for the space.117 of 673
ROA: maxLength203.147.16.0/24ROA 203.147.16.0/20 AS7616 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 203.147.16.0/24.115 of 673
Route object: none203.147.16.0/24No route object for it. A route object for 203.147.16.0/21 with origin AS7616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7616 in the RIR database for the space.115 of 673
ROA: maxLength203.147.58.0/24ROA 203.147.48.0/20 AS7616 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 203.147.58.0/24.115 of 673
Route object: none203.147.58.0/24No route object for it. A route object for 203.147.48.0/20 with origin AS7616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7616 in the RIR database for the space.115 of 673
ROA: maxLength203.130.141.0/24ROA 203.130.128.0/19 AS7616 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 203.130.141.0/24.114 of 673
Route object: none203.130.141.0/24No route object for it. A route object for 203.130.128.0/20 with origin AS7616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7616 in the RIR database for the space.114 of 673
ROA: maxLength203.130.148.0/24ROA 203.130.128.0/19 AS7616 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 203.130.148.0/24.114 of 673
Route object: none203.130.148.0/24No route object for it. A route object for 203.130.144.0/20 with origin AS7616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7616 in the RIR database for the space.114 of 673
ROA: maxLength203.130.150.0/24ROA 203.130.128.0/19 AS7616 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 203.130.150.0/24.114 of 673
Route object: none203.130.150.0/24No route object for it. A route object for 203.130.144.0/20 with origin AS7616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7616 in the RIR database for the space.114 of 673
ROA: maxLength203.130.152.0/21ROA 203.130.128.0/19 AS7616 has maxLength 20; the route is a /21. Raise the maxLength, or add a ROA for 203.130.152.0/21.114 of 673
Route object: none203.130.152.0/21No route object for it. A route object for 203.130.144.0/20 with origin AS7616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7616 in the RIR database for the space.114 of 673
ROA: maxLength203.130.149.0/24ROA 203.130.128.0/19 AS7616 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 203.130.149.0/24.113 of 673
Route object: none203.130.149.0/24No route object for it. A route object for 203.130.144.0/20 with origin AS7616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7616 in the RIR database for the space.113 of 673
ROA: none203.147.0.0/18No ROA covers it. Add a ROA for AS7616, maxLength 18.673 of 673
Route object: RIR203.147.0.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.147.0.0/20No ROA covers it. Add a ROA for AS7616, maxLength 20.673 of 673
Route object: RIR203.147.0.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.156.0.0/17No ROA covers it. Add a ROA for AS7616, maxLength 17.673 of 673
Route object: RIR203.156.0.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.156.0.0/20No ROA covers it. Add a ROA for AS7616, maxLength 20.673 of 673
Route object: RIR203.156.0.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.156.16.0/20No ROA covers it. Add a ROA for AS7616, maxLength 20.673 of 673
Route object: RIR203.156.16.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.156.32.0/20No ROA covers it. Add a ROA for AS7616, maxLength 20.673 of 673
Route object: RIR203.156.32.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.156.96.0/20No ROA covers it. Add a ROA for AS7616, maxLength 20.673 of 673
Route object: RIR203.156.96.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.156.112.0/20No ROA covers it. Add a ROA for AS7616, maxLength 20.673 of 673
Route object: RIR203.156.112.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

202.90.112.0/24RADBNo ROA
202.90.113.0/24RADBNo ROA
202.90.114.0/24RADBNo ROA
202.90.115.0/24RADBNo ROA
203.147.0.0/19NTTCOM, RADBNo ROA
203.147.0.0/21NTTCOM, RADBNo ROA
203.147.0.0/22NTTCOM, RADBNo ROA
203.147.0.0/23NTTCOM, RADBNo ROA
203.147.0.0/24NTTCOM, RADBNo ROA
203.147.1.0/24NTTCOM, RADBNo ROA
203.147.2.0/23NTTCOM, RADBNo ROA
203.147.2.0/24NTTCOM, RADBNo ROA
203.147.3.0/24NTTCOM, RADBNo ROA
203.147.4.0/22NTTCOM, RADBNo ROA
203.147.4.0/23NTTCOM, RADBNo ROA
203.147.4.0/24NTTCOM, RADBNo ROA
203.147.5.0/24NTTCOM, RADBNo ROA
203.147.6.0/23NTTCOM, RADBNo ROA
203.147.7.0/24NTTCOM, RADBNo ROA
203.147.8.0/21NTTCOM, RADBNo ROA
203.147.8.0/22NTTCOM, RADBNo ROA
203.147.8.0/23NTTCOM, RADBNo ROA
203.147.8.0/24NTTCOM, RADBNo ROA
203.147.9.0/24NTTCOM, RADBNo ROA
203.147.10.0/23NTTCOM, RADBNo ROA
203.147.11.0/24NTTCOM, RADBNo ROA
203.147.12.0/22NTTCOM, RADBNo ROA
203.147.12.0/23NTTCOM, RADBNo ROA
203.147.12.0/24NTTCOM, RADBNo ROA
203.147.14.0/23NTTCOM, RADBNo ROA
203.147.14.0/24NTTCOM, RADBNo ROA
203.147.15.0/24NTTCOM, RADBNo ROA
203.147.16.0/21APNIC, NTTCOM, RADBValid
203.147.24.0/21APNIC, NTTCOM, RADBValid
203.147.32.0/19NTTCOM, RADBNo ROA
203.147.32.0/21APNIC, NTTCOM, RADBValid
203.147.40.0/21APNIC, NTTCOM, RADBValid
203.156.0.0/18NTTCOM, RADBNo ROA
203.156.0.0/19NTTCOM, RADBNo ROA
203.156.0.0/21NTTCOM, RADBNo ROA
203.156.4.0/22NTTCOM, RADBNo ROA
203.156.4.0/23NTTCOM, RADBNo ROA
203.156.5.0/24NTTCOM, RADBNo ROA
203.156.6.0/23NTTCOM, RADBNo ROA
203.156.6.0/24NTTCOM, RADBNo ROA
203.156.16.0/21NTTCOM, RADBNo ROA
203.156.16.0/22NTTCOM, RADBNo ROA
203.156.16.0/23NTTCOM, RADBNo ROA
203.156.17.0/24NTTCOM, RADBNo ROA
203.156.18.0/23NTTCOM, RADBNo ROA
203.156.19.0/24NTTCOM, RADBNo ROA
203.156.20.0/22NTTCOM, RADBNo ROA
203.156.20.0/23NTTCOM, RADBNo ROA
203.156.20.0/24NTTCOM, RADBNo ROA
203.156.21.0/24NTTCOM, RADBNo ROA
203.156.22.0/23NTTCOM, RADBNo ROA
203.156.22.0/24NTTCOM, RADBNo ROA
203.156.23.0/24NTTCOM, RADBNo ROA
203.156.24.0/21NTTCOM, RADBNo ROA
203.156.24.0/22NTTCOM, RADBNo ROA
203.156.24.0/23NTTCOM, RADBNo ROA
203.156.26.0/23NTTCOM, RADBNo ROA
203.156.28.0/22NTTCOM, RADBNo ROA
203.156.28.0/23NTTCOM, RADBNo ROA
203.156.29.0/24NTTCOM, RADBNo ROA
203.156.30.0/23NTTCOM, RADBNo ROA
203.156.32.0/19NTTCOM, RADBNo ROA
203.156.32.0/21NTTCOM, RADBNo ROA
203.156.32.0/22NTTCOM, RADBNo ROA
203.156.32.0/23NTTCOM, RADBNo ROA
203.156.34.0/23NTTCOM, RADBNo ROA
203.156.34.0/24NTTCOM, RADBNo ROA
203.156.35.0/24NTTCOM, RADBNo ROA
203.156.36.0/22NTTCOM, RADBNo ROA
203.156.36.0/23NTTCOM, RADBNo ROA
203.156.36.0/24NTTCOM, RADBNo ROA
203.156.37.0/24NTTCOM, RADBNo ROA
203.156.38.0/23NTTCOM, RADBNo ROA
203.156.38.0/24NTTCOM, RADBNo ROA
203.156.39.0/24NTTCOM, RADBNo ROA
203.156.40.0/21NTTCOM, RADBNo ROA
203.156.44.0/22NTTCOM, RADBNo ROA
203.156.44.0/23NTTCOM, RADBNo ROA
203.156.44.0/24NTTCOM, RADBNo ROA
203.156.45.0/24NTTCOM, RADBNo ROA
203.156.64.0/18NTTCOM, RADBNo ROA
203.156.64.0/19NTTCOM, RADBNo ROA
203.156.96.0/19NTTCOM, RADBNo ROA
203.156.96.0/21NTTCOM, RADBNo ROA
203.156.96.0/22NTTCOM, RADBNo ROA
203.156.98.0/23NTTCOM, RADBNo ROA
203.156.98.0/24NTTCOM, RADBNo ROA
203.156.99.0/24NTTCOM, RADBNo ROA
203.156.100.0/22NTTCOM, RADBNo ROA
203.156.100.0/23NTTCOM, RADBNo ROA
203.156.100.0/24NTTCOM, RADBNo ROA
203.156.104.0/21NTTCOM, RADBNo ROA
203.156.104.0/22NTTCOM, RADBNo ROA
203.156.104.0/23NTTCOM, RADBNo ROA
203.156.104.0/24NTTCOM, RADBNo ROA
203.156.106.0/23NTTCOM, RADBNo ROA
203.156.108.0/22NTTCOM, RADBNo ROA
203.156.108.0/23NTTCOM, RADBNo ROA
203.156.112.0/21NTTCOM, RADBNo ROA
203.156.112.0/22NTTCOM, RADBNo ROA
203.156.112.0/23NTTCOM, RADBNo ROA
203.156.116.0/22NTTCOM, RADBNo ROA
203.156.116.0/23NTTCOM, RADBNo ROA
203.156.118.0/23NTTCOM, RADBNo ROA
203.156.128.0/19APNIC, NTTCOM, RADBValid
203.156.146.0/24APNIC, NTTCOM, RADBValid
203.156.147.0/24APNIC, NTTCOM, RADBValid
203.156.148.0/24APNIC, NTTCOM, RADBValid
203.156.149.0/24APNIC, NTTCOM, RADBValid
203.156.150.0/24APNIC, NTTCOM, RADBValid
203.156.152.0/21APNIC, NTTCOM, RADBValid
203.156.152.0/24APNIC, NTTCOM, RADBValid
203.156.160.0/19APNIC, NTTCOM, RADBValid

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.