Summary
- IMCLOUD TECHNOLOGY COMPANY LIMITED is a Hong Kong-registered APNIC member holding AS135314, with an ASSIGNED PORTABLE /22 at 103.214.16.0/22 and additional associated ranges; the BGP footprint is modest, with CIDR Report showing roughly 3,328 originated IPv4 addresses and no transit space.
- Operational evidence points to Taiwan: upstreams and route maintenance via Sky Digital Co., Ltd. (AS134823), a geofeed under telecom.tw, Taipei geolocation, and a shared idc-tw.com domain with a separately registered Taiwan entity, Imcloud Technology Co., Ltd. (AS131151, TWNIC).
- Public records do not establish whether the Hong Kong and Taiwan 'Imcloud' registrations are one corporate group; the routing evidence contradicts any reading of the address space as dormant.
The registry record and the routing record tell different stories about the same company, and neither story is complete on its own. The APNIC whois database lists AS135314 under the as-name IMCLOUD-AS-AP with the description IMCLOUD TECHNOLOGY COMPANY LIMITED, registered to Hong Kong, organisation handle ORG-ITCL1-AP, and with route maintenance delegated to MAINT-IMCLOUD-HK; the object was last modified on 2020-11-03 (APNIC whois). The autonomous system number itself was allocated on 2016-04-06 according to aggregator snapshots of APNIC data (IPGeolocation.io). On its face, this is an unremarkable entry: one more Hong Kong entity in the APNIC region with an ASN and a modest block of address space.
The address portfolio is likewise small and specific. APNIC whois, read through a third-party mirror, lists the inetnum 103.214.16.0 through 103.214.19.255 — a /22 containing 1,024 addresses — under the netname IMCLOUD-HK, status ASSIGNED PORTABLE, same organisation handle, and last modified 2026-02-06. Notably, that object carries a geofeed URL hosted under the domain telecom.tw (whois record). A geofeed is the operator's own machine-readable statement of where its address space physically sits. In this case, the operator's own declaration ties the Hong Kong-registered space to Taiwan-side infrastructure.
What the company does with the space is visible, at a point-in-time level, in routing data. CIDR Report's snapshot of AS135314 shows an origin-only operator: approximately 3,328 IPv4 addresses originated, zero transit address space, with an upstream adjacency reported through AS134823, which belongs to Sky Digital Co., Ltd. in Taiwan. Sample AS paths observed at the collection point include 2497 3462 134823 135314 for 103.214.16.0/23 and 7018 3491 134823 135314 for 103.214.16.0/24, indicating that the prefixes are actively announced into the global routing table (CIDR Report). This matters because it contradicts the common pattern in which small registrants hold allocations without ever routing them; here, the prefixes are live.
The route-object layer adds a wrinkle. A RADB route object for 103.214.16.0/22 originates AS135314, described as 'Customer Route - LOA provided', and is maintained not by MAINT-IMCLOUD-HK but by MAINT-AS134823, the maintainer of the Taiwan upstream. The object was last modified 2026-01-16 and carries an RPKI origin-validation state of 'valid' (RADB record via Robtex). Read together with the AS paths in the CIDR Report data, the picture is of an operator whose announcements are handled through its upstream's infrastructure: IMCLOUD owns the space and the origin ASN, while Sky Digital's maintainer object vouches for the routes. There is a plausible commercial explanation — a transit customer whose provider manages route objects on its behalf — but the LOA ('letter of authorization') note confirms that a third party was authorised to advertise IMCLOUD's space, which is a dependency worth noting for anyone evaluating the network's continuity.
Beyond the /22, aggregators associate further ranges with AS135314: 144.48.32.0/23, 144.48.33.0/24 and an egress range at 154.18.168.0/24 (IPGeolocation.io, IPinfo). IPinfo geolocates one address in that footprint, 144.48.33.193, to Taipei, Taiwan, and classifies the ASN type as 'hosting' — but reports zero hosted domains on that address (IPinfo). That combination is the quiet core of this story: infrastructure classified as hosting, with no observed customer domains riding on it. Hosting classification describes how the space is used at the routing level; zero hosted domains suggests either that the space serves infrastructure without publishing customer web properties, that usage is internal or transit-like, or that aggregation has not yet observed the tenants. The data does not distinguish between those possibilities.
The identity question then widens. A separately registered entity, Imcloud Technology Co., Ltd., operates AS131151 with a TWNIC-registered range at 187.79.248.0/21 in Taiwan, and IPinfo associates it with the same idc-tw.com domain that appears in IMCLOUD's Hong Kong-side records (IPinfo). The APNIC registration for the Hong Kong entity likewise lists an abuse mailbox at that domain (APNIC whois). Two registries, two ASNs, one shared domain, one shared name: the public record does not establish whether these are one corporate group operating across two registries, or two related but distinct entities. Hong Kong company registration and Taiwan company registration are separate legal universes, and neither whois system records corporate parentage.
Not every aggregator agrees on the basics, which is itself instructive. WHOER's page for AS135314 reports IPv4 prefix counts in the thousands (1,474), figures irreconcilable with APNIC whois, which lists a single ASSIGNED PORTABLE /22 at 103.214.16.0, and with IPGeolocation.io's count of nine IPv4 routes (WHOER, IPGeolocation.io). Where sources conflict, this article follows the primary registry records and treats aggregator counts as unreliable snapshots. One page does correctly place 154.18.168.0/24 with AS135314 (IPinfo), though other IPinfo pages associate the same range with the Taiwan-registered AS131151, an ambiguity the aggregators themselves have not resolved.
What can be said with confidence is bounded but real. IMCLOUD TECHNOLOGY COMPANY LIMITED holds an APNIC-registered ASN and a portable /22 that have been modified as recently as February 2026 (whois record). The space is announced, RPKI-valid, and upstreamed through a Taiwan provider (CIDR Report, Robtex). The operator's own geofeed places the addresses in Taiwan (whois record). The organisation behind the ASN presents itself to the internet through Taiwan infrastructure and a Taiwan-facing domain, while its registration paperwork says Hong Kong. For a company with 'cloud' in its name, the visible footprint is small — a few thousand originated addresses, no IPv6, no observed hosted domains — closer to a niche hosting or network-services operation than to a cloud platform at scale.
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance
