bgpreport

Network · data from 2026-11-12

AS63540 SD-CLOUD - Shandong Cloud Comb Culture CO.LTD

Registry name: SD-CLOUD - Shandong Cloud Comb Culture CO.LTD, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63540, 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.
240a:41b8:8800::/40 Valid None 69 11% 34
240a:41b8:a000::/40 Valid None 69 11% 34
240a:41b8:d400::/40 Valid None 69 11% 34
240a:41b8:e400::/40 Valid None 69 11% 34
240a:4224:9000::/44 Valid None 69 11% 34
240a:4224:a000::/44 Valid None 69 11% 34
240a:4224:c000::/44 Valid None 69 11% 34
240a:4224:d000::/44 Valid None 69 11% 34
240a:4224:e000::/44 Valid None 69 11% 34
240a:4225:1000::/44 Valid None 69 11% 34
240a:4225:3000::/44 Valid None 69 11% 34
60.232.132.0/23 Valid None 57 8%low visibility 33
60.232.244.0/23 Valid None 57 8%low visibility 33

AS-SET

AS63540 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 13 are in fix.csv.

  • Route object: none13
ChangePrefix or setDetailFull-table peers
Route object: none240a:41b8:8800::/40No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:41b8:a000::/40No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:41b8:d400::/40No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:41b8:e400::/40No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:4224:9000::/44No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:4224:a000::/44No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:4224:c000::/44No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:4224:d000::/44No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:4224:e000::/44No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:4225:1000::/44No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none240a:4225:3000::/44No route object for it. Add a route object with origin AS63540 in the RIR database for the space.69 of 636
Route object: none60.232.132.0/23No route object for it. Add a route object with origin AS63540 in the RIR database for the space.57 of 673
Route object: none60.232.244.0/23No route object for it. Add a route object with origin AS63540 in the RIR database for the space.57 of 673

Route objects not announced

Every route object with origin AS63540 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.