Summary

  • Ordos UniCloud Technology Company Limited holds two APNIC autonomous systems, AS131311 and AS131335, both named UniCloud-IDC and both allocated in June 2011; neither has ever announced an IPv4 or IPv6 prefix, and both objects were last modified in a near-simultaneous batch edit on 5 September 2023.
  • The registry contact handles for both objects carry @zte.com.cn e-mail addresses, and one aggregator lists zte.com.cn as the organisation's website — evidence pointing to ZTE-linked administration rather than an independent Ordos operator.
  • Uptime Institute's awards list names "Ordos UniCloud Tech. Co., Ltd." as the client for a single project, "Tower 1A of UniCloud Ordos DC" in Ordos, China; the excerpt available publicly does not show the award type or year.
  • The aggregator Coloprice describes Tower 1A as operational and Uptime Tier III design-certified, but attributes the operator to Tsinghua Unigroup's 紫光云 (UniCloud) cloud business — an unsourced claim in tension with the ZTE registry contacts and with 紫光云's own site, whose listed data-center nodes do not include Ordos.
  • The ownership question — 紫光云 lineage versus ZTE lineage — cannot be resolved from the present public record; this article attributes every conflicting claim rather than harmonizing it.

A name in three databases

Start with the network layer. The APNIC registry, as republished by mirrors and ASN profiling services, attributes two autonomous systems to Ordos UniCloud Technology Company Limited. AS131335 carries the as-name "UniCloud-IDC" with the description "Ordos UniCloud Technology Company Limited" and the address "14F, Tower B, Wanzheng Plaza, Dongsheng District, Ordos 071000, PRC"; the organisational object is ORG-OUTC1-AP and the sponsoring organisation is ORG-BCTC1-AP (1, 2). AS131311 shows the same as-name, the same organisation, the same Ordos address, the same org object and the same sponsoring organisation (3, 4). IPinfo reports both allocations dated June 2011 — 1 June for AS131311 and 24 June for AS131335 — with a last update of 5 September 2023 on each (2, 3).

Then the routing layer, which is where the record turns strange. Every routing observatory consulted reports the same zeros. IPinfo flags both ASNs as "Inactive" with no routed prefixes (2, 3). TheIpAPI's records show zero IPv4 prefixes and zero IPv6 prefixes for both ASNs (6, 7). Qrator Labs' radar — an independent BGP monitoring vantage — reports zero prefixes announced, zero visibility, and zero RPKI or route objects for AS131335 (8). The IP.CC ASN page likewise reports no announced prefixes, no peers, no upstreams and no downstreams (1). A network that was registered in 2011 and has never carried traffic is not a network operator; it is a registration.

The maintenance pattern reinforces that reading. Both aut-num objects were last modified on 5 September 2023, within four seconds of each other — 03:51:06Z for AS131311 and 03:51:10Z for AS131335 (1, 4). A near-simultaneous batch edit to two twelve-year-old, never-routing registrations is the signature of administrative housekeeping — a sponsor organisation touching up stale objects — not of new operations coming online. Twelve years of dormancy followed by a synchronised registry touch-up is a very specific kind of institutional persistence: the objects matter to somebody enough to maintain, but not enough to use.

Who answers for these networks

Registry contact fields are where corporate structure leaks into public view. For both ASNs, the administrative contact handle MC1465-AP belongs to a person named Ming Cui and the technical contact handle YH1667-AP to Yupeng Hu — and both carry @zte.com.cn e-mail addresses, with a postal address at 14F, Tower B, Wanzheng Plaza, Dongsheng District, Ordos (4, 5). The person objects themselves were last modified on 21 December 2016 (4). One aggregator, IPGeolocation, records zte.com.cn as the organisation's website for AS131311 (5). The Abuse/IRT role for AS131311 resolves not to Ordos UniCloud at all but to an address in Haidian, Beijing, at an address under the cnispgroup.com domain — with remarks noting that address was validated on 8 December 2025 (5).

Read together, these fields sketch an administration chain that runs through ZTE's domain and, for abuse handling, through a Beijing network-services group — not through a standalone Ordos company. A registry contact e-mail is not a corporate ownership document: people listed under a ZTE domain could have been seconded, contracted, or simply using employer addresses when the objects were created in 2011 and last touched by humans in 2016. But it is public, verifiable evidence, and it points in one direction. Any attribution of this organisation to a different corporate family has to explain it.

The certified tower

The third layer is facilities. Uptime Institute's own published awards database names a client called "Ordos UniCloud Tech. Co., Ltd." — a shortened form of the registry organisation — with exactly one project listed: "Tower 1A of UniCloud Ordos DC", located in Ordos, China (9). The client-side mirror of the same database confirms the same single-project footprint (10). What the publicly visible excerpts do not show is the award type or the year; any statement beyond "a Uptime Institute award action exists for this client and project" would overreach the evidence. Two important caveats apply here: the certification date cannot be stated, and the shortened client name, while plainly resembling the registry organisation, is an identity match made by pattern rather than by a corporate document.

The aggregator Coloprice fills in more detail and less reliability. Its entry describes Tower 1A of UniCloud Ordos DC as an operational data center in Ordos, Uptime Tier III design-certified, air-cooled, with power capacity listed as unknown, and scores it 23/100 (Class E, 43rd of 184 facilities in China) with zero compliance, transparency and scale sub-scores (11) — the entry whose underlying record is also mirrored in catalogue form (12), and whose CSV listing cites "Uptime Institute Tier III Certification of Design Documents" (11). Tier III design certification is a design-stage award, not a construction or operational one; "design certified" is the strongest claim the record supports without the award date.

The ownership conflict nobody can resolve

Here the record breaks. Coloprice states that the operator of Tower 1A is "a project company of Tsinghua Unigroup's UniCloud (紫光云) commercial IDC and cloud-hosting business" (11). No source for that attribution is visible on the page. Against it stand two facts from independent layers: the APNIC registry contacts for the organisation of the same name carry ZTE-domain addresses (4, 5), and 紫光云's own corporate site — whose about page describes the company (13) — lists data-center nodes that do not include Ordos (13). A cloud company's own facility list omitting the very city its supposed project company certified a tower in is not proof of absence — companies leave facilities off marketing pages — but it is a pointed silence.

The honest summary is that the present public record contains two irreconcilable attributions and no primary document that adjudicates between them. The ZTE-side evidence is registry-sourced and verifiable field by field. The 紫光云-side evidence is a single aggregator sentence with no citation. The name "UniCloud" itself is no help: 紫光云 operates internationally under the UniCloud brand, and a project company named after that brand could plausibly have been named at founding, renamed, or coincidentally similar. Brand-name similarity is not evidence of ownership in either direction.

What the record does and does not establish

Stripped of attribution, here is what public sources establish about Ordos UniCloud Technology Company Limited as of 28 September 2026. It exists as a named organisation in the APNIC registry, holding two autonomous systems allocated in June 2011, both named UniCloud-IDC, both carrying an Ordos street address, both never having announced a route, both last modified in a batch edit on 5 September 2023 (1, 2, 3, 4). Its registry contact persons use ZTE-domain e-mail addresses, its abuse role is delegated to a Beijing services group whose address was revalidated in December 2025, and one aggregator records ZTE's website as the organisation's own (5, 6, 7, 8). A name matching the organisation appears once in Uptime Institute's awards database, as the client for Tower 1A of UniCloud Ordos DC in Ordos (9, 10); aggregator entries describe that tower as operational and Tier III design-certified (11, 12). 紫光云's own site lists 19 data-center nodes, none in Ordos (13).

What no public source establishes: the year or type of the Uptime award; the facility's actual power capacity; whether the certified tower was built by the ZTE-linked administration, by 紫光云, or by some other entity entirely; whether the dormant ASNs were ever intended for a data-center interconnect that never came into being; and whether the company is solvent, active, or a shell. Corporate registration documents for Ordos UniCloud Technology Company Limited — the layer that would adjudicate the ownership conflict — are not among the sources inspected for this article.

One further caution. Third-party ASN profiles are mirrors and aggregates of registry data, not the registry itself; this article's registry facts are drawn from mirrors (1, 4) rather than a live APNIC whois query. Aggregator timestamps can also mislead: one record shows "Created 2023-09-06", which is an object-timestamp artefact of the aggregator's own database, not a corporate founding date (6).