Two LACNIC /20 transfers to Mexican holders

Two /20s, Two Mexican Holders, 114 Days. LACNIC Has Separate Receipts.

Why it matters

The Venezuelan-registered holder transferred equal IPv4 blocks to INBTEL SA DE CV and DIGY NETWORKS 114 days apart. One current RDAP object names an origin ASN; the other leaves that field empty.

Theo March2 November 2026Reading Time 2 minLast update: 2 November 2026

LACNIC records separate full /20 transfers from one source organization to two recipients on 7 July and 29 October 2026.

Summary

LACNIC records 190.103.32.0/20 moving from SUPERCABLE ALK INTERNATIONAL, S.A. to INBTEL SA DE CV on 7 July 2026 and 200.35.240.0/20 moving to DIGY NETWORKS on 29 October.
The two whole blocks contain 4,096 addresses each. Current LACNIC RDAP names the two recipients separately and shows AS265586 as an origin ASN for INBTEL SA DE CV’s block, while DIGY NETWORKS’s corresponding field is empty.

A second receipt appeared on 29 October. The LACNIC transfer file puts SUPERCABLE ALK INTERNATIONAL, S.A. on the source side of 200.35.240.0/20 and DIGY NETWORKS on the recipient side. The same source appears in a 7 July entry for 190.103.32.0/20, whose recipient is INBTEL SA DE CV. Both entries carry VE for the source organization and MX for the recipient. The dates are 114 calendar days apart.

Each transfer covers its entire original /20. The July range runs from 190.103.32.0 through 190.103.47.255; the October range from 200.35.240.0 through 200.35.255.255. That is 4,096 IPv4 addresses per record and 8,192 across the pair. These are separate ranges, not the two halves of a larger contiguous block. No ASN or IPv6 resource is listed in either transfer row.

The registry’s current INBTEL SA DE CV RDAP object registers the July /20 to INBTEL SA DE CV with a 7 July event and lists AS265586 in lacnic_originAutnum. The DIGY NETWORKS object registers the October /20 to DIGY NETWORKS with a 29 October event; its lacnic_originAutnum array is empty. A route or ROA record would establish present announcement or authorization for either prefix. The transfer log gives no price, common contract identifier or reason tying the two receipts together.