bgpreport

Network · data from 2026-11-12

AS152644 QINIU (CHINA) limited, QINIU (CHINA) limited

Registry name: QINIU-AS-AP - QINIU Limited, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS152644, 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.
38.123.103.0/24 No ROA Other IRR onlyRADB 672 100% 67
154.41.93.0/24 No ROA Other IRR onlyRADB 670 100% 67
204.141.218.0/24 Valid None 673 100% 67
2001:418:149b::/48 Valid None 635 100% 67
204.141.229.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
2001:418:149c::/48 Valid Other IRR onlyNTTCOM 636 100% 67
202.47.135.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.47.134.0/24 Valid RIR databaseAPNIC, RADB 667 99% 67
154.3.169.0/24 Valid RIR databaseARIN 348 52% 62

AS-SET

AS152644'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 40 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none38.123.103.0/24No ROA covers it. Add a ROA for AS152644, maxLength 24.672 of 673
Route object: RIR38.123.103.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.41.93.0/24No ROA covers it. Add a ROA for AS152644, maxLength 24.670 of 673
Route object: RIR154.41.93.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none204.141.218.0/24No route object for it. Add a route object with origin AS152644 in the RIR database for the space.673 of 673
Route object: none2001:418:149b::/48No route object for it. Add a route object with origin AS152644 in the RIR database for the space.635 of 636
Route object: RIR204.141.229.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR2001:418:149c::/48Route object only in NTTCOM. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

38.99.243.0/24ARINValid
2401:89a0::/32APNICValid
2401:89a0::/33APNICValid
2401:89a0::/34APNICValid
2401:89a0::/35APNICValid
2401:89a0::/36APNICValid
2401:89a0:1000::/36APNICValid
2401:89a0:2000::/35APNICValid
2401:89a0:2000::/36APNICValid
2401:89a0:3000::/36APNICValid
2401:89a0:4000::/34APNICValid
2401:89a0:4000::/35APNICValid
2401:89a0:4000::/36APNICValid
2401:89a0:5000::/36APNICValid
2401:89a0:6000::/35APNICValid
2401:89a0:6000::/36APNICValid
2401:89a0:7000::/36APNICValid
2401:89a0:8000::/33APNICValid
2401:89a0:8000::/34APNICValid
2401:89a0:8000::/35APNICValid
2401:89a0:8000::/36APNICValid
2401:89a0:9000::/36APNICValid
2401:89a0:a000::/35APNICValid
2401:89a0:a000::/36APNICValid
2401:89a0:b000::/36APNICValid
2401:89a0:c000::/34APNICValid
2401:89a0:c000::/35APNICValid
2401:89a0:c000::/36APNICValid
2401:89a0:d000::/36APNICValid
2401:89a0:e000::/35APNICValid
2401:89a0:e000::/36APNICValid
2401:89a0:f000::/36APNICValid

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.