RIPE NCC's Reserve in Months, Not Millions

Summary

• RIPE NCC reported a Clearing House Reserve of EUR 33.663 million at 31 December 2025 against a 2026 operational-expense budget of EUR 41.125 million. On its own calculation, that is 82 percent of annual expense, or 9.8 months at the full planned burn rate.
• The reserve policy adopted in May 2026 expresses a 60-100 percent target band. In time terms, the minimum is 7.2 months, the 80 percent benchmark is 9.6 months and the maximum is 12 months of the current full budget. Months make the consequences of crossing those points easier to understand than percentages or millions.
• RIPE NCC says immediate cuts to non-essential spending could extend the current reserve by another four to six months and support at least 15 months with zero income. That conclusion is plausible but not independently reproducible until the organisation publishes the monthly cost of full service, constrained service and the minimum core-and-handover service.
• Different risks require different reserve compartments. A banking delay, sanctions-related payment delay, cyber recovery, litigation loss, mass revenue shock and transfer of essential registry functions have different timing, liquidity and cost profiles; one undifferentiated balance can hide both excess and shortage.
• Members should receive a quarterly reserve dashboard showing liquid months, protected core months, stress assumptions, committed draws, replenishment or redistribution triggers and the service consequences of each scenario. The goal is not the smallest reserve, but a reserve whose purpose can be verified before crisis.

EUR 33.7 million is a balance, not an argument

RIPE NCC's Clearing House Reserve ended 2025 at EUR 33.663 million. To a small Local Internet Registry paying annual fees, that is a large pool of accumulated member-funded capital. To a board responsible for databases, routing-security services, staff, legal obligations and a service region exposed to war, sanctions and banking restrictions, it may look like a finite safety margin. Both reactions are reasonable and analytically weak.

An absolute balance does not say what the money can protect. It does not identify how quickly the organisation spends, which activities stop first, how much is immediately liquid, what obligations have already been committed, or how long a transfer of essential functions would take. It cannot show whether the institution is overfunded against a small collection delay and underfunded against a legal judgment or prolonged zero-income event.

RIPE NCC's May 2026 reserve document made an important improvement by translating the balance into annual-expense coverage. Against a 2026 expense budget of EUR 41.125 million, the reserve covers 82 percent, or 9.8 months at the full budget rate. The same document established a target of 60-100 percent of current budgeted operational expense, with an 80 percent benchmark.

The percentages are useful. Months are better. A member can understand that 60 percent means 7.2 months of planned expenditure, 80 percent means 9.6 months and 100 percent means 12 months. A director can ask which decisions must occur before month seven. An operator can ask whether core services survive after broader activity stops. An auditor can test the burn rate.

The phrase reserve in months is not an accounting reclassification. It is a governance discipline. It forces every claim of prudence or excess to name the service, scenario and time horizon being protected.

The official conversion is a strong beginning

The reserve document, RIPE-860, is unusually explicit. It gives the 31 December 2025 balance, the 2026 budget denominator, the 82 percent ratio and the 9.8-month result. It also says a worst case would cause non-essential spending to stop immediately, extending the period by four to six months. On that basis, RIPE NCC expects at least 15 months of operation with zero income.

This is materially more informative than saying the financial position is sound. It gives members a falsifiable model: reserve divided by monthly expenditure, modified by an assumed reduction in burn. It also acknowledges that reserves can be too high, creating risks of complacency, spending growth, hubris, poor investment and increased attraction to litigation.

The next step is to publish the denominator behind the extension. At the full annual rate, monthly expense is approximately EUR 3.427 million. The EUR 33.663 million balance divided by that rate produces about 9.82 months. To reach 15 months with the same opening balance, average spending during the stress period would need to fall to roughly EUR 2.244 million per month, or about 65.5 percent of the full budget. Put differently, the scenario assumes that approximately one third of normal spending can be stopped or deferred quickly enough.

That may be conservative. It may be difficult. The public document does not yet identify which costs make up the reduced rate, how fast contracts can be exited, which staff remain, whether redundancy or restructuring costs increase early cash outflow, or whether a crisis raises legal and security spending while other spending falls.

The official calculation should therefore be treated as a testable base case, not a guaranteed survival period. Its value lies in inviting a better cost map.

The target band becomes clearer when expressed as time

RIPE-860 sets a minimum of 60 percent, a benchmark of 80 percent and a maximum of 100 percent of current budgeted operational expenses. Using the EUR 41.125 million 2026 denominator, these correspond to EUR 24.7 million, EUR 32.9 million and EUR 41.1 million.

In months, the same policy reads:

Reserve position	Full-budget months	Governance meaning
60 percent minimum	7.2 months	A replenishment plan is required if the audited balance falls below this point.
80 percent benchmark	9.6 months	The intended central position for ordinary planning.
82 percent actual at 31 December 2025	9.8 months	Slightly above the benchmark using the 2026 expense budget.
100 percent maximum	12.0 months	A reduction or redistribution plan is required above this point.

The band is wide in operational terms. The difference between minimum and maximum is 4.8 months at the full burn rate, or EUR 16.45 million. A policy can reasonably permit this flexibility, but it should identify why the organisation occupies one part of the band rather than another.

If threat levels rise, investment liquidity falls or a costly handover becomes more plausible, a position near the upper boundary may be justified. If income is collected early, outstanding receivables are small and stress tests show rapid cost reduction, a position near the benchmark may be enough. If members are paying higher fees while reserves remain above the benchmark and no named risk has changed, the institution should explain why accumulation is preferable to fee relief or redistribution.

Months expose the choice. A proposal to add EUR 4 million is a proposal to add about 1.17 full-budget months. A EUR 4 million redistribution removes the same margin. Members can debate the operational consequence rather than react to a large number in isolation.

There is more than one monthly burn rate

The full annual budget is an appropriate common denominator because it is published and comprehensive. It is not the only useful one. A continuity reserve should be tested against at least three burn rates.

The first is the planned full-service rate. It includes the activities and capacity approved for the year. For 2026, it is roughly EUR 3.427 million per month. This rate answers how long the reserve can fund the organisation without reducing its plan.

The second is a constrained-service rate. It assumes a serious revenue or banking shock and stops defined expansion, travel, events, discretionary procurement, new initiatives and other deferrable work while maintaining contractual and operational obligations that cannot disappear immediately. RIPE NCC's four-to-six-month extension implies such a rate, but the public needs its composition.

The third is the core-and-handover rate. It funds the minimum services needed to preserve accurate registry data, authentication, RDAP and WHOIS access, reverse DNS, RPKI, essential security, incident response, communications, legal compliance, backups and the transfer of those functions if RIPE NCC cannot continue. This rate may be lower than the constrained rate in some months and higher in others because a handover brings one-time engineering, legal, data-protection and staffing costs.

The three rates should not be moral rankings. Activities outside the core can remain valuable. RIPE Atlas, training, meetings, policy support and regional engagement may produce significant public benefit. The distinction asks what can be deferred during an existential financial event, not what should be abolished in normal times.

Without these rates, the reserve policy measures the resilience of the entire institution while claiming to protect crucial functions. The two are related and not identical.

A core-continuity budget must be reproducible

The 2026 Activity Plan and Budget provides enough detail to begin the separation. It budgets the Registry division at EUR 5.665 million and identifies Registration Services, Member Services and Registry Monitoring. Other essential functions sit elsewhere: the LIR Portal, RIPE Database, RPKI, DNS and K-root, information security, legal, finance, infrastructure and shared IT. Simply taking the line called Registry would understate the cost of continuity.

The reverse mistake is treating every organisational cost as indivisible from the ledger. The full EUR 41.125 million includes community engagement, learning, meetings, coordination, measurement services, facilities, leadership and projects with different crisis priority. Some may remain necessary to maintain trust and communicate during stress; others can pause.

RIPE NCC should publish a service dependency map. Each essential output would identify direct staff, systems, vendor contracts, facilities, security, shared services and legal obligations. Shared costs would be allocated by a stated method. The result would be a monthly minimum for operating the service and a separate one-time estimate for moving it.

The map should also show time to cut. A travel budget can stop quickly. An office lease cannot. Staff costs may require notice, restructuring payments and retention incentives. Cloud, colocation and security contracts may be fixed. A cyber event can increase consultancy expense precisely when other work stops. A reserve model that assumes immediate reduction based on annual budget categories may overstate months available.

Reproducibility does not require publishing exploitable infrastructure details. Members need service categories, cost ranges, contractual timing and assumptions. Auditors can inspect the protected detail. The public figure should be sufficient for another analyst to obtain approximately the same months.

The discipline is simple: if RIPE NCC says it can run for 15 months, a member should be able to see what is running in month fourteen.

Accounting capital is not the same as spendable continuity

The reserve appears as capital, but a crisis consumes liquidity. Assets may include cash, short-term investments, bonds and other positions with different maturity, market and access characteristics. A euro in a bank account available for payroll tomorrow is not operationally identical to a security that must be sold through a delayed or disrupted banking relationship.

The 2025 Financial Report describes conservative treasury management, government bonds and short-term investments, while the June 2025 Treasury Statute prioritises preservation of principal and limited risk. That approach is appropriate for an institution that cannot speculate with member funds. It still leaves a timing question: how many reserve months are available in cash or near-cash within one day, one week, one month and one quarter?

RIPE NCC's service region complicates banking. In 2025, the Executive Board recorded that onboarding a new investment partner could take six to nine months, possibly because the organisation invoices across a diverse region that banks classify across risk categories. The organisation changed investment arrangements and later placed treasury management with ABN AMRO. A banking-friction scenario can affect both incoming member money and access to reserve assets.

The dashboard should therefore distinguish accounting months from liquid months. It should deduct committed but unpaid obligations and identify assets subject to settlement delay, counterparty concentration or currency exposure. It should also show a minimum payroll-and-vendor liquidity buffer separate from longer-term investments.

This is not an argument for holding everything as idle cash. Inflation and bank concentration also threaten continuity. It is an argument for matching asset maturity to service obligations. Treasury performance should be judged partly by whether funds arrive before the service deadline, not only by return and nominal preservation.

The annual fee cycle creates a timing risk, not only a revenue risk

RIPE NCC invoices and collects most annual membership fees early in the financial year. RIPE-860 notes that the majority of budgeted income is collected before the end of the first quarter. This means the reserve is not normally expected to fund twelve months before revenue arrives.

The timing creates two different stress periods. A shock in January or February may occur before most fees are collected, requiring cash to bridge ordinary expenditure and delayed receipts. A shock late in the year may arrive after income has been used and before the next cycle. A mid-year shock may find substantial income already collected, reducing immediate reserve need but raising questions about obligations to members who prepaid.

Reserve months should therefore be reported on a rolling basis. The 31 December balance is useful and seasonally sensitive. A monthly dashboard would show opening cash, collected income, remaining committed expenditure, reserve assets and stress coverage. The same EUR 33.7 million can represent different resilience in February and October.

The model also needs a fee-collection haircut rather than only zero income. Zero income is a valuable extreme. More plausible cases might include 5, 15, 30 and 50 percent collection loss by geography or risk category. Correlated legal, banking or geopolitical events may delay a specific group while other members continue paying.

The relevant question is not how long the reserve lasts if no one ever pays again. It is how the organisation changes course when a measurable part of expected income does not arrive on time. Months make the trigger visible: at what projected coverage does the board freeze hiring, defer projects, seek a fee adjustment or protect the core compartment?

Sanctions-related delays reveal the need for scenario matching

RIPE-860 says sanctions and bank classifications delayed EUR 1-1.5 million of committed funding annually from 2022 through 2025. It then observes that a EUR 33.6 million reserve could cover EUR 1.5 million a year for 22.4 years. The comparison is intentionally illustrative: the delay is real, but the full reserve is much larger than that one risk.

In monthly full-budget terms, EUR 1.5 million is about 0.44 months. EUR 1 million is about 0.29 months. If the sole purpose of the reserve were to bridge the observed annual delayed funding, less than half a month would cover the historical upper figure before considering eventual collection.

That does not make the reserve excessive. It shows why risks cannot be pooled rhetorically. The same money also protects against zero income, unexpected costs, litigation, restructuring and handover. A correlated sanctions expansion could affect far more than the historical amount. The reserve document expressly notes the diversity of the service region and the possibility of a broader event.

The proper response is to assign a scenario sleeve. The dashboard might show 0.5 months for observed payment delays, an additional stress amount for a multi-country collection event, and the assumptions that would increase or release that margin. Money need not sit in separate bank accounts for every sleeve, but the claims on the common balance should be visible.

Otherwise a modest historical delay can be cited to justify a large reserve while the same balance is simultaneously counted in full for zero-income survival, litigation and handover. Scenario accounting prevents one euro from appearing to protect every risk independently.

Cyber recovery has a different cost curve

A cyber incident may not reduce income immediately. It may instead increase expenditure while essential systems are impaired. Incident responders, external forensic specialists, replacement infrastructure, legal advice, member communications, identity re-verification and security monitoring can create a sharp early cash requirement.

The monthly model should therefore include a one-time shock plus a higher short-term burn, not only a lower constrained rate. A plausible exercise could assume immediate containment costs, three months of elevated security and support, delayed projects, and a gradual return to normal. The reserve must be liquid early enough to fund the spike.

The service boundary matters. A compromise of a public website is different from a compromise affecting member accounts, registry data or RPKI. The latter may require broad credential rotation, independent verification and restoration from known-good state. Continuity spending can rise even if systems remain online because trust must be re-established.

Insurance may reimburse some cost, but policy exclusions, deductibles, proof and payment timing mean insurance should not be counted as immediate cash unless the terms support it. Vendor support may be contracted, but the reserve model should include the obligation and any surge rates.

Cyber months should be presented as survival of service quality, not mere corporate payroll. Can authoritative data remain available? Can holders authenticate? Can route authorisations continue? Can affected records be isolated? How long can enhanced monitoring operate?

A flat reserve-to-budget ratio cannot answer these questions. A scenario with a front-loaded cash curve can.

Litigation requires a reserve limit and a continuity firewall

RIPE-860 identifies litigation and possible damages as risks, noting the financial interests associated with Internet number resources and warning that high reserves can themselves attract claims. This is a mature recognition of both sides of the issue.

Litigation risk should not become an unlimited claim on continuity funds. The institution may need to defend its contracts, comply with courts and protect the registry. It may also pursue strategic positions whose cost and benefit are contestable. Members should not discover after the fact that months of core resilience were consumed by discretionary litigation.

The reserve policy should distinguish legal operations, case contingency, adverse-award risk and emergency continuity. Board authority should define when a matter can draw from each compartment. A material draw should identify its effect in months. Privileged advice can remain confidential while aggregate exposure, decision authority and reserve impact are reported.

Scenario design should include at least three legal cases: sustained defence cost without damages, an adverse payment plus continued operation, and an order requiring rapid service or data transition. Each has a different shape. A damages award may be a large one-time outflow. Long proceedings create recurring burn. A handover order creates parallel-operation cost.

The continuity firewall should protect a minimum period of registry operation and orderly transfer from ordinary litigation spend. If law permits funds to be reached by creditors, the limitation should be stated rather than hidden by an internal label. Structural protection may require insurance, contractual arrangements, separate custody or advance continuity agreements, all subject to legal review.

Members need to know that defending the institution cannot silently consume the ability to preserve the function.

Handover is the scenario that tests institutional humility

RIPE-860 includes a purpose that is rarely stated so directly: reserves may finance handover or continuation of an essential function if RIPE NCC cannot, or is not allowed to, execute it. This is one of the strongest elements of the policy. It recognises that Internet continuity does not require institutional immortality.

A handover reserve should be costed independently. It may require simultaneous operation of source and target environments, data reconciliation, contract and privacy analysis, staff retention, security review, credential and key ceremonies, public communication, operator support, litigation management and independent assurance. Costs rise before the old organisation can shrink.

The handover period should have milestones: verified export, target restoration, dual operation, authoritative cutover, reconciliation, operator remedy and closure of source access. The reserve model assigns monthly cost to each phase and identifies one-time items. It should assume some revenue loss as confidence changes and some staff departure as institutional uncertainty grows.

The handover compartment is different from a reserve intended to keep every present activity alive. Its purpose is to protect the ledger, dependent services and operators even if the surrounding institution contracts. If the compartment is not visible, directors may spend it sustaining ordinary structure until too little remains to move the function safely.

RIPE NCC does not need to predict its own failure to publish a credible cost. A tested handover budget strengthens confidence in the present provider because it shows that continuity has been engineered beyond leadership assurances.

The relevant measure is not only months until money is gone. It is months until another qualified provider can carry the essential state.

Staff continuity needs more than an annual salary total

RIPE NCC's services depend on specialised staff. Database engineers, registration experts, security professionals, infrastructure operators, legal and compliance staff, finance personnel and support teams hold knowledge that a distressed organisation cannot replace instantly.

A reserve model that reduces staff cost aggressively may extend arithmetic survival while weakening actual service. Conversely, a model that preserves every position and planned hire may overstate what is essential during a zero-income shock. The answer is role-based continuity.

The core-and-handover budget should identify positions and capabilities required in each phase, minimum coverage, cross-training, on-call duties, succession and retention. It should include the cost of keeping key people through a transition and the possibility that retention payments or temporary contractors raise short-term spending.

Employment law and notice periods affect cash. Immediate programme cancellation does not imply immediate payroll reduction. Restructuring can require advice, consultation, compensation and management time. These timing effects belong in the constrained-rate assumption.

The reserve should also protect staff from becoming leverage. People should know which payroll and pension obligations are covered and how long. Uncertainty can cause the most portable skills to leave first, making the published months fictional. RIPE-860's historical objectives include staff security for a reason.

Members do not need personal remuneration details beyond existing reporting. They need assurance that the continuity model is built from roles and legal obligations rather than an arbitrary percentage reduction.

A reserve cannot be assessed without the fee path

Reserves accumulate through past results, investment returns and decisions about surplus. Members fund the organisation principally through fees. Reserve adequacy therefore interacts with charging policy.

If the reserve is below the protected minimum, replenishment may justify temporary fee pressure or slower redistribution. If it is above the maximum, RIPE-860 requires a plan to reduce it through refunding or redistribution. Near the benchmark, the annual fee should primarily reflect expected service cost and any explicit planned movement in risk coverage.

The connection should be shown in months. A charging proposal that intentionally adds EUR 2 million to reserves adds about 0.58 full-budget months. A surplus redistribution of EUR 2 million removes the same amount. A budget increase raises the denominator and can reduce months even if the reserve balance is unchanged.

This last effect is important. Institutional expansion can consume resilience arithmetically. If annual expense rises faster than the reserve, the capital-expense ratio falls. The response should not automatically be to raise fees and restore the ratio. Members should ask whether the new spending belongs inside the continuity denominator and whether the risk actually increased.

The Charging Scheme Task Force's work on principles, fee differentiation and decision timing is relevant because stable charging and reserve policy should reinforce each other. Members cannot judge the appropriate fee if the resilience target is opaque. Nor can they judge the reserve if activities and fees are treated as fixed facts.

A transparent model states: planned service costs this much, named risks require this many months, the opening reserve supplies this coverage, and the fee decision will move the result by this amount.

The dashboard should show claims on the same euro

One reserve balance is often described as protection against many risks. Unless those risks are mutually exclusive, the presentation can double count. A cyber event can coincide with litigation. A geopolitical shock can delay member payments and disrupt banking. A handover can follow governance or legal stress after reserves have already been used.

The dashboard should distinguish dedicated, shared and contingent coverage. Dedicated coverage is protected for a named minimum such as payroll liquidity or handover. Shared coverage can respond to several risks but is counted once in aggregate. Contingent coverage depends on recoveries, insurance or future fees and should be discounted for timing and uncertainty.

A simple waterfall can show the result. Begin with liquid reserve. Deduct committed obligations. Protect the minimum core-and-handover months. Allocate a near-term operational buffer. Show remaining flexible coverage. Then apply combined scenarios, not only one-at-a-time tests.

Correlation assumptions should be conservative and explicit. Complete zero income plus the maximum cyber and legal loss may be implausibly severe, but payment delay plus banking friction is not. Litigation and handover may be directly connected. A conflict affecting part of the service region may reduce revenue while increasing compliance work.

Stress results should show the lowest month of liquidity, not only ending balance. An organisation can be solvent over the year and unable to pay an urgent obligation in week two. Recovery time should be included because fee changes and asset sales are not instant.

Members do not need a bank-style capital model with false complexity. They need to know whether the same EUR 10 million has been promised three times.

Trigger rules turn the reserve from comfort into control

A reserve policy becomes operational when thresholds cause defined action. The current 60 and 100 percent boundaries require plans after the most recent audited report. That is useful but potentially slow. A fast-moving event can change forecast coverage months before the next audit.

RIPE NCC should monitor both audited position and forward projected months. Trigger levels can initiate graduated action. Falling below twelve liquid weeks might restrict new commitments. Falling below a protected core threshold might require board approval for any non-core draw. A projected breach of the 7.2-month minimum could require a published recovery plan. A sustained position above twelve full-budget months could initiate fee or redistribution review.

Triggers should account for scenario changes. A severe cyber event may justify drawing reserve even while the ratio remains above benchmark. A large committed legal exposure should reduce available months before payment. A handover trigger should protect rather than freeze the transfer budget.

Board discretion remains necessary. Mechanical rules can worsen a crisis if they force cuts at the wrong time. Discretion should produce reasons: which trigger was reached, which action was taken, what alternative was rejected and how core continuity remains protected.

Member approval may be required for charging or redistribution, but emergency operational protection cannot wait for a General Meeting. The authority schedule should state what management, the Executive Board and members can each decide.

Triggers change incentives. Directors know that expansion has a visible reserve consequence. Management knows that delayed corrective action will cross a public threshold. Members know that a reserve below minimum is not simply described as comfortable.

Quarterly reporting would make annual policy credible

The annual Financial Report is detailed and independently audited. The Activity Plan and Budget is detailed and open to member feedback. The reserve goals now provide an explicit target. The missing layer is a concise recurring connection among them.

A quarterly reserve statement could fit on a small number of pages. It would show opening reserve, liquid assets, investment maturities, committed obligations, full-service months, constrained-service months, core-and-handover months, scenario changes, actual draws, forecast year-end position and trigger status.

It should reconcile to financial statements and explain material differences. If the budget changes, the denominator changes. If a new risk is added, its cost and overlap are stated. If an asset becomes less liquid, accounting and liquid months diverge. If the board decides not to act at a trigger, reasons are recorded.

The report should also show service indicators. Reserve sufficiency is not proved if costs are low because essential capability has degraded. Availability, staffing gaps, backup tests, security incidents, critical vendor concentration and handover readiness provide context.

Independent assurance need not audit every quarterly estimate as if it were a statutory account. Auditors can review the methodology, source data and annual reconciliation, while internal control certifies interim numbers. Periodic scenario exercises can test whether cost reductions and transfers are feasible.

This form of reporting would reduce argument. Members could still disagree about the correct number of months, but they would debate a common model rather than competing impressions of EUR 33.7 million.

Too little and too much reserve fail in different ways

Under-reserving exposes the registry to coercion by timing. A bank, creditor, litigant, supplier or sudden revenue loss can force decisions before members or operators can respond. Staff leave, security work is deferred, systems become fragile and a handover is attempted too late. The institution may preserve cash by restricting service, shifting cost to operators.

Over-reserving creates quieter risks. Fees accumulate beyond named needs. Management gains room for expansion without returning to members. Investment and banking exposure grow. A large balance becomes attractive in litigation. Members may rationally disengage because annual financial choices appear predetermined by institutional comfort.

The two failures are not symmetric. Losing essential registry continuity can impose wide external harm, so prudent policy should tolerate some margin. But prudence is not an unlimited number. It is a documented relationship between risk and time.

The 60-100 percent band reflects this balance. Its legitimacy will depend on whether the 80 percent benchmark remains connected to tested scenarios. If core service can run much longer than 15 months because the essential burn is low, members may ask why the full-institution benchmark is needed. If a realistic handover and legal shock exhaust the balance in six months, the current benchmark may be too low despite the impressive euro amount.

Months do not decide the answer. They make the trade visible enough to decide.

A worked stress table would improve the policy

RIPE NCC could publish a worked table using ranges rather than claims of prediction. An illustrative structure would look like this:

Scenario	Income assumption	Spending pattern	One-time cost	Primary question
Early-year collection delay	Most fees late by 60-90 days	Full service	Limited financing cost	Is immediate liquidity sufficient until committed income arrives?
Regional sanctions expansion	10-20 percent of fees delayed	Full service, added compliance	Moderate	How long can service continue without penalising affected operators?
Major cyber recovery	Income largely continues	Elevated core cost, deferred projects	High and front-loaded	Can trusted state and authentication be restored without cash delay?
Prolonged legal stress	Income continues with uncertainty	Normal service plus legal burn	Possible award	Does litigation consume protected continuity months?
Zero-income institutional shock	No new receipts	Rapid move to constrained service	Restructuring cost	Are the claimed 15 months reproducible?
Mandatory service handover	Revenue declines during transfer	Parallel source and target operation	High transition cost	Can essential functions move before funds or staff run out?
Combined geopolitical and banking event	Partial fees and constrained asset access	Higher compliance, lower discretionary spend	Variable	Are accounting reserves available when needed?

The table would include best, central and adverse values, the lowest liquid point and the decision triggered. It would show which assumptions are management estimates and which have external evidence.

Members could then test proposed reserve levels. The benchmark should cover the selected central set plus margin; the minimum should preserve core continuity and handover under a defined adverse case; the maximum should prevent accumulation beyond credible combined risk.

The objective is not to forecast the exact crisis. It is to show that the institution has considered the shape of cash need rather than multiplying one annual budget by a policy percentage.

Reserve governance is membership accountability in financial form

RIPE NCC is a membership association operating infrastructure used beyond its voting membership. The Executive Board manages, the organisation prepares budgets and reports, and members vote on important financial matters. This arrangement creates a duty of translation.

Members should not need to be accountants to understand how much continuity they are funding. Nor should a small group of finance specialists be able to dismiss concern by pointing to an audited balance. Audit establishes reliability of financial statements. It does not decide the appropriate service perimeter or risk appetite.

The months model gives different members a common language. A small operator can ask why fees fund ten full-budget months. A large operator can ask whether a cyber or handover scenario needs more. A board member can explain why a draw was necessary. Staff can see the protected runway. Relying networks can assess whether essential services are resilient.

Accountability also requires admitting uncertainty. Cost cuts may take longer than planned. Investment access may be delayed. A new legal duty may raise spending. The dashboard should show ranges and confidence, not manufacture precision to one decimal month when assumptions are broad.

The 9.8-month figure is precise because it is a simple ratio. The 15-month claim is a scenario. Both are useful when labelled correctly. The first describes coverage at one budget rate; the second depends on management action and cost behaviour.

Membership control becomes meaningful when members can see the difference and influence the assumptions before the reserve is needed.

The reserve should protect the ledger, not every institutional preference

RIPE NCC performs many valuable functions. It supports number-resource registration, routing security, DNS, data services, measurement, training, meetings, policy coordination and regional engagement. A reserve large enough to protect the entire present institution can be defended as going-concern prudence.

The stricter continuity test asks what must survive even if the institution cannot. Accurate registry state, authentication, public lookup, reverse DNS, RPKI, security, evidence, operator communication and lawful transfer cannot be allowed to disappear. Broader activity may pause, change funding or move separately.

This distinction should not be used to starve public goods during normal operation. It should control reserve claims. If management wants to preserve a measurement platform or engagement programme through a zero-income event, it can explain the benefit, cost and duration. The activity does not become essential merely because it is currently bundled with the registry.

The same discipline protects RIPE NCC from hostile simplification. Critics cannot credibly say only the staff labelled Registry matter when RPKI, security, shared systems, legal compliance and support sit elsewhere. A dependency-based core budget will be larger than a superficial line item and smaller than the whole institution. Evidence replaces slogan.

The reserve policy's reference to handover already accepts the central principle. Its most important purpose is not to keep every organisational form unchanged. It is to maintain the crucial function in a worst case.

Months should therefore be reported for both the institution and the ledger. The gap between them is the space where informed member choice belongs.

Nine point eight months is useful because it can be challenged

RIPE NCC's reserve is neither obviously excessive nor obviously limited public evidence. The current public evidence supports a narrower conclusion. At the 2026 full-budget rate, EUR 33.663 million equals about 9.8 months. The policy benchmark equals 9.6 months. The minimum equals 7.2 and the maximum 12. Management believes rapid constraint can extend current coverage to at least 15 months with zero income.

Those statements create a solid base for accountability. The unresolved questions are the constrained burn rate, core service boundary, handover cost, asset liquidity, combined risk, contractual timing and activation rules. Each can be measured more precisely without pretending the future is certain.

The institution should publish three answers every quarter: how many months of the approved plan are funded, how many months of constrained operation are funded, and how many months of essential service plus orderly handover are protected. It should show the cash available at each horizon and the events that change the answer.

Members can then decide whether fees, spending and redistribution are aligned. Auditors can test inputs. Operators can assess continuity. The board can defend prudent reserves without relying on institutional prestige. Critics can identify a specific assumption rather than calling the whole balance too large.

The number of millions will continue to matter for accounts. The number of months should govern the argument. Money is the input. Continuity over time is the purpose.

Sources and analytical limits

The principal source is RIPE-860, Goals of the RIPE NCC Clearing House Reserve, published on 17 May 2026. It supplies the 60-100 percent target, 80 percent benchmark, EUR 33.663 million 31 December 2025 reserve, EUR 41.125 million 2026 expense denominator, 82 percent ratio, 9.8-month full-budget calculation, four-to-six-month extension assumption, at-least-15-month zero-income conclusion, EUR 1-1.5 million annual delayed-funding example, 22.4-year comparison, stated reserve purposes and acknowledged risks of excessive reserves. These are RIPE NCC's policy statements and scenario assumptions, not independent guarantees.

The RIPE NCC Activity Plan and Budget 2026, RIPE-850 supports the annual budget, activity divisions, service costs, staffing and consultation context. The RIPE NCC Financial Report 2025, RIPE-856 supports the audited financial position, capital-expense ratio, reported reserve, asset categories, receivables, risk disclosures and treasury changes. Budget categories are not treated as automatic classifications of essentiality.

The June 2025 Treasury Statute supports the conservative investment objective, principal-preservation priority, risk parameters and reporting responsibilities. The 187th Executive Board minutes support the attributed six-to-nine-month bank-onboarding concern and the decision to discontinue the then investment partnership. These materials do not establish how quickly every reserve asset would be available in an unspecified crisis.

The Final Report of the Charging Scheme Task Force 2024, the 2026 budget consultation page and the October 2025 General Meeting minutes support the member-financing and budget-accountability context. They do not prescribe the scenario compartments proposed here.

The monthly calculations in this article are arithmetic conversions of published figures: annual expense divided by twelve, reserve divided by monthly expense, and target percentages multiplied by twelve. The constrained-rate estimate required to stretch EUR 33.663 million to 15 months is an analytical inference, not a RIPE NCC published budget. No protected contract schedule, detailed liquidity ladder, cyber-insurance policy, legal exposure estimate, staff-restructuring plan, handover cost model or confidential treasury statement was available.

The proposed dashboard, compartments, triggers and stress table are governance recommendations, not findings that RIPE NCC is presently under-reserved, over-reserved or unable to meet its obligations.