Summary

  • Two live LACNIC event views can be mistaken for one measure: one counts registrations and the other is labelled attendees, but the public page does not define the second count or time it.
  • At the 20 October capture, the page showed 1,215 registrations and 706 in the separate attendees view while the event was still under way; neither number establishes final turnout or an attendance rate.

The most important detail in LACNIC 46’s public statistics is not the difference between 1,215 and 706. It is the missing sentence that would tell a reader what the second number means.

At 19:36 UTC on 20 October, the LACNIC Event System’s registration view labelled 1,215 people “Registered participants.” It broke that total into 864 in person and 351 remote. A separate “attendees” view returned its own breakdown: 696 and 10 by participation mode, 633 Spanish, 31 English and 42 Portuguese by language. Those latter categories sum to 706. The official event page placed LACNIC 46–LACNOG 2026 in Mendoza from 19 to 22 October, so this was an interim snapshot, not a post-event account.

The source does not say whether “attendees” means people checked in, people with a particular registration status, credentials issued, or another event-system state. Nor does the public page show when either chart was last refreshed. The capture time is an observer’s timestamp; it is not the system’s stated data time. Without those definitions, subtracting 706 from 1,215 would turn two differently labelled system outputs into a claim about people who did not attend. Dividing one by the other would create an attendance rate the source itself does not publish.

This is a modest but consequential publication problem. A live event dashboard can help participants understand the scale and format of a meeting. It can also be reused in later reports, presentations or arguments about who took part. Once a number leaves its original screen, its label and time boundary often disappear first. A count that was provisional during day two may later be read as a final outcome.

The remedy is straightforward: state the operational meaning of each count, identify its observation window and display a “data as of” time with the event’s time zone. If the value is a check-in count, say so; if it represents another status, name that status. Keep registrations and attendance as separate measures, and preserve the event’s closing time before presenting a final total. LACNIC’s published page does not currently provide those details, so no stronger conclusion is supported.

Sources