bgpreport

Network · data from 2026-11-12

AS59048 CLOUDTIMES - Bei Jing Cloud Times Technology Co.,Ltd

Registry name: CLOUDTIMES - Bei Jing Cloud Times Technology Co.,Ltd, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59048, 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.
43.224.56.0/23 Valid None 5 1%low visibility 6
43.224.56.0/24 Valid None 5 1%low visibility 6
103.224.228.0/22 Valid None 5 1%low visibility 6
103.255.200.0/24 Valid None 5 1%low visibility 6
103.255.201.0/24 Valid None 5 1%low visibility 6
103.255.202.0/24 Valid None 5 1%low visibility 6
103.255.203.0/24 Valid None 5 1%low visibility 6
103.222.43.0/24 Valid None 1 0%low visibility 3
103.192.212.0/24 Valid Other IRR onlyRADB 5 1%low visibility 6
103.192.214.0/24 Valid Other IRR onlyRADB 5 1%low visibility 6

AS-SET

AS59048 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: none8
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none43.224.56.0/23No route object for it. Add a route object with origin AS59048 in the RIR database for the space.5 of 673
Route object: none43.224.56.0/24No route object for it. Add a route object with origin AS59048 in the RIR database for the space.5 of 673
Route object: none103.224.228.0/22No route object for it. Add a route object with origin AS59048 in the RIR database for the space.5 of 673
Route object: none103.255.200.0/24No route object for it. Add a route object with origin AS59048 in the RIR database for the space.5 of 673
Route object: none103.255.201.0/24No route object for it. Add a route object with origin AS59048 in the RIR database for the space.5 of 673
Route object: none103.255.202.0/24No route object for it. Add a route object with origin AS59048 in the RIR database for the space.5 of 673
Route object: none103.255.203.0/24No route object for it. Add a route object with origin AS59048 in the RIR database for the space.5 of 673
Route object: none103.222.43.0/24No route object for it. Add a route object with origin AS59048 in the RIR database for the space.1 of 673
Route object: RIR103.192.212.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR103.192.214.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

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

103.192.215.0/24RADBValid
103.222.32.0/24RADBValid
2401:a140:2::/48RADBNo 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.