bgpreport

Network · data from 2026-11-12

AS135314 IMCLOUD-AS-AP - IMCLOUD TECHNOLOGY COMPANY LIMITED

Registry name: IMCLOUD-AS-AP - IMCLOUD TECHNOLOGY COMPANY LIMITED, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135314, 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.
154.18.168.0/24 No ROA Other IRR onlyRADB 60 9%low visibility 32
103.214.18.0/23 Valid RIR databaseAPNIC 670 100% 67
144.48.32.0/23 Valid RIR databaseAPNIC 670 100% 67
103.214.16.0/24 Valid RIR databaseAPNIC 390 58% 65
103.214.18.0/24 Valid RIR databaseAPNIC 261 39% 60
103.214.19.0/24 Valid RIR databaseAPNIC 261 39% 60
144.48.32.0/24 Valid RIR databaseAPNIC 261 39% 60
144.48.33.0/24 Valid RIR databaseAPNIC 261 39% 60
103.214.17.0/24 Valid RIR databaseAPNIC 79 12% 42
103.214.16.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none154.18.168.0/24No ROA covers it. Add a ROA for AS135314, maxLength 24.60 of 673
Route object: RIR154.18.168.0/24Route object only in RADB. Add it in the RIR database for the space.60 of 673

Route objects not announced

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

103.214.16.0/22APNIC, RADBValid
144.48.32.0/22APNIC, RADBValid
144.48.34.0/23APNICValid
144.48.34.0/24APNICValid
144.48.35.0/24APNIC, NTTCOM, RADBValid

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.