bgpreport

Network · data from 2026-11-12

AS38643 U-Cloud - UNIADEX, LTD.

Registry name: U-Cloud - UNIADEX, LTD., JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38643, 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.
202.55.136.0/22 No ROA Other IRR onlyJPIRR, NTTCOM 673 100% 67
223.223.164.0/23 No ROA Other IRR onlyJPIRR, NTTCOM 672 100% 67
223.223.167.0/24 No ROA Other IRR onlyJPIRR, NTTCOM 669 99% 67

AS-SET

AS38643 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 21 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none202.55.136.0/22No ROA covers it. Add a ROA for AS38643, maxLength 22.673 of 673
Route object: RIR202.55.136.0/22Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none223.223.164.0/23No ROA covers it. Add a ROA for AS38643, maxLength 23.672 of 673
Route object: RIR223.223.164.0/23Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none223.223.167.0/24No ROA covers it. Add a ROA for AS38643, maxLength 24.669 of 673
Route object: RIR223.223.167.0/24Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

202.55.136.0/23NTTCOMNo ROA
202.55.136.0/24JPIRR, NTTCOMNo ROA
202.55.137.0/24JPIRR, NTTCOMNo ROA
202.55.138.0/23NTTCOMNo ROA
202.55.138.0/24JPIRR, NTTCOMNo ROA
202.55.139.0/24JPIRR, NTTCOMNo ROA
203.189.8.0/22NTTCOM, RADBNo ROA
203.189.8.0/23NTTCOM, RADBNo ROA
203.189.8.0/24NTTCOM, RADBNo ROA
203.189.9.0/24NTTCOM, RADBNo ROA
203.189.10.0/23NTTCOM, RADBNo ROA
203.189.10.0/24NTTCOM, RADBNo ROA
203.189.11.0/24NTTCOM, RADBNo ROA
223.223.164.0/24JPIRR, NTTCOMNo ROA
223.223.165.0/24JPIRR, NTTCOMNo 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.