Summary

  • LACNIC's dated 3 November transfer file has 39 disjoint 2026 IPv4 transfer sets wholly inside 186.196.0.0/16 with the source written TIM S.A. or TIM SA. They total 36,608 addresses and name 23 distinct recipient strings. The file supplies no shared legal-entity identifier for the two source spellings.
  • Twenty-seven of the 39 rows are /24s: 69% of the paperwork, only 6,912 addresses or 19% of the transferred total. One /19 alone carries 8,192. Current exact RDAP still names TIM S/A on the adjacent 186.196.15.0/24 gap.

A transfer ledger can make a sale look like a crowd scene. Count the lines and the TIM-labelled portion of 186.196.0.0/16 looks like a market of tiny pieces. Count the addresses and a few large blocks take over the stage. LACNIC publishes both the evidence and the trap: the transfer set is the thing that moved; its original_set may be much wider. Confuse those columns and the story becomes an accounting error with a headline.

The latest dated LACNIC transfer original contains 39 2026 rows whose transferred IPv4 ranges sit wholly within the mathematical /16 and whose source field reads exactly TIM S.A. in 35 rows or TIM SA in four. These 39 ranges do not overlap. Together they span 36,608 addresses, or 55.86% of the /16's 65,536 addresses. The first selected transfer was on 18 May; the last on 29 October. The recipient column has 23 different literal names. Those are counts of records and strings, not a finding that 23 networks changed their routing on those dates.

The distribution is the punchline. Twenty-seven /24 transfers occupy more than two-thirds of the rows yet move 6,912 addresses, 18.88% of the selected total. Seven /22s move 7,168. Three /20s move 12,288. One /21 adds 2,048, and the lone /19 adds 8,192. The four /20-or-larger rows therefore carry 20,480 addresses, almost 56% of what all 39 rows carry. A board presentation that says “27 small transfers” tells one true story; an address-weighted chart tells another.

The biggest single receipt is 186.196.128.0/19, sent to IP AMERICA TELECOM LTDA. on 8 September. It holds 8,192 addresses, more than all 27 /24s combined. Exact current RDAP names IP AMERICA and gives an 8 September last-changed event. At the other end, DIMENOC received ten /24s on 18 May and five more on 22 July, then a /20 on 25 August: 16 separate rows and 7,936 addresses in this /16. The exact .0/24 object names DIMENOC SERVICOS DE INFORMATICA LTDA, a different spelling from the transfer file's DIMENOC SOLUCOES DE INFORMATICA LTDA. The block is exact; the string is not stable enough to serve as a legal identity key by itself.

At the newest edge of the sequence, 186.196.16.0/21 moved to INTERFIBRAS TELECOMUNICACOES LTDA on 29 October. Its exact RDAP now names that recipient and dates its last change to 29 October. The adjacent 186.196.15.0/24 is the useful counterweight. There is no selected 2026 transfer set for it; its current exact RDAP names TIM S/A. One map can have new owners on either side of a retained-looking square. The record does not tell an editor to paint the whole remaining 28,928 addresses in TIM's colour.

There is a second naming wrinkle. One of the four TIM SA rows sends 186.196.209.0/24 to I3 TELECOMUNICACOES LTDA on 11 September. Current RDAP calls the registrant I3 Telecomunicacoes - EIRELI. The sources identify exact address intervals and dated administrative changes; they do not carry a common transaction ID or a complete corporate identity history. An operator's contract and routing change log would settle whether any particular recipient string corresponds to an independent commercial deal or network cutover.

This is why the registry's mundane-looking columns matter. A /16 is an arithmetic frame, not a single transferable asset in this file. Thirty-nine rows are thirty-nine administrative receipts, not thirty-nine equal amounts of IPv4. The /24s give the ledger its busy appearance; the /19 and /20s give it most of its weight. If a regulator, buyer or member wants to measure concentration, counting receipts is the wrong unit. If they want to inspect operational transition, even the address count is only the start: they need the exact registration and routing evidence for the ranges that moved.

LACNIC originals