bgpreport

Network · data from 2026-11-12

AS9466 UUNET-JP-AP - UUNET Japan Limited

Registry name: UUNET-JP-AP - UUNET Japan Limited, JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9466, 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.
138.198.0.0/16 No ROA Other origin only 672 100% 67
202.125.0.0/22 No ROA None 672 100% 67
202.125.4.0/22 No ROA None 672 100% 67
103.3.198.0/24 No ROA Other IRR onlyNTTCOM 671 100% 67
144.250.40.0/24 No ROA Other IRR onlyRADB 641 95% 67
138.198.4.0/24 No ROA RIR databaseRIPE 672 100% 66
103.109.16.0/24 No ROA RIR databaseAPNIC 671 100% 67
203.6.64.0/21 Valid Other IRR onlyRADB 673 100% 67
203.6.72.0/21 Valid Other IRR onlyRADB 673 100% 67
203.6.118.0/24 Valid Other IRR onlyRADB 673 100% 67
203.6.119.0/24 Valid Other IRR onlyRADB 673 100% 67
203.6.120.0/24 Valid Other IRR onlyRADB 673 100% 67
203.5.217.0/24 Valid RIR databaseAPNIC 673 100% 67
203.6.31.0/24 Valid RIR databaseAPNIC 673 100% 67
203.6.32.0/24 Valid RIR databaseAPNIC 673 100% 67
203.6.33.0/24 Valid RIR databaseAPNIC 673 100% 67
203.6.36.0/22 Valid RIR databaseAPNIC 673 100% 67
203.6.121.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
203.10.217.0/24 Valid RIR databaseAPNIC 673 100% 67
203.11.0.0/24 Valid RIR databaseAPNIC 673 100% 67
202.1.128.0/19 Valid RIR databaseAPNIC 672 100% 67
2401:6bff::/40 Valid RIR databaseAPNIC 636 100% 67
2401:6bff:8000::/40 Valid RIR databaseAPNIC 636 100% 67

AS-SET

AS9466 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 18 are in fix.csv.

  • ROA: none7
  • Route object: none3
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none138.198.0.0/16No ROA covers it. Add a ROA for AS9466, maxLength 16.672 of 673
Route object: none138.198.0.0/16Route objects for it name AS2830, AS4862. Add a route object with origin AS9466 in the RIR database for the space.672 of 673
ROA: none202.125.0.0/22No ROA covers it. Add a ROA for AS9466, maxLength 22.672 of 673
Route object: none202.125.0.0/22No route object for it. Add a route object with origin AS9466 in the RIR database for the space.672 of 673
ROA: none202.125.4.0/22No ROA covers it. Add a ROA for AS9466, maxLength 22.672 of 673
Route object: none202.125.4.0/22No route object for it. Add a route object with origin AS9466 in the RIR database for the space.672 of 673
ROA: none103.3.198.0/24No ROA covers it. Add a ROA for AS9466, maxLength 24.671 of 673
Route object: RIR103.3.198.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none144.250.40.0/24No ROA covers it. Add a ROA for AS9466, maxLength 24.641 of 673
Route object: RIR144.250.40.0/24Route object only in RADB. Add it in the RIR database for the space.641 of 673
ROA: none138.198.4.0/24No ROA covers it. Add a ROA for AS9466, maxLength 24.672 of 673
ROA: none103.109.16.0/24No ROA covers it. Add a ROA for AS9466, maxLength 24.671 of 673
Route object: RIR203.6.64.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.6.72.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.6.118.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.6.119.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR203.6.120.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

103.21.80.0/24APNICNo 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.