bgpreport

Network · data from 2026-11-12

AS9311 HITRON-AS-AP - HITRON TECHNOLOGY INC.

Registry name: HITRON-AS-AP - HITRON TECHNOLOGY INC., TW · not in PeeringDB

75IPv4 routes 98.7% RPKI valid · 94.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 4 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS9311, seen from no peer

Announced routes

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

103.246.252.0/23 No ROA Other IRR onlyRADB 671 100% 67
210.201.139.0/24 Valid Other origin onlycovered by 210.201.136.0/22 670 100% 67
210.201.138.0/24 Valid Other origin onlycovered by 210.201.136.0/22 667 99% 67
210.200.142.0/24 Valid Other origin onlycovered by 210.200.140.0/22 2 0%low visibility 2
210.200.143.0/24 Valid Other origin onlycovered by 210.200.140.0/22 2 0%low visibility 2
103.122.224.0/24 Valid Other IRR onlyRADB 671 100% 67
150.242.100.0/24 Valid Other IRR onlyRADB 671 100% 67
150.242.101.0/24 Valid Other IRR onlyRADB 671 100% 67
203.79.221.0/24 Valid Other IRR onlyRADB 671 100% 67
203.79.223.0/24 Valid Other IRR onlyRADB 671 100% 67
203.79.224.0/24 Valid Other IRR onlyRADB 671 100% 67
203.79.235.0/24 Valid Other IRR onlyRADB 671 100% 67
222.156.247.0/24 Valid Other IRR onlyRADB 671 100% 67
210.58.98.0/23 Valid Other IRR onlyRADB 670 100% 67
210.58.101.0/24 Valid Other IRR onlyRADB 670 100% 67
210.58.102.0/24 Valid Other IRR onlyRADB 670 100% 67
210.63.239.0/24 Valid Other IRR onlyRADB 670 100% 67
210.63.240.0/24 Valid Other IRR onlyRADB 670 100% 67
210.63.253.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.17.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.79.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.106.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.128.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.132.0/23 Valid Other IRR onlyRADB 670 100% 67
210.200.134.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.136.0/23 Valid Other IRR onlyRADB 670 100% 67
210.200.138.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.140.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.144.0/23 Valid Other IRR onlyRADB 670 100% 67
210.200.180.0/23 Valid Other IRR onlyRADB 670 100% 67
210.200.182.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.183.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.190.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.216.0/22 Valid Other IRR onlyRADB 670 100% 67
210.200.216.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.217.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.218.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.221.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.222.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.228.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.229.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.247.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.251.0/24 Valid Other IRR onlyRADB 670 100% 67
210.200.255.0/24 Valid Other IRR onlyRADB 670 100% 67
210.201.52.0/23 Valid Other IRR onlyRADB 670 100% 67
210.201.54.0/24 Valid Other IRR onlyRADB 670 100% 67
210.201.61.0/24 Valid Other IRR onlyRADB 670 100% 67
210.201.74.0/24 Valid Other IRR onlyRADB 670 100% 67
210.201.75.0/24 Valid Other IRR onlyRADB 670 100% 67
210.201.76.0/24 Valid Other IRR onlyRADB 670 100% 67
210.201.77.0/24 Valid Other IRR onlyRADB 670 100% 67
210.201.79.0/24 Valid Other IRR onlyRADB 670 100% 67
210.201.80.0/24 Valid Other IRR onlyRADB 670 100% 67
210.201.136.0/22 Valid Other IRR onlyRADB 670 100% 67
210.202.233.0/24 Valid Other IRR onlyRADB 670 100% 67
210.203.2.0/24 Valid Other IRR onlyRADB 670 100% 67
210.203.16.0/24 Valid Other IRR onlyRADB 670 100% 67
2404:0:4000::/36 Valid Other IRR onlyRADB 635 100% 67
210.200.141.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
103.30.253.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.30.255.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.70.181.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.70.182.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.70.183.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.103.169.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.103.171.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.234.44.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.234.45.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.240.81.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.240.83.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
185.171.169.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
185.171.171.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
202.58.20.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
202.58.22.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
202.58.26.0/24 Valid RIR databaseAPNIC 671 100% 67
202.58.27.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS9311 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 76 are in fix.csv.

  • ROA: none1
  • Route object: none4
  • Route object: RIR55
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none103.246.252.0/23No ROA covers it. Add a ROA for AS9311, maxLength 23.671 of 673
Route object: RIR103.246.252.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none210.201.139.0/24Route objects for it name AS17709. A route object for 210.201.136.0/22 with origin AS9311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9311 in the RIR database for the space.670 of 673
Route object: none210.201.138.0/24Route objects for it name AS17709. A route object for 210.201.136.0/22 with origin AS9311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9311 in the RIR database for the space.667 of 673
Route object: none210.200.142.0/24Route objects for it name AS17709. A route object for 210.200.140.0/22 with origin AS9311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9311 in the RIR database for the space.2 of 673
Route object: none210.200.143.0/24Route objects for it name AS17709. A route object for 210.200.140.0/22 with origin AS9311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9311 in the RIR database for the space.2 of 673
Route object: RIR103.122.224.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR150.242.100.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR150.242.101.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.79.221.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.79.223.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.79.224.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR203.79.235.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR222.156.247.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.58.98.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.58.101.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.58.102.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.63.239.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.63.240.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.63.253.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.17.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.79.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.106.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.128.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.132.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.134.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.136.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.138.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.140.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.144.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.180.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.182.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.183.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.190.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.216.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.216.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.217.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.218.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.221.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.222.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.228.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.229.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.247.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.251.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.200.255.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.52.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.54.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.61.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.74.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.75.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.76.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.77.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.79.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.80.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.201.136.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.202.233.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.203.2.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR210.203.16.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2404:0:4000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR210.200.141.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.124.60.0/22RADBNo ROA
103.15.79.0/24APNIC, RADBValid
103.24.160.0/22RADBNo ROA
103.154.20.0/23RADBNo ROA
103.224.56.0/24APNIC, NTTCOM, RADBValid
103.224.59.0/24APNIC, NTTCOM, RADBValid
202.58.26.0/23RADBNo ROA
202.58.30.0/23RADBNo ROA
202.58.30.0/24APNICValid
202.58.31.0/24APNICValid
203.79.220.0/24NTTCOMValid
203.79.222.0/24NTTCOM, RADBValid
203.119.94.0/24RADBValid
210.200.140.0/22RADBValid
210.200.144.0/24RADBValid
210.200.211.0/24RADBValid

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.