Summary

  • LACNIC defines created as the date on which the record for an address block was created; changed separately dates a modification to that record.
  • The field establishes registry chronology, not corporate, contractual, operational or routing chronology.

A precise date for a narrow event

LACNIC’s published database format gives created a literal meaning: it is the date the block record was made. The same description assigns later modification to changed. That distinction makes the field useful for audit work. It can show that a particular registry object existed by a particular time and help analysts order later edits.

The precision must not widen the claim. A record can be created after an organisation has operated for years, after a network has already used other resources, or as part of an administrative migration. Conversely, creating a record does not prove that routers accepted a configuration, users received service, contracts transferred, or packets crossed the network that day.

One response, several clocks

The current LACNIC RDAP response for 45.6.248.0/22 makes the separation visible. Its IP-network object carries a registration event at 2017-04-27T17:53:25Z. The response separately exposes the address boundaries, an active status, registrant and contact entities, a parent handle, origin-AS metadata and reverse-delegation checks.

Those fields are not interchangeable. The registration event dates the object. A status is a registry classification. An origin-AS value is declared metadata. A delegation check is a DNS observation at another time. None of them is a route-collector record, router configuration, traffic measurement or corporate filing.

Matching each claim to its evidence

To investigate a network’s actual beginning, analysts need evidence tied to the event being claimed. Corporate formation requires an authoritative corporate register. Contractual control requires agreements and registry processing records. First operational use may require internal change records, customer activation evidence or contemporaneous measurement. First BGP visibility requires archived collector observations, with the limits of collector coverage stated.

LACNIC Whois and RDAP remain valuable because they preserve a public registration surface. The disciplined conclusion is narrower and stronger: the record was created at the stated time. Any larger history should be joined from independently dated sources, not smuggled into the word created.

Sources