Summary

  • ARIN awarded $17,350 to Virginia Tech and $20,000 to Dominica State College, for a 2026 total of $37,350. Its Board minutes say two of ten applications were selected and the total was below the program budget.
  • ARIN’s program timeline says final project reports are due in October 2027. A reporting section lower on the same page says the final written report is due in September 2027.
  • No recipient is shown to be late. The open issue is document authority: the published blank agreement contains no September or October date, while the recipient-specific executed agreements are not public.

The award arithmetic is settled. ARIN’s 22 September announcement assigns $17,350 to Virginia Tech for an RPKI Operational Health Dashboard for the ARIN Service Region and $20,000 to Dominica State College for a Youth Internet Governance Lab. Together, the awards total $37,350.

That is $12,650 below the program’s published annual ceiling of $50,000. The 18 August Board minutes record that two of ten applications were selected, that their combined total was less than the budget, and that the Board approved the selection 10-0. ARIN’s program rules also say the selection committee is not obliged to spend the entire budget. The public record therefore supports the amount, not a theory about why the remainder was unused.

The unresolved part begins after selection. On the current Community Grant Program page, the program timeline says final project reports are due in October 2027. In the reporting section on that same page, recipients are told that a final written report is due in September 2027. The page also asks for an initial update by the end of March 2027 and a prerecorded presentation in spring 2027. Those two intermediate checkpoints do not resolve the final-month conflict.

A one-month difference is an evidence problem

September versus October is not a large interval in the life of a grant. It is large enough, however, to change when a recipient freezes its evidence, closes expenditures, approves a narrative and decides that an outcome can be stated publicly. It also changes when ARIN can reasonably mark a report as expected and when a member or outside observer can begin asking whether the record is complete.

This is not evidence that either recipient has failed an obligation. Both dates are in the future. Nor does the announcement prove that funds have already moved: ARIN says disbursement follows the required documentation, and the public notice records awards rather than recipient-specific payment events.

The useful question is narrower: which document is the authoritative clock?

The public agreement points to a hierarchy, not a date

ARIN publishes a blank Grant Recipient Agreement, version 4 dated 9 February 2023. It says an agreement becomes effective when ARIN countersigns it. It requires two written reports describing objectives, use of funds, outcomes, reach and community benefit, and it calls for results to be shared at least once within 12 months after funding is received.

The blank form does not specify September or October 2027. It also says that amendments must be in writing and authorized and signed by ARIN, and that the agreement prevails over explanatory documents if the two conflict. This establishes a sensible authority order. It does not reveal what date appears in the executed agreement for either 2026 recipient.

The Board minutes do not fill that gap. They document institutional approval of the selections, not the operative reporting terms. The ARIN 57 transcript says projects should be completed by fall 2027, which is consistent with either month but does not choose one.

The public sources therefore support three separate records:

Record What it proves What it does not prove
Board minutes Selection and approval of two applications Recipient-specific obligations or disbursement
Program page Public instructions and the presence of two different final-report dates Which date controls an executed grant
Executed agreement The recipient’s binding terms, if published or disclosed Not currently available in the public record reviewed here

The repair is a small control surface

ARIN does not need a new reporting regime to make the clock auditable. It needs one versioned schedule with a visible effective date and a clear statement of document authority. If the executed agreements set September, the timeline should say September. If they set October, the reporting section should say October. If recipient agreements differ, the public page should say that the agreement controls and avoid presenting one universal month.

A compact public receipt could preserve four things: the controlling document, the applicable deadline, the date recipients were notified of any correction, and the publication date of the final report or completion note. That would let the community distinguish an editorial correction from a contractual change and a report deadline from a publication date.

The two funded projects are designed to create public value: one seeks operational evidence about RPKI health; the other seeks campus evidence for inclusive and resilient Internet governance. The grant program’s own reporting record should meet the same standard. The issue is not whether September or October is more generous. It is whether the public can identify the clock that ARIN and the recipients are actually using.

Sources

  1. ARIN: 2026 Community Grant Program Recipients Announced
  2. ARIN Community Grant Program
  3. ARIN Board of Trustees meeting minutes, 18 August 2026
  4. ARIN Grant Recipient Agreement, version 4
  5. ARIN 57 day-two transcript