bgpreport

Network · data from 2026-11-12

AS9216 PUNET-AP - PUNET Taiwan

Registry name: PUNET-AP - PUNET Taiwan, TW · not in PeeringDB

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

Announced routes

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

2402:4900::/32 No ROA Other IRR onlyRADB 633 100% 68
211.76.136.0/24 Valid Other origin onlycovered by 211.76.128.0/20 3 0%low visibility 3
202.154.192.0/19 Valid Other IRR onlyNTTCOM, REACH 673 100% 67
203.135.64.0/19 Valid Other IRR onlyNTTCOM, RADB, REACH 673 100% 67
211.76.128.0/20 Valid Other IRR onlyNTTCOM, REACH 673 100% 67
202.154.198.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.154.210.0/24 Valid RIR databaseAPNIC 671 100% 67
202.154.209.0/24 Valid RIR databaseAPNIC 338 50% 63

AS-SET

AS9216 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 192 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced186
ChangePrefix or setDetailFull-table peers
ROA: none2402:4900::/32No ROA covers it. Add a ROA for AS9216, maxLength 32.633 of 636
Route object: RIR2402:4900::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: none211.76.136.0/24Route objects for it name AS56179. A route object for 211.76.128.0/20 with origin AS9216 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9216 in the RIR database for the space.3 of 673
Route object: RIR202.154.192.0/19Route object only in NTTCOM, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR203.135.64.0/19Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.673 of 673
Route object: RIR211.76.128.0/20Route object only in NTTCOM, REACH. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

122.144.32.0/19APNIC, NTTCOM, RADBValid
122.144.32.0/20APNICValid
122.144.32.0/21APNICValid
122.144.32.0/22APNICValid
122.144.32.0/23APNICValid
122.144.32.0/24APNICValid
122.144.33.0/24APNICValid
122.144.34.0/23APNICValid
122.144.34.0/24APNICValid
122.144.35.0/24APNICValid
122.144.36.0/22APNICValid
122.144.36.0/23APNICValid
122.144.36.0/24APNICValid
122.144.37.0/24APNICValid
122.144.38.0/23APNICValid
122.144.38.0/24APNICValid
122.144.39.0/24APNICValid
122.144.40.0/21APNICValid
122.144.40.0/22APNICValid
122.144.40.0/23APNICValid
122.144.40.0/24APNICValid
122.144.41.0/24APNICValid
122.144.42.0/23APNICValid
122.144.42.0/24APNICValid
122.144.43.0/24APNICValid
122.144.44.0/22APNICValid
122.144.44.0/23APNICValid
122.144.44.0/24APNICValid
122.144.45.0/24APNICValid
122.144.46.0/23APNICValid
122.144.46.0/24APNICValid
122.144.47.0/24APNICValid
122.144.48.0/20APNICValid
122.144.48.0/21APNICValid
122.144.48.0/22APNICValid
122.144.48.0/23APNICValid
122.144.48.0/24APNICValid
122.144.49.0/24APNICValid
122.144.50.0/23APNICValid
122.144.50.0/24APNICValid
122.144.51.0/24APNICValid
122.144.52.0/22APNICValid
122.144.52.0/23APNICValid
122.144.52.0/24APNICValid
122.144.53.0/24APNICValid
122.144.54.0/23APNICValid
122.144.54.0/24APNICValid
122.144.55.0/24APNICValid
122.144.56.0/21APNICValid
122.144.56.0/22APNICValid
122.144.56.0/23APNICValid
122.144.56.0/24APNICValid
122.144.57.0/24APNICValid
122.144.58.0/23APNICValid
122.144.58.0/24APNICValid
122.144.59.0/24APNICValid
122.144.60.0/22APNICValid
122.144.60.0/23APNICValid
122.144.60.0/24APNICValid
122.144.61.0/24APNICValid
122.144.62.0/23APNICValid
122.144.62.0/24APNICValid
122.144.63.0/24APNICValid
202.5.4.0/23REACHNo ROA
202.154.192.0/20APNIC, RADBValid
202.154.192.0/21APNICValid
202.154.192.0/22APNICValid
202.154.192.0/23APNICValid
202.154.192.0/24APNICValid
202.154.193.0/24APNICValid
202.154.194.0/23APNICValid
202.154.194.0/24APNICValid
202.154.195.0/24APNICValid
202.154.196.0/22APNICValid
202.154.196.0/23APNICValid
202.154.196.0/24APNICValid
202.154.197.0/24APNICValid
202.154.198.0/23APNICValid
202.154.199.0/24APNICValid
202.154.200.0/21APNICValid
202.154.200.0/22APNICValid
202.154.200.0/23APNICValid
202.154.200.0/24APNICValid
202.154.201.0/24APNICValid
202.154.202.0/23APNICValid
202.154.202.0/24APNICValid
202.154.203.0/24APNICValid
202.154.204.0/22APNICValid
202.154.204.0/23APNICValid
202.154.204.0/24APNICValid
202.154.205.0/24APNICValid
202.154.206.0/23APNICValid
202.154.206.0/24APNICValid
202.154.207.0/24APNICValid
202.154.208.0/20APNICValid
202.154.208.0/21APNICValid
202.154.208.0/22APNICValid
202.154.208.0/23APNICValid
202.154.208.0/24APNICValid
202.154.210.0/23APNICValid
202.154.211.0/24APNICValid
202.154.212.0/22APNICValid
202.154.212.0/23APNICValid
202.154.212.0/24APNICValid
202.154.213.0/24APNICValid
202.154.214.0/23APNICValid
202.154.214.0/24APNICValid
202.154.215.0/24APNICValid
202.154.216.0/21APNICValid
202.154.216.0/22APNICValid
202.154.216.0/23APNICValid
202.154.216.0/24APNICValid
202.154.217.0/24APNICValid
202.154.218.0/23APNICValid
202.154.218.0/24APNICValid
202.154.219.0/24APNICValid
202.154.220.0/22APNICValid
202.154.220.0/23APNICValid
202.154.220.0/24APNICValid
202.154.221.0/24APNICValid
202.154.222.0/23APNICValid
202.154.222.0/24APNICValid
202.154.223.0/24APNICValid
203.135.64.0/20APNICValid
203.135.64.0/21APNICValid
203.135.64.0/22APNICValid
203.135.64.0/23APNICValid
203.135.64.0/24APNICValid
203.135.65.0/24APNICValid
203.135.66.0/23APNICValid
203.135.66.0/24APNICValid
203.135.67.0/24APNICValid
203.135.68.0/22APNICValid
203.135.68.0/23APNICValid
203.135.68.0/24APNICValid
203.135.69.0/24APNICValid
203.135.70.0/23APNICValid
203.135.70.0/24APNICValid
203.135.71.0/24APNICValid
203.135.72.0/21APNICValid
203.135.72.0/22APNICValid
203.135.72.0/23APNICValid
203.135.72.0/24APNICValid
203.135.73.0/24APNICValid
203.135.74.0/23APNICValid
203.135.74.0/24APNICValid
203.135.75.0/24APNICValid
203.135.76.0/22APNICValid
203.135.76.0/23APNICValid
203.135.76.0/24APNICValid
203.135.77.0/24APNICValid
203.135.78.0/23APNICValid
203.135.78.0/24APNICValid
203.135.79.0/24APNICValid
203.135.80.0/20APNICValid
203.135.80.0/21APNICValid
203.135.80.0/22APNICValid
203.135.80.0/23APNICValid
203.135.80.0/24APNICValid
203.135.81.0/24APNICValid
203.135.82.0/23APNICValid
203.135.82.0/24APNICValid
203.135.83.0/24APNICValid
203.135.84.0/22APNICValid
203.135.84.0/23APNICValid
203.135.84.0/24APNICValid
203.135.85.0/24APNICValid
203.135.86.0/23APNICValid
203.135.86.0/24APNICValid
203.135.87.0/24APNICValid
203.135.88.0/21APNICValid
203.135.88.0/22APNICValid
203.135.88.0/23APNICValid
203.135.88.0/24APNICValid
203.135.89.0/24APNICValid
203.135.90.0/23APNICValid
203.135.90.0/24APNICValid
203.135.91.0/24APNICValid
203.135.92.0/22APNICValid
203.135.92.0/23APNICValid
203.135.92.0/24APNICValid
203.135.93.0/24APNICValid
203.135.94.0/23APNICValid
203.135.94.0/24APNICValid
203.135.95.0/24APNICValid
211.76.128.0/21RADBValid

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.