Network · data from 2026-11-12
AS402587 SAKURADREAM
Registry name: SAKURADREAM - Enhosting, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS402587, 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:f3b7:24::/48 | Valid | Other origin onlycovered by 2602:f3b7::/40 | 636 100% |
| 2602:f3b7:62::/48 | Valid | Other origin onlycovered by 2602:f3b7::/40 | 3 0%low visibility |
| 2602:f3b7:27::/48 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 23.158.164.0/24 | Valid | RIR databaseARIN | 2 0%low visibility |
AS-SET
AS402587'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 4 are in fix.csv.
- Route object: none2
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2602:f3b7:24::/48 | Route objects for it name AS31898. A route object for 2602:f3b7::/40 with origin AS402587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402587 in the RIR database for the space. |
| Route object: none | 2602:f3b7:62::/48 | Route objects for it name AS31898. A route object for 2602:f3b7::/40 with origin AS402587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402587 in the RIR database for the space. |
| Route object: RIR | 2602:f3b7:27::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS402587 whose prefix no peer sees AS402587 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:f3b7::/40 | 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.