ARIN Community Grant 2026: Which Projects Actually Get Funded
A customer pinged me mid-deal on the morning of 16 April 2026, a /22 transfer half-papered on my desk, asking whether the ARIN grant he'd just seen could "cover the address side." I closed the transfer file and pulled up the announcement to answer him properly. That same morning ARIN had opened the 2026 ARIN Community Grant Program: up to US$50,000 in total, individual grants of $1,000 to $20,000, applications open through 14 June 2026 at arin.net/grants.
An applicant has until 14 June to decide one thing: whether a project worth somewhere between $1,000 and $20,000 actually belongs in this program, or just wants the money. I broker IPv4 and IPv6 transfers for a living, which means my days run on one quiet question: who holds what address space, and whether the registry record agrees. From that seat, this program is narrower and more deliberate than the dollar figure suggests. It funds four specific categories of work, and the gap between a fundable proposal and a polite rejection is whether you read those categories the way ARIN's Board reads them.
This piece is about that gap. Not a how-to-fill-the-form walkthrough, ARIN's own form does that better than I can, but a working operator's read on which projects clear the bar, which category to file under, and why the grant deliberately will not touch the problem most people think it solves.
What ARIN Will and Will Not Pay For
The source text is admirably blunt. A project must be "noncommercial in nature" and benefit "the Internet community within the ARIN service region," and it must fit one or more of four categories: Internet technical improvements that grow the infrastructure consistent with the public interest; registry process and technology improvements that keep "a globally consistent and highly usable Internet number registry system"; informational outreach on topics like IPv6 deployment, Internet research, and Internet governance; and research tied to ARIN's mission.
The word doing the heavy lifting is noncommercial. I will say plainly what that excludes, because half the conversations I have with operators start from the wrong assumption. This grant cannot buy address space, cannot fund a proprietary product, and cannot subsidise private R&D that conveniently benefits the public later. If your underlying problem is "I am short on IPv4," the grant is the wrong instrument, and the arithmetic settles it.
The secondary transfer market sat around a mean of $22 per address in the 2025, 26 cycle, with peaks near $34 (ARIN, January 2026). A single /24 is 256 addresses. Even at the mean, that purchase clears the entire $20,000 ceiling on its own. The grant was never sized for inventory, and reading it as a discount on address scarcity guarantees a rejection.
So what does win? Work that makes the registry or the routing system measurably better for everyone, the kind of thing no single vendor has the commercial incentive to build alone.
The Category You File Under Decides the Outcome
Operators lose this grant on the framing while the substance was fine all along. A project mislabeled as general "awareness" when it is really a registry tool, or pitched as a one-organisation upgrade when it could be a shared one, trips the noncommercial and public-benefit filters before anyone reads the technical detail. Here is how I'd sort a project before writing a word of narrative.
| If your project is really… | File it under | What makes it fundable |
|---|---|---|
| A tool that improves registry data accuracy or transfer workflows | Registry process improvements | Helps *every* holder, not just yours; outlives your org |
| A testbed or measurement for IPv6 deployment | Internet technical improvements | Produces reusable public results, with named metrics |
| Documentation, training, or community education on IPv6/governance | Informational outreach | Teaches the region, not your customers |
| A study of an ARIN-mission question (exhaustion, transfers, RPKI uptake) | Research | Open methodology, publishable findings |
The registry-process category is the one I'd point a serious applicant toward first, and not because it sounds impressive. It carries the strongest public-benefit story, because a globally consistent registry is, by definition, a thing one organisation cannot fix for itself. The 2023 Internet2 grant is the template ARIN keeps holding up. It let 30 participants test real software against IPv6-only networks and documented where applications broke: a concrete count, a public result, a reusable finding. That proposal did not promise to "improve IPv6 awareness." It promised to test 30 applications and write down the failures. Specificity is what separates a fundable proposal from a hopeful one.
Where I'd Push Back on the IPv6 Framing
A lot of grant pitches this year will open with the same line: native IPv6 traffic crossed 50% globally on 28 March 2026, every nation in ARIN's 29-country region has passed the threshold, so the transition is essentially done. I sell into this market, and I think that framing quietly misleads.
Aggregate adoption hides the operators who carry the cost. T-Mobile reportedly runs around 88% IPv6 on its network, while plenty of fixed-line peers sit far lower. The 50% line is a weighted average dragged up by a handful of mobile carriers running IPv6-only cores. It is no evidence that the long tail of enterprises and regional ISPs have finished anything.
Those laggards still run dual stack, still pay to maintain two parallel routing planes, and still lean on NAT in residential segments. That is precisely the population a registry-process or outreach grant can help. A proposal that says "adoption is at 50%, so let's celebrate" tells a reviewer the applicant never looked under the average. A proposal that names the deployment gap behind that average, and the tool that closes it, tells a reviewer the applicant did.
My counsel to applicants leans the opposite way from the optimism. The transition is not over, the unevenness is the opportunity, and the grant rewards work aimed squarely at the operators still stuck halfway.
A Pre-Submission Read-Through Before You Spend the Effort
Drafting a strong narrative costs real hours. Before committing them, I weigh a proposal against a handful of criteria, and any one of them failing means the application is not ready. ARIN's deadline of 14 June 2026 is firm, with no late window, so the time spent now is the only time you get.
The first thing I look for is whether the benefit lands on the broader community rather than a single organisation, because single-org gains simply do not qualify. From there I press on whether the work is genuinely noncommercial, with no proprietary product or private R&D tucked inside the framing, since that is the filter most applicants trip. The proposal then has to name a measurable deliverable, the way the Internet2 grant named thirty tested applications: a participant count, a failure list, a published dataset, something a reviewer can point at. It also needs to map cleanly to exactly one of the four categories, so nobody scoring it has to guess where it belongs.
The last criterion is the one people skip. You have to confirm the application form requirements at arin.net/grants rather than working from a blog summary. The announcement says applicants should "clearly demonstrate how their projects meet eligibility guidelines and selection criteria in the application form." That sentence is the rubric, so treat it as one.
About
I'm Alexei Krylov, Head of Sales at InterLIR, a Berlin-based marketplace for renting, leasing, buying, and selling IPv4 and IPv6 resources. My days move between Regional Internet Registry procedure and B2B IP transactions, and I came to both through civil law. That training is why I read an announcement like this one for what it contractually permits and forbids before I read it for the marketing copy.
I have no stake in this grant. InterLIR is a commercial broker, which makes it exactly the kind of applicant ARIN would decline. I find that outsider seat useful rather than awkward, because the program funds the public-good registry work that the market, mine included, will not pay for on its own. So when a customer asks whether the grant solves their address shortage, I answer the way I would draft a deal memo: read the constraint first, then decide.
Conclusion
The 2026 ARIN Community Grant is a small, sharp instrument aimed at a specific job: improving the shared registry and routing fabric that no single operator profits enough to fix alone. Its ceiling is too low to touch the IPv4 scarcity that dominates my conversations, and that is by design rather than oversight. A funded application treats the four categories as a real filter, picks exactly one, and brings a measurable, public deliverable in place of a vision statement.
If you are weighing an application, the most valuable hour you can spend before 14 June is not on prose. It is on classifying your project against the four categories and pressure-testing whether its benefit genuinely leaves your own walls. The form and the eligibility detail live at arin.net/grants, and that document, not this article, is the one you are graded against.
So if the grant works as intended this cycle, the address-scarcity problem my customer asked about will still be sitting on my desk in June, and a little more of the registry plumbing underneath it will quietly be in better shape.
Frequently Asked Questions
Individual grants range from $1,000 to $20,000, awarded based on project need. ARIN's Board of Trustees approved up to US$50,000 in total for the entire 2026 cycle, so multiple projects share that pool.
No. The program is explicitly noncommercial. It cannot purchase address space or subsidise proprietary product development. With transfer prices near $22 per address on average, even one /24 would exceed the grant ceiling, so it was never designed for inventory.
Pick the single best fit: Internet technical improvements, registry process improvements, informational outreach, or research. Reviewers should never have to guess. Registry-process work tends to have the clearest public-benefit story, since a consistent registry helps every holder rather than one organisation.
One with a measurable, public deliverable. The 2023 Internet2 grant tested 30 applications on IPv6-only networks and documented the failures - a concrete count and a reusable result. Vague "raise awareness" pitches lose; named metrics and outcomes that benefit the whole community win.
Applications are open through 14 June 2026, and the window is firm - no late submissions. Confirm the current eligibility guidelines and selection criteria on the application form at arin.net/grants before you draft, since that form is the document you are evaluated against.
