Network · data from 2026-11-12
AS32346 SAKURA-SEA - SAKURA LTD.
Registry name: SAKURA-SEA - SAKURA LTD., US · not in PeeringDB
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% |
| 206.251.53.0/24 | Valid | Other origin onlycovered by 206.251.52.0/22 | 638 95% |
| 206.251.54.0/24 | Valid | Other origin onlycovered by 206.251.52.0/22 | 7 1%low visibility |
| 199.19.16.0/24 | Valid | Nonecovered by 199.19.16.0/22 | 3 0%low visibility |
| 199.19.17.0/24 | Valid | Nonecovered by 199.19.16.0/22 | 3 0%low visibility |
| 199.19.18.0/24 | Valid | Nonecovered by 199.19.16.0/22 | 3 0%low visibility |
| 199.19.19.0/24 | Valid | Nonecovered by 199.19.16.0/22 | 3 0%low visibility |
| 64.49.46.0/23 | Valid | Other origin onlycovered by 64.49.44.0/22 | 2 0%low visibility |
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
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 206.251.52.0/24 | Route 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. |
| Route object: none | 206.251.53.0/24 | Route 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. |
| Route object: none | 206.251.54.0/24 | Route 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. |
| Route object: none | 199.19.16.0/24 | No 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. |
| Route object: none | 199.19.17.0/24 | No 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. |
| Route object: none | 199.19.18.0/24 | No 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. |
| Route object: none | 199.19.19.0/24 | No 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. |
| Route object: none | 64.49.46.0/23 | Route 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. |
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/22 | ARIN | Valid |
| 82.163.64.0/22 | RADB, RIPE | Valid |
| 82.163.168.0/22 | RADB, RIPE | Valid |
| 82.163.224.0/22 | RADB, RIPE | Valid |
| 140.235.9.0/24 | ARIN | Valid |
| 140.235.10.0/24 | ARIN | Valid |
| 199.19.16.0/22 | ARIN | Valid |
| 206.251.52.0/22 | ARIN | Valid |
| 209.248.32.0/20 | RADB | Valid |
| 209.248.32.0/21 | RADB | Valid |
| 209.248.32.0/22 | RADB | Valid |
| 209.248.32.0/23 | RADB | Valid |
| 209.248.32.0/24 | RADB | Valid |
| 209.248.33.0/24 | RADB | Valid |
| 209.248.34.0/23 | RADB | Valid |
| 209.248.34.0/24 | RADB | Valid |
| 209.248.35.0/24 | RADB | Valid |
| 209.248.36.0/22 | RADB | Valid |
| 209.248.36.0/23 | RADB | Valid |
| 209.248.36.0/24 | RADB | Valid |
| 209.248.37.0/24 | RADB | Valid |
| 209.248.38.0/23 | RADB | Valid |
| 209.248.38.0/24 | RADB | Valid |
| 209.248.39.0/24 | RADB | Valid |
| 209.248.40.0/21 | RADB | Valid |
| 209.248.40.0/22 | RADB | Valid |
| 209.248.40.0/23 | RADB | Valid |
| 209.248.40.0/24 | RADB | Valid |
| 209.248.41.0/24 | RADB | Valid |
| 209.248.42.0/23 | RADB | Valid |
| 209.248.42.0/24 | RADB | Valid |
| 209.248.43.0/24 | RADB | Valid |
| 209.248.44.0/22 | RADB | Valid |
| 209.248.44.0/23 | RADB | Valid |
| 209.248.44.0/24 | RADB | Valid |
| 209.248.45.0/24 | RADB | Valid |
| 209.248.46.0/23 | RADB | Valid |
| 209.248.46.0/24 | RADB | Valid |
| 209.248.47.0/24 | RADB | Valid |
| 209.248.48.0/21 | RADB | Valid |
| 209.248.48.0/22 | RADB | Valid |
| 209.248.48.0/23 | RADB | Valid |
| 209.248.48.0/24 | RADB | Valid |
| 209.248.49.0/24 | RADB | Valid |
| 209.248.50.0/23 | RADB | Valid |
| 209.248.50.0/24 | RADB | Valid |
| 209.248.51.0/24 | RADB | Valid |
| 209.248.52.0/22 | RADB | Valid |
| 209.248.52.0/23 | RADB | Valid |
| 209.248.52.0/24 | RADB | Valid |
| 209.248.53.0/24 | RADB | Valid |
| 209.248.54.0/23 | RADB | Valid |
| 209.248.54.0/24 | RADB | Valid |
| 209.248.55.0/24 | RADB | Valid |
| 209.248.56.0/22 | RADB | Valid |
| 209.248.56.0/23 | RADB | Valid |
| 209.248.56.0/24 | RADB | Valid |
| 209.248.57.0/24 | RADB | Valid |
| 209.248.58.0/23 | RADB | Valid |
| 209.248.58.0/24 | RADB | Valid |
| 209.248.59.0/24 | RADB | Valid |
| 209.248.60.0/22 | RADB | Valid |
| 209.248.60.0/23 | RADB | Valid |
| 209.248.60.0/24 | RADB | Valid |
| 209.248.61.0/24 | RADB | Valid |
| 209.248.62.0/23 | RADB | Valid |
| 209.248.62.0/24 | RADB | Valid |
| 209.248.63.0/24 | RADB | Valid |
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.