bgpreport

Network · data from 2026-11-12

AS401339 YAMATO CLOUD LLC

Registry name: YCL-US - YAMATO CLOUD LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401339, 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.
74.1.206.0/24 Valid Other IRR onlyRADB 672 100% 67
74.1.207.0/24 Valid Other IRR onlyRADB 672 100% 67
14.137.238.0/23 Valid Other IRR onlyRADB 671 100% 66
14.137.238.0/24 Valid Other IRR onlyRADB 457 68% 66
14.137.239.0/24 Valid Other IRR onlyRADB 456 68% 66
23.188.72.0/24 Valid RIR databaseARIN, RADB 673 100% 67
74.1.206.0/23 Valid RIR databaseARIN, RADB 671 100% 68
207.174.132.0/23 Valid RIR databaseARIN 671 100% 67
207.174.134.0/23 Valid RIR databaseARIN 670 100% 68
23.188.168.0/24 Valid RIR databaseARIN, RADB 669 99% 67
207.174.132.0/24 Valid RIR databaseARIN 296 44% 59
207.174.133.0/24 Valid RIR databaseARIN 293 44% 59
207.174.135.0/24 Valid RIR databaseARIN 197 29% 56
207.174.134.0/24 Valid RIR databaseARIN 179 27% 55

AS-SET

AS401339'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 8 are in fix.csv.

  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR74.1.206.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.1.207.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR14.137.238.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR14.137.238.0/24Route object only in RADB. Add it in the RIR database for the space.457 of 673
Route object: RIR14.137.239.0/24Route object only in RADB. Add it in the RIR database for the space.456 of 673

Route objects not announced

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

207.174.132.0/22ARIN, RADBValid
2602:f825::/40ARIN, RADBValid
2602:f836::/40ARIN, 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.