Network · data from 2026-11-12
AS57175 SAKURA-AS Tianhai InfoTech Limited
Registry name: SAKURA-AS Tianhai InfoTech Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57175, 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.
| 2a13:1802:c010::/44 | No ROA | Nonecovered by 2a13:1802:c000::/36 | 632 99% |
| 2a13:1802:c001::/48 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
AS57175 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 6 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a13:1802:c010::/44 | No ROA covers it. Add a ROA for AS57175, maxLength 44. |
| Route object: none | 2a13:1802:c010::/44 | No route object for it. A route object for 2a13:1802:c000::/36 with origin AS57175 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57175 in the RIR database for the space. |
| Route object: RIR | 2a13:1802:c001::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS57175 whose prefix no peer sees AS57175 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:2a4::/40 | ARIN | No ROA |
| 2602:2a4::/44 | ARIN | No ROA |
| 2a13:1802:c000::/36 | RIPE | No ROA |
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.