bgpreport

Network · data from 2026-11-12

AS38851 TNET Communication

Registry name: TNET-NET - TNET Communication Inc. 10F., No.78, Sec. 2, Chongxin Rd., Sanchong Dist.,New Taipei City, Taiwan (R.O.C Taiwan 241), TW · PeeringDB

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

Announced routes

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

119.15.200.0/21 Valid Other origin only 672 100% 66
119.15.216.0/21 Valid Other origin only 672 100% 66
61.65.240.0/21 Valid Nonecovered by 61.65.240.0/20 161 24% 54
61.65.248.0/21 Valid Nonecovered by 61.65.240.0/20 160 24% 54
119.15.216.0/22 Valid Other origin only 159 24% 54
119.15.220.0/22 Valid Other origin only 159 24% 54
150.116.120.0/22 Valid Nonecovered by 150.116.120.0/21 159 24% 54
119.15.200.0/22 Valid Other origin only 121 18% 43
43.227.24.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
43.227.25.0/24 Valid Other IRR onlyRADB 673 100% 68
43.227.26.0/23 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
43.250.44.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
103.3.192.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
103.46.188.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
103.229.100.0/23 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
150.117.0.0/20 Valid Other IRR onlyRADB 673 100% 68
58.115.8.0/21 Valid Other IRR onlyRADB 672 100% 68
58.115.16.0/20 Valid Other IRR onlyRADB 672 100% 68
58.115.32.0/19 Valid Other IRR onlyRADB 672 100% 68
58.115.48.0/21 Valid Other IRR onlyRADB 672 100% 68
58.115.192.0/20 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
103.229.100.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
113.196.144.0/21 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
203.133.56.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
203.203.220.0/22 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
203.203.224.0/19 Valid Other IRR onlyNTTCOM, RADB 672 100% 68
61.65.240.0/20 Valid Other IRR onlyRADB 671 100% 66
103.131.172.0/22 Valid Other IRR onlyRADB 671 100% 68
103.197.174.0/23 Valid Other IRR onlyNTTCOM, RADB 671 100% 66
103.234.76.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 66
150.116.120.0/21 Valid Other IRR onlyRADB 671 100% 66
43.227.24.0/23 Valid Other IRR onlyRADB 670 100% 67
60.245.120.0/21 Valid Other IRR onlyRADB 670 100% 67
103.229.102.0/23 Valid Other IRR onlyRADB 670 100% 67
122.146.108.0/23 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
122.147.160.0/22 Valid Other IRR onlyRADB 670 100% 67
122.147.160.0/23 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
122.147.164.0/23 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
150.117.0.0/21 Valid Other IRR onlyNTTCOM, RADB 160 24% 54
150.117.8.0/21 Valid Other IRR onlyNTTCOM, RADB 160 24% 54
103.3.192.0/23 Valid Other IRR onlyNTTCOM, RADB 76 11% 40
103.3.194.0/23 Valid Other IRR onlyNTTCOM, RADB 76 11% 40
43.226.232.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.5.100.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.46.144.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.246.208.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
223.26.80.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
223.26.108.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.5.100.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 76 11% 40
103.5.102.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 76 11% 40
103.246.208.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 76 11% 40
103.246.210.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 76 11% 40
223.26.80.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 76 11% 40
223.26.82.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 76 11% 40
223.26.108.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 76 11% 40
223.26.110.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 76 11% 40

AS-SET

AS38851'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 161 are in fix.csv.

  • Route object: none8
  • Route object: RIR34
  • Route object: not announced119
ChangePrefix or setDetailFull-table peers
Route object: none119.15.200.0/21Route objects for it name AS18046. Add a route object with origin AS38851 in the RIR database for the space.672 of 673
Route object: none119.15.216.0/21Route objects for it name AS18046. Add a route object with origin AS38851 in the RIR database for the space.672 of 673
Route object: none61.65.240.0/21No route object for it. A route object for 61.65.240.0/20 with origin AS38851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38851 in the RIR database for the space.161 of 673
Route object: none61.65.248.0/21No route object for it. A route object for 61.65.240.0/20 with origin AS38851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38851 in the RIR database for the space.160 of 673
Route object: none119.15.216.0/22Route objects for it name AS18046. Add a route object with origin AS38851 in the RIR database for the space.159 of 673
Route object: none119.15.220.0/22Route objects for it name AS18046. Add a route object with origin AS38851 in the RIR database for the space.159 of 673
Route object: none150.116.120.0/22No route object for it. A route object for 150.116.120.0/21 with origin AS38851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38851 in the RIR database for the space.159 of 673
Route object: none119.15.200.0/22Route objects for it name AS18046. Add a route object with origin AS38851 in the RIR database for the space.121 of 673
Route object: RIR43.227.24.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.227.25.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.227.26.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.250.44.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.3.192.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.46.188.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.229.100.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR150.117.0.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR58.115.8.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.115.16.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.115.32.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.115.48.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR58.115.192.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.229.100.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.196.144.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.133.56.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.203.220.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.203.224.0/19Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR61.65.240.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.131.172.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.197.174.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.234.76.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR150.116.120.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR43.227.24.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR60.245.120.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.229.102.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR122.146.108.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR122.147.160.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR122.147.160.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR122.147.164.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR150.117.0.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.160 of 673
Route object: RIR150.117.8.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.160 of 673
Route object: RIR103.3.192.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.76 of 673
Route object: RIR103.3.194.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.76 of 673

Route objects not announced

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

43.226.232.0/23APNIC, NTTCOM, RADBValid
43.226.234.0/23APNIC, NTTCOM, RADBValid
43.250.44.0/23RADBValid
43.250.46.0/23RADBValid
58.115.48.0/22RADBValid
58.115.48.0/23RADBValid
58.115.48.0/24RADBValid
58.115.49.0/24RADBValid
58.115.50.0/23RADBValid
58.115.50.0/24RADBValid
58.115.51.0/24RADBValid
58.115.52.0/22RADBValid
58.115.52.0/23RADBValid
58.115.52.0/24RADBValid
58.115.53.0/24RADBValid
58.115.54.0/23RADBValid
58.115.54.0/24RADBValid
58.115.55.0/24RADBValid
60.245.120.0/22RADBValid
60.245.120.0/23RADBValid
60.245.120.0/24RADBValid
60.245.121.0/24RADBValid
60.245.122.0/23RADBValid
60.245.122.0/24RADBValid
60.245.123.0/24RADBValid
60.245.124.0/22RADBValid
60.245.124.0/23RADBValid
60.245.124.0/24RADBValid
60.245.125.0/24RADBValid
60.245.126.0/23RADBValid
60.245.126.0/24RADBValid
60.245.127.0/24RADBValid
103.3.192.0/24APNIC, NTTCOM, RADBValid
103.3.193.0/24APNIC, NTTCOM, RADBValid
103.3.194.0/24APNIC, NTTCOM, RADBValid
103.3.195.0/24APNIC, NTTCOM, RADBValid
103.5.100.0/24APNIC, NTTCOM, RADBValid
103.5.101.0/24APNIC, NTTCOM, RADBValid
103.5.102.0/24APNIC, NTTCOM, RADBValid
103.5.103.0/24APNIC, NTTCOM, RADBValid
103.46.144.0/23APNIC, NTTCOM, RADBValid
103.46.146.0/23APNIC, NTTCOM, RADBValid
103.46.188.0/23RADBValid
103.46.190.0/23RADBValid
103.131.172.0/24RADBValid
103.131.173.0/24RADBValid
103.131.174.0/24RADBValid
103.131.175.0/24RADBValid
103.197.174.0/24NTTCOM, RADBValid
103.197.175.0/24NTTCOM, RADBValid
103.234.76.0/23RADBValid
103.234.76.0/24RADBValid
103.234.77.0/24RADBValid
103.234.78.0/23RADBValid
103.234.78.0/24RADBValid
103.234.79.0/24RADBValid
103.246.208.0/24APNIC, NTTCOM, RADBValid
103.246.209.0/24APNIC, NTTCOM, RADBValid
103.246.210.0/24APNIC, NTTCOM, RADBValid
103.246.211.0/24APNIC, NTTCOM, RADBValid
113.196.144.0/22NTTCOM, RADBValid
113.196.144.0/23NTTCOM, RADBValid
113.196.144.0/24NTTCOM, RADBValid
113.196.145.0/24NTTCOM, RADBValid
113.196.146.0/23NTTCOM, RADBValid
113.196.146.0/24NTTCOM, RADBValid
113.196.147.0/24NTTCOM, RADBValid
113.196.148.0/22NTTCOM, RADBValid
113.196.148.0/23NTTCOM, RADBValid
113.196.148.0/24NTTCOM, RADBValid
113.196.149.0/24NTTCOM, RADBValid
113.196.150.0/23NTTCOM, RADBValid
113.196.150.0/24NTTCOM, RADBValid
113.196.151.0/24NTTCOM, RADBValid
122.146.108.0/24NTTCOM, RADBValid
122.146.109.0/24NTTCOM, RADBValid
122.147.160.0/24NTTCOM, RADBValid
122.147.161.0/24NTTCOM, RADBValid
122.147.162.0/23RADBValid
122.147.162.0/24RADBValid
122.147.163.0/24RADBValid
122.147.164.0/24NTTCOM, RADBValid
122.147.165.0/24NTTCOM, RADBValid
150.117.0.0/22NTTCOM, RADBValid
150.117.0.0/23NTTCOM, RADBValid
150.117.0.0/24NTTCOM, RADBValid
150.117.1.0/24NTTCOM, RADBValid
150.117.2.0/23NTTCOM, RADBValid
150.117.2.0/24NTTCOM, RADBValid
150.117.3.0/24NTTCOM, RADBValid
150.117.4.0/22NTTCOM, RADBValid
150.117.4.0/23NTTCOM, RADBValid
150.117.4.0/24NTTCOM, RADBValid
150.117.5.0/24NTTCOM, RADBValid
150.117.6.0/23NTTCOM, RADBValid
150.117.6.0/24NTTCOM, RADBValid
150.117.7.0/24NTTCOM, RADBValid
150.117.8.0/22NTTCOM, RADBValid
150.117.8.0/23NTTCOM, RADBValid
150.117.8.0/24NTTCOM, RADBValid
150.117.9.0/24NTTCOM, RADBValid
150.117.10.0/23NTTCOM, RADBValid
150.117.10.0/24NTTCOM, RADBValid
150.117.11.0/24NTTCOM, RADBValid
150.117.12.0/22NTTCOM, RADBValid
150.117.12.0/23NTTCOM, RADBValid
150.117.12.0/24NTTCOM, RADBValid
150.117.13.0/24NTTCOM, RADBValid
150.117.14.0/23NTTCOM, RADBValid
150.117.14.0/24NTTCOM, RADBValid
150.117.15.0/24NTTCOM, RADBValid
223.26.80.0/24NTTCOM, RADBValid
223.26.81.0/24NTTCOM, RADBValid
223.26.82.0/24NTTCOM, RADBValid
223.26.83.0/24NTTCOM, RADBValid
223.26.108.0/24APNIC, NTTCOM, RADBValid
223.26.109.0/24APNIC, NTTCOM, RADBValid
223.26.110.0/24APNIC, NTTCOM, RADBValid
223.26.111.0/24APNIC, 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.