Summary

  • The official ARIN short link for its 2026 Candidate Forum leads to a current event page for 8 October, but the page says the election runs from 30 October through 7 November. ARIN’s 2026 candidate slate and election calendar instead put voting between 22 and 30 October.
  • The stray window exactly matches the dates in ARIN’s 2025 candidate-slate announcement. The public record does not show how it got there or that anyone relied on it, but the mismatch makes a simple point: an election deadline should be generated from one cycle-stamped source, not copied independently across credible-looking pages.

Analysis

On 30 October, one ARIN page says the ballot opens and two others say it closes. That is not a philosophical disagreement about Internet governance. It is a collision between two dates on public surfaces maintained for the same election.

The oddity sits on a page that otherwise looks unmistakably current. The official arin.net/candidateforum address leads to a registration site headed “ARIN 2026 Candidate Forum”. It gives the forum date as Thursday, 8 October 2026 at 2:00 PM Eastern Time. It invites readers to hear ARIN Board candidates discuss IPv6, routing security and Internet governance. It describes a 90-minute Zoom webinar and says that only the candidates and moderator may speak. Registration is active.

Then an “About the ARIN Elections” panel says the voting period runs from 30 October through 7 November.

ARIN’s own 8 September candidate-slate announcement gives a different schedule: online voting opens at 3:00 PM Eastern Time on Thursday, 22 October and closes at 7:00 PM on Friday, 30 October. The 2026 election calendar gives the same opening and closing times. The source of the stray dates is visible in the archive. ARIN’s 2025 candidate slate set voting from 30 October through 7 November 2025.

The evidence supports a narrow conclusion. A current 2026 event page retained the previous cycle’s voting window when it was observed on 11 September. It does not establish that ARIN changed the election, that the archived dates have procedural force, that anyone missed a ballot, or that the error was deliberate. Responsibility cannot be assigned from the public pages. The event page is hosted by Swoogo, but it is reached from ARIN’s official short link and presents itself as an official ARIN event surface. For a reader, that distinction is invisible until the dates are compared.

The practical risk comes from the direction of the error. If the stale page merely moved the opening by a day while leaving the close intact, a careful voter might still recover. Here the stale opening date is the real closing date. Someone who relied on the forum page could believe that there was no reason to look for a ballot during nearly the whole actual voting period. After 30 October, the same person could believe another eight days remained even though the official calendar says the election had ended.

No evidence shows that this happened. The point is that the published information creates the possibility without asking a reader to visit a suspicious or obsolete page. The page has the correct year. It has the correct forum. It has an active registration button. Its visual currency masks a stale deadline.

Elections run on more than bylaws and ballots. They also run on reminders, event pages, calendar entries and the ordinary routes by which a Voting Contact decides when to pay attention. Those surfaces are part of the participation mechanism because timing determines whether a formal right can be used. A correct rule stored in one place does not neutralise a wrong date displayed on another official route.

The useful repair is smaller than a governance reform and more durable than a manual correction. ARIN could give each election cycle one structured identifier and one canonical pair of opening and closing timestamps. Any event page, candidate guide or announcement that displays the voting window would render those values from the same record. A publication check would reject a page marked for the 2026 cycle if its deadline fingerprint belonged to 2025.

Call it a deadline checksum. It need not be cryptographic theatre. The public signal could be as plain as “Election cycle 2026 · window version 2026-09-08”, linked to the calendar that supplies the dates. Behind it, a build or content-management check would compare year, opening time, closing time and timezone before publication. If a date changes, the source record changes once and dependent pages either update or fail visibly.

A correction receipt matters too. Election information is unusually vulnerable to screenshots and forwarded messages. Silently replacing the old dates may fix the next visit while leaving earlier copies circulating. A dated note recording the observed value, the corrected value and the correction time gives candidates, members and staff a shared account of what changed. It also prevents a later debate from turning into an argument about memory.

The current 2026 slate and calendar are the coherent public schedule: 22–30 October. The forum page should converge on that window. The larger lesson is that a deadline is not decorative text. It is executable governance, because readers organise action around it.

Sources