Summary

  • Five LACNIC aut-num objects covering Mexico, Argentina and Peru print five different registrant strings, and none of them is América Móvil, S.A.B. de C.V.
  • The only in-register evidence that the two Argentine objects answer to one administration is a shared three-handle contact set, and one holder name does not even match its own issuer's filed spelling.

Ask a registry who holds a network and it will answer with a name that is legally exact and commercially useless. This is not a fault. It is what a register of holders is for. The interesting part is what happens when someone tries to reassemble a group out of those answers.

LACNIC's RDAP service, queried directly on 20 November 2026, returns five separate objects for five autonomous systems long associated with the group's operating brands in Mexico, Argentina and Peru. Each is a DIRECT ALLOCATION, and each is active. That is where the uniformity ends.

Five objects, five names

Mexico's wireless side sits under a name that contains neither the retail brand nor the parent. AS28403 is held by RadioMovil Dipsa, S.A. de C.V., entity handle MX-RDSA-LACNIC, registered 26 November 2013 and last changed 2 September 2024 — https://rdap.lacnic.net/rdap/autnum/28403. The record's own registrant address is at Edif. Telcel, Lago Zurich, in Miguel Hidalgo: the building is named, the group is not.

Argentina is where a brand search gives up entirely. AS11664 is held by Techtel LMDS Comunicaciones Interactivas S.A. under handle AR-TLCI-LACNIC, registered 9 November 1998 and last changed 8 June 2022, with a Buenos Aires address — https://rdap.lacnic.net/rdap/autnum/11664. AS19037 is held by AMX Argentina S.A. under handle AR-CCTI1-LACNIC, registered 10 November 2000 and last changed 16 March 2021, on an address in Capital Federal — https://rdap.lacnic.net/rdap/autnum/19037. Neither string contains the Claro brand. Neither contains América Móvil.

Mexico's fixed side adds a third name, and the oldest allocation of the five. AS8151 belongs to Uninet S.A. de C.V., entity handle MX-USCV4-LACNIC, registered 29 April 1997 — https://rdap.lacnic.net/rdap/autnum/8151.

Peru is the one place where the group's own words survive, and they survive only as a national company. AS12252 is held by America Movil Peru S.A.C., handle PE-TPSA4-LACNIC, registered 17 November 2000 and last changed 15 April 2025, on an address in La Victoria, Lima — https://rdap.lacnic.net/rdap/autnum/12252. Five objects, five registrant strings, one parent named nowhere.

A register is a photograph of a form

The holder string is not a summary of who runs a network. It is a self-reported name attached to an entity object, and that entity object moves on its own schedule. AS8151 shows the seam clearly: the aut-num record last changed on 28 September 2021, while the registrant entity record embedded in the same response last changed on 31 July 2026. Five years apart inside one record. The legal-representative field on that object reads, in the registry's own words, "No hay informacion".

None of this makes any entry wrong. It makes each entry a statement about a form at a moment, and it means the holder string cannot carry a question it was never designed to answer.

What actually links the Argentine pair

Inside the register, the evidence of common administration is not the name. It is the handles. AS11664 and AS19037 carry the identical administrative handle ADL82, the identical technical handle SAD3 and the identical abuse handle CAT66. Two different companies on paper, one administrative team in the record. AS11664 pushes the point further: its legal-representative field reads "Administrador de Direcciones IP - CLARO".

The other three objects each carry a single handle covering the administrative, technical and abuse roles: OSH6 on AS28403, GEC10 on AS8151, CLL68 on AS12252. Three objects, three different names, three different contacts. If the Argentine pair is the case where the register quietly admits a shared back office, the other three are the case where it does not.

The one document that names the parent

The only document in this set that joins any of these names to a single owner is the parent's own filing. An exhibit to an América Móvil registration statement, titled as a list of certain subsidiaries as of 31 March 2023, carries a row for "Radiomóvil Dipsa, S.A. de C.V. (Telcel)" recording Mexico, an ownership interest of 100.0 and a main activity of Wireless — https://www.sec.gov/Archives/edgar/data/1129137/000119312523129777/d464232dex81.htm. The same table as read also sets out Claro NXT Telecomunicações S.A. and América Móvil Perú, S.A.C.

That exhibit is framed as certain subsidiaries, and it is dated. Absence from it proves nothing about ownership. What it does prove is direction: the corporate mapping runs from the group outward to the operating companies, and the register never runs it back.

The join that fails on one character

Now put the two halves together. The exhibit prints the Mexican holder as Radiomóvil Dipsa, with an accent on the first o. The RDAP object prints RadioMovil Dipsa, without one. An exact-string join between the issuer's own subsidiary list and the registry of record fails on a diacritic — on the single most important entity in the set, the one the filing explicitly labels Telcel and marks 100 per cent owned.

That is the finding, and it is bigger than a typo. Anyone reconciling a group's network assets by name will match the Peruvian object, because the group's name is inside it. They will miss the Mexican wireless object on one character, the Mexican fixed object entirely, and both Argentine objects entirely, since neither of those strings resembles the brand or the parent. Four of five missed, and no error message anywhere.

What this is not

It is not evidence that the group has no resources registered in its own name. This piece read five objects, not a register-wide search, and it makes no claim about any registration outside those five or outside LACNIC.

It is not evidence of a corporate renaming, merger, sale or transfer. No document read here records one behind Techtel LMDS, AMX Argentina or Uninet, and the register would not say so if it did — it holds names, not histories.

What it is, is a working instruction. A group's network footprint in a registry is assembled from handles, entity records and the issuer's own filed lists, reconciled deliberately, with the spelling hazards treated as first-class. The holder string is where the search starts. It is never where the answer ends — https://btw.media/en/directory/am-rica-m-vil-s-a-b-de-c-v.