bgpreport

Network · data from 2026-11-12

AS55962 Beijing Kuaishou Technology Co.

Registry name: KUAISHOU-KJ-NET - Beijing Kuaishou Technology Co., Ltd., CN · PeeringDB

0IPv4 routes
3IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS55962, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55962, 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.

2402:5ec0::/32 Valid Other origin only 97 15% 44
2402:5ec0:1f00::/40 Valid Other origin only 97 15% 44
2402:5ec0:1000::/40 Valid Other origin only 60 9%low visibility 33

AS-SET

AS55962'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 3 are in fix.csv.

  • Route object: none3
ChangePrefix or setDetailFull-table peers
Route object: none2402:5ec0::/32Route objects for it name AS23724. Add a route object with origin AS55962 in the RIR database for the space.97 of 636
Route object: none2402:5ec0:1f00::/40Route objects for it name AS23724. Add a route object with origin AS55962 in the RIR database for the space.97 of 636
Route object: none2402:5ec0:1000::/40Route objects for it name AS23724. Add a route object with origin AS55962 in the RIR database for the space.60 of 636

Route objects not announced

Every route object with origin AS55962 is announced.

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.