Summary

  • Noor Helmi, co-founder and chief executive of Malaysia-based connectivity provider IX Telecom, has argued in public remarks that telecommunications remains under-automated and that APIs and integration among operators, clouds and enterprise systems are the industry's way forward.
  • IX-API, the open interconnection API standard initiated by AMS-IX, DE-CIX and LINX, is a concrete test of that direction — but none of the public documents reviewed for this briefing names Helmi or IX Telecom as an adopter, implementer, partner or endorser, and the company's own materials do not name the standard.

The argument, and the company behind it

Noor Helmi has put a specific position into the public record: telecommunications remains under-automated, and APIs, together with tighter integration among operators, clouds and enterprise systems, are the industry's way forward (public remarks). He is the co-founder and chief executive of IX Telecom, a Malaysia-based enterprise connectivity provider. The company's own materials describe it as a global virtual network operator supplying managed connectivity, network operations centre support, cloud connectivity and XaaS, with coverage claimed in more than 200 countries — delivered through partner operators rather than owned infrastructure (company materials).

Two features of that description matter for the question that follows. The coverage figure is the company's own claim and is treated here as one. And the delivery model is coordination: the service depends on other operators' networks and on enterprise systems, the layer where interconnection automation is meant to operate.

The standard that matches the argument

The open standard matching that direction is IX-API, a common API standard for interconnection services initiated by AMS-IX, DE-CIX and LINX, with named implementation support from interconnection and data-centre providers including Interxion and Epsilon (standard materials). If interconnection is to become API-driven in the way Helmi describes, standards like IX-API are where that change becomes visible and checkable: an organisation either appears in an implementation or adoption record, or it does not.

Reading the adoption record

Read plainly, the record reviewed for this briefing is thin. Across the pages, announcements and directories inspected in September 2026, no document names Noor Helmi or IX Telecom as an IX-API adopter, implementer, partner or endorser (absence across the sources reviewed). The company's service and partnership materials describe managed connectivity, coverage and partnerships without naming IX-API or any open interconnection API standard (company materials reviewed).

That absence does not prove non-adoption, and this briefing does not report it as proof. Private integrations, unannounced pilots and procurement records would not appear in any of the sources reviewed. The narrower, defensible reading is that the adoption question stays open on the public record — and remains closeable in either direction by specific documents.

What would count as evidence either way

  • A named adopter or implementer listing in IX-API's own materials, or in the publications of the exchanges that initiated it: AMS-IX, DE-CIX or LINX.
  • A joint announcement, case study or implementation note naming IX Telecom alongside a technology or data-centre partner.
  • Public technical documentation from IX Telecom that names the standard or describes an interface conforming to it.
  • A governance, working-group or event record naming Helmi or a colleague as a participant in the standard's development.
  • In the other direction, an on-record statement that the company's interconnection integrations are proprietary, or a decision not to adopt.

Each item is a checkable artifact rather than an inference. What would not settle the question: chronology (the standard and the company simply coexist in time), advocacy (arguing for APIs is not adopting them), or absence (silence in the sources reviewed is a boundary of evidence, not proof of conduct).

The record that does exist

The university-linked public materials reviewed here place Helmi as a 2003 telecommunication-engineering graduate of Multimedia University in Malaysia who later served there as an adjunct professor and as a non-executive director; the same materials record an executive MBA (university-linked materials). They also recount, in his account, that the company's early operations were built from a university hostel room with fellow students — a story attributed to those materials and not independently verified here (university-linked materials).

Why the distinction is the story

A founder's public argument for API-driven interconnection is a statement of direction. It is not a record of conformance, and it should not be reported as one. A missing public record is not a finding of avoidance either, and it should not be reported as one. Between those two errors sits the question this briefing set out to test: whether the public record connects Noor Helmi and IX Telecom to the industry's open interconnection standard. In the documents reviewed, it does not — and the checks that would change that answer are named above.