bgpreport

Network · data from 2026-11-12

AS58593 BLUECLOUD - Shanghai Blue Cloud Technology Co.,Ltd

Registry name: BLUECLOUD - Shanghai Blue Cloud Technology Co.,Ltd, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58593, 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.
42.159.128.0/24 Valid Other IRR onlyRADB 673 100% 67
103.9.8.0/24 Valid Other IRR onlyRADB 673 100% 67
40.72.0.0/15 Valid Other IRR onlyRADB 672 100% 69
40.72.0.0/16 Valid Other IRR onlyRADB 672 100% 69
40.72.0.0/17 Valid Other IRR onlyRADB 672 100% 69
40.72.128.0/17 Valid Other IRR onlyRADB 672 100% 69
40.73.0.0/17 Valid Other IRR onlyRADB 672 100% 69
40.73.128.0/17 Valid Other IRR onlyRADB 672 100% 69
40.125.128.0/17 Valid Other IRR onlyRADB 672 100% 69
40.126.64.0/18 Valid Other IRR onlyRADB 672 100% 69
40.162.0.0/16 Valid Other IRR onlyRADB 672 100% 69
42.159.0.0/18 Valid Other IRR onlyRADB 672 100% 69
42.159.64.0/18 Valid Other IRR onlyRADB 672 100% 69
42.159.128.0/18 Valid Other IRR onlyRADB 672 100% 69
42.159.192.0/18 Valid Other IRR onlyRADB 672 100% 69
52.130.0.0/20 Valid Other IRR onlyRADB 672 100% 69
52.130.32.0/19 Valid Other IRR onlyRADB 672 100% 69
52.130.96.0/20 Valid Other IRR onlyRADB 672 100% 69
52.130.112.0/20 Valid Other IRR onlyRADB 672 100% 69
52.130.128.0/18 Valid Other IRR onlyRADB 672 100% 69
52.130.192.0/18 Valid Other IRR onlyRADB 672 100% 69
52.131.0.0/17 Valid Other IRR onlyRADB 672 100% 69
52.131.128.0/17 Valid Other IRR onlyRADB 672 100% 69
103.9.8.0/23 Valid Other IRR onlyRADB 672 100% 69
139.217.0.0/17 Valid Other IRR onlyRADB 672 100% 69
139.217.128.0/17 Valid Other IRR onlyRADB 672 100% 69
139.219.0.0/17 Valid Other IRR onlyRADB 672 100% 69
139.219.128.0/17 Valid Other IRR onlyRADB 672 100% 69
143.64.0.0/16 Valid Other IRR onlyRADB 672 100% 69
159.27.0.0/16 Valid Other IRR onlyRADB 672 100% 69
163.228.0.0/16 Valid Other IRR onlyRADB 672 100% 69
52.130.16.0/20 Valid Other IRR onlyRADB 670 100% 69
52.130.64.0/19 Valid Other IRR onlyRADB 669 99% 69
2406:e500::/48 Valid Other IRR onlyRADB 636 100% 68
2404:7940::/32 Valid Other IRR onlyRADB 635 100% 69
2406:e500::/33 Valid Other IRR onlyRADB 635 100% 69
2406:e500:1::/48 Valid Other IRR onlyRADB 635 100% 69
42.159.0.0/16 Valid RIR databaseAPNIC, RADB 672 100% 69
103.9.8.0/22 Valid RIR databaseAPNIC, RADB 672 100% 69
139.217.0.0/16 Valid RIR databaseAPNIC, RADB 672 100% 69
139.219.0.0/16 Valid RIR databaseAPNIC, RADB 672 100% 69

AS-SET

AS58593 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 44 are in fix.csv.

  • Route object: RIR37
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: RIR42.159.128.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.9.8.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR40.72.0.0/15Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR40.72.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR40.72.0.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR40.72.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR40.73.0.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR40.73.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR40.125.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR40.126.64.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR40.162.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR42.159.0.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR42.159.64.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR42.159.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR42.159.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.130.0.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.130.32.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.130.96.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.130.112.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.130.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.130.192.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.131.0.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.131.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.9.8.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.217.0.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.217.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.219.0.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR139.219.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.64.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR159.27.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR163.228.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.130.16.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR52.130.64.0/19Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2406:e500::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2404:7940::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2406:e500::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2406:e500:1::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS58593 whose prefix no peer sees AS58593 announce. Many are kept on purpose (backup routes, space announced only in some places).

40.72.254.0/24RADBValid
40.72.255.0/24RADBValid
40.73.3.0/24RADBValid
40.73.65.0/24RADBValid
103.9.10.0/24RADBValid
139.217.98.0/24RADBValid
139.217.220.0/24RADBValid

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.