Summary

  • On 3 November 2026, ARIN said it had suspended posting to its mailing lists while troubleshooting an issue. The status incident ran from 19:11 UTC to a one-sentence resolution at 00:55 UTC on 4 November; the record does not date the exact posting suspension within that interval.
  • Two ARIN policies were then in Last Call. Their official notices directed every comment to the Public Policy Mailing List and set 11 November as the deadline. ARIN’s current policy index still displays that date.

The policy clock kept running beside a closed microphone

ARIN asks its community to speak through a mailing list, then announced that posting to its mailing lists was suspended. The notice went up at 19:11 UTC on 3 November. At 22:02 UTC ARIN said a fix had been implemented and was under observation. At 00:55 UTC on 4 November, it marked the incident resolved with a single sentence. That is five hours and 44 minutes between the first status record and resolution. The page identifies the affected component as Mailing Lists. It supplies no technical cause, list-by-list scope or message-handling account.

The timing matters because two real policy clocks were already running. ARIN’s Last Call for ARIN-2025-1, on ISP and LIR definitions, and Last Call for ARIN-2025-8, on the Section 4.10 in-region reserve, were posted on 28 October. Each says comments should go to the Public Policy Mailing List, PPML. Each expires on 11 November. The live draft-policy index continued to show both deadlines on 9 November.

This is an unusually clean collision between institutional procedure and institutional infrastructure. The ARIN Policy Development Process calls PPML an official method for discussing number-resource policy and requires at least fourteen days of Last Call. ARIN’s own policy page says anyone may participate; membership is not required. For these two Last Calls, the written instruction sent comments to one named public channel. During the status incident, the operator of that channel said it had suspended posting to its mailing lists.

Resolved is a service status, not a record of the missing hours

The status page has three stages: investigation, fix under monitoring, resolved. It says nothing about whether a message submitted during the suspension was rejected, queued, bounced or accepted later. Nor does it count attempted posts. The published timestamps establish the status window, not the exact duration of every failed posting attempt. That missing message-handling record is the fact that would change an assessment of actual participation loss.

It would also matter whether PPML itself was among the lists disabled at every point in the window. The status notice uses the broad phrase “ARIN Mailing Lists”; it does not enumerate list names. The mailing-lists page identifies PPML as part of the service and integral to the policy process. The direct overlap between a broad posting suspension and two live PPML Last Calls is therefore a real procedural question, with its precise delivery effect still unreported.

ARIN’s one-sentence closure restores a green status indicator. It leaves the public policy record thinner than the service record. The two proposals were open for comment until 11 November; the institution controlled both the comment route and the status explanation. An open process deserves a timestamped account of how the route reopened, not a shrug dressed as an incident resolution.