Summary

  • Sixteen exact date-and-address matches between LACNIC and RIPE NCC's official outgoing transfer files carry NL in LACNIC's source-organization country field and ES in RIPE's from-country field.
  • The matched rows span 10,240 IPv4 addresses; the two newest, both on 27 October, are 2.152.46.0/24 and 2.152.250.0/24.

One address range, two country labels. The LACNIC transfer export lists Vodafone ONO, S.A. as the source of 2.152.46.0/24 on 27 October, moving from RIPE to LACNIC for a recipient in Peru. Its source_organization.country_code is NL. The RIPE NCC outgoing file gives the same date, block and source name, but from_country_code is ES. On that day 2.152.250.0/24 went to an Ecuadorian recipient and repeats the split. The destination changes; the source-country discrepancy does not.

This is a pattern rather than one strange row. Matching the two files on organization name, destination RIR, date and exact IPv4 start and end yields 16 LACNIC entries from 6 July through 27 October. They total 10,240 addresses and reach recipients in eight country-code jurisdictions. All sixteen pair NL with ES. Two further LACNIC Vodafone ONO ranges have a 27 August date while RIPE dates their matching ranges 24 August. They sit outside this strict same-date count.

RIPE's field definitions call “From Country Code” the country where the original holder was legally registered when the transfer was processed. LACNIC's JSON names a source-organization country field but supplies no comparable explanation of why it says NL. The files establish the conflicting published values. A LACNIC field-definition note or record correction would tell readers whether they reflect different rules or a mistake.