bgpreport

Network · data from 2026-11-12

AS32346 SAKURA-SEA - SAKURA LTD.

Registry name: SAKURA-SEA - SAKURA LTD., US · not in PeeringDB

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

Announced routes

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

206.251.52.0/24 Valid Other origin onlycovered by 206.251.52.0/22 638 95% 65
206.251.53.0/24 Valid Other origin onlycovered by 206.251.52.0/22 638 95% 65
206.251.54.0/24 Valid Other origin onlycovered by 206.251.52.0/22 7 1%low visibility 4
199.19.16.0/24 Valid Nonecovered by 199.19.16.0/22 3 0%low visibility 2
199.19.17.0/24 Valid Nonecovered by 199.19.16.0/22 3 0%low visibility 2
199.19.18.0/24 Valid Nonecovered by 199.19.16.0/22 3 0%low visibility 2
199.19.19.0/24 Valid Nonecovered by 199.19.16.0/22 3 0%low visibility 2
64.49.46.0/23 Valid Other origin onlycovered by 64.49.44.0/22 2 0%low visibility 2

AS-SET

AS32346 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.

  • Route object: none8
  • Route object: not announced68
ChangePrefix or setDetailFull-table peers
Route object: none206.251.52.0/24Route objects for it name AS49304. A route object for 206.251.52.0/22 with origin AS32346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32346 in the RIR database for the space.638 of 673
Route object: none206.251.53.0/24Route objects for it name AS49304. A route object for 206.251.52.0/22 with origin AS32346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32346 in the RIR database for the space.638 of 673
Route object: none206.251.54.0/24Route objects for it name AS49304. A route object for 206.251.52.0/22 with origin AS32346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32346 in the RIR database for the space.7 of 673
Route object: none199.19.16.0/24No route object for it. A route object for 199.19.16.0/22 with origin AS32346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32346 in the RIR database for the space.3 of 673
Route object: none199.19.17.0/24No route object for it. A route object for 199.19.16.0/22 with origin AS32346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32346 in the RIR database for the space.3 of 673
Route object: none199.19.18.0/24No route object for it. A route object for 199.19.16.0/22 with origin AS32346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32346 in the RIR database for the space.3 of 673
Route object: none199.19.19.0/24No route object for it. A route object for 199.19.16.0/22 with origin AS32346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32346 in the RIR database for the space.3 of 673
Route object: none64.49.46.0/23Route objects for it name AS49304. A route object for 64.49.44.0/22 with origin AS32346 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32346 in the RIR database for the space.2 of 673

Route objects not announced

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

64.49.44.0/22ARINValid
82.163.64.0/22RADB, RIPEValid
82.163.168.0/22RADB, RIPEValid
82.163.224.0/22RADB, RIPEValid
140.235.9.0/24ARINValid
140.235.10.0/24ARINValid
199.19.16.0/22ARINValid
206.251.52.0/22ARINValid
209.248.32.0/20RADBValid
209.248.32.0/21RADBValid
209.248.32.0/22RADBValid
209.248.32.0/23RADBValid
209.248.32.0/24RADBValid
209.248.33.0/24RADBValid
209.248.34.0/23RADBValid
209.248.34.0/24RADBValid
209.248.35.0/24RADBValid
209.248.36.0/22RADBValid
209.248.36.0/23RADBValid
209.248.36.0/24RADBValid
209.248.37.0/24RADBValid
209.248.38.0/23RADBValid
209.248.38.0/24RADBValid
209.248.39.0/24RADBValid
209.248.40.0/21RADBValid
209.248.40.0/22RADBValid
209.248.40.0/23RADBValid
209.248.40.0/24RADBValid
209.248.41.0/24RADBValid
209.248.42.0/23RADBValid
209.248.42.0/24RADBValid
209.248.43.0/24RADBValid
209.248.44.0/22RADBValid
209.248.44.0/23RADBValid
209.248.44.0/24RADBValid
209.248.45.0/24RADBValid
209.248.46.0/23RADBValid
209.248.46.0/24RADBValid
209.248.47.0/24RADBValid
209.248.48.0/21RADBValid
209.248.48.0/22RADBValid
209.248.48.0/23RADBValid
209.248.48.0/24RADBValid
209.248.49.0/24RADBValid
209.248.50.0/23RADBValid
209.248.50.0/24RADBValid
209.248.51.0/24RADBValid
209.248.52.0/22RADBValid
209.248.52.0/23RADBValid
209.248.52.0/24RADBValid
209.248.53.0/24RADBValid
209.248.54.0/23RADBValid
209.248.54.0/24RADBValid
209.248.55.0/24RADBValid
209.248.56.0/22RADBValid
209.248.56.0/23RADBValid
209.248.56.0/24RADBValid
209.248.57.0/24RADBValid
209.248.58.0/23RADBValid
209.248.58.0/24RADBValid
209.248.59.0/24RADBValid
209.248.60.0/22RADBValid
209.248.60.0/23RADBValid
209.248.60.0/24RADBValid
209.248.61.0/24RADBValid
209.248.62.0/23RADBValid
209.248.62.0/24RADBValid
209.248.63.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.