Network · data from 2026-11-12
AS59025 SKBJNET - Beijing Sankuai Technology Co.,Ltd.
Registry name: SKBJNET - Beijing Sankuai Technology Co.,Ltd., CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59025, 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.
| 101.236.8.0/21 | Valid | Other origin only | 1 0%low visibility |
| 101.236.64.0/21 | Valid | Other origin only | 1 0%low visibility |
| 103.37.136.0/21 | Valid | Other origin only | 1 0%low visibility |
| 103.37.152.0/21 | Valid | Other origin only | 1 0%low visibility |
AS-SET
AS59025 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 5 are in fix.csv.
- Route object: none4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 101.236.8.0/21 | Route objects for it name AS23724. Add a route object with origin AS59025 in the RIR database for the space. |
| Route object: none | 101.236.64.0/21 | Route objects for it name AS23724. Add a route object with origin AS59025 in the RIR database for the space. |
| Route object: none | 103.37.136.0/21 | Route objects for it name AS23724. Add a route object with origin AS59025 in the RIR database for the space. |
| Route object: none | 103.37.152.0/21 | Route objects for it name AS23724. Add a route object with origin AS59025 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59025 whose prefix no peer sees AS59025 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 101.236.56.0/21 | 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.