Network · data from 2026-11-12
AS26768 SAKURA Content
Registry name: SAKURA - SAKURA LTD., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26768, 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.
| 2602:2a4:9d::/48 | Valid | None | 636 100% |
| 140.235.10.0/23 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 2602:2a4:9c::/48 | Valid | RIR databaseARIN | 636 100% |
AS-SET
AS26768'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 75 are in fix.csv.
- Route object: none1
- Route object: RIR1
- Route object: not announced73
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2602:2a4:9d::/48 | No route object for it. Add a route object with origin AS26768 in the RIR database for the space. |
| Route object: RIR | 140.235.10.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26768 whose prefix no peer sees AS26768 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 104.251.233.0/24 | ARIN | Valid |
| 140.235.8.0/22 | RADB | Valid |
| 140.235.8.0/23 | RADB | Valid |
| 140.235.8.0/24 | RADB | Valid |
| 140.235.9.0/24 | ARIN, RADB | Valid |
| 140.235.10.0/24 | RADB | Valid |
| 140.235.11.0/24 | RADB | Valid |
| 209.248.32.0/19 | RADB | 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/20 | 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/21 | 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 |
| 2602:2a4:9a::/48 | ARIN | Valid |
| 2602:2a4:9b::/48 | ARIN | Valid |
| 2602:2a4:9e::/48 | ARIN | 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.