Summary

  • RIPE NCC says an arbitration request leads to a lock and warning on the relevant RIPE Database records until the arbiter’s ruling is communicated. That describes the treatment of records, not a demonstrated guarantee of continued membership or services. RIPE-858
  • Its arbitration procedure describes a 12-calendar-week ruling period measured from commencement, with reasonable extension permitted. Commencement has prerequisites; the period is not a guaranteed filing-to-resolution interval. RIPE-844

What the lock actually tells a member

A member challenging a decision by RIPE Network Coordination Centre needs more than confirmation that a review route exists. It also needs to know what happens while the challenge is pending.

RIPE NCC’s closure and deregistration document, RIPE-858, published on 7 May 2026, says that when a member requests arbitration, it will lock the relevant RIPE Database records and add a warning statement. RIPE NCC describes those measures as remaining in place until communication of the arbiter’s ruling. It also refers members to the timeframes in its Conflict Arbitration Procedure. RIPE-858

The distinction matters. A database lock concerns the treatment of records. It does not, by itself, establish whether a membership continues, whether contract termination or resource deregistration is suspended, or whether a particular service remains available. Nor does the provision establish that those protections are absent. Those are separate questions requiring the applicable terms and, in an individual dispute, confirmation of the actual status.

A lock could preserve a contested record against alteration. Depending on its scope, it could also restrict a change that a member needs to make. A warning could give database users useful notice while prompting questions about the entry. Neither a protective nor a harmful outcome follows automatically: the relevant fields, permissions, exceptions and downstream use would need to be known.

Administrative control of a record should therefore not be confused with ownership of number resources or direct control over routers and traffic. The member-facing accountability question is narrower and more practical: who can change what during review, and what happens if an urgent correction is needed?

A request is not the start of every clock

RIPE NCC’s Conflict Arbitration Procedure, RIPE-844, is dated 20 June 2025. According to its section C.2.3, both parties must sign the arbiter’s indemnification statement within two calendar weeks of the final arbiter’s notification. Both signatures are a condition of commencement. That two-week signature period is not the initial window for requesting arbitration. RIPE-844, section C.2.3

RIPE NCC describes an additional condition where the dispute involves an outstanding invoice to it: the invoice must be paid to RIPE NCC, which holds the amount in escrow for the arbitration’s duration. In those cases, commencement requires receipt of payment as well as both indemnification signatures. This is a conditional provision for invoice disputes, not an established payment requirement for every arbitration. RIPE-844, section C.2.3

Section C.4 then describes a ruling to be communicated within 12 calendar weeks from commencement. RIPE NCC’s procedure allows the arbiter to extend that period reasonably at their discretion. The commencement conditions therefore matter to interpreting the timeframe, including the payment condition where applicable. RIPE-844, section C.4

There are three distinct milestones: requesting arbitration, satisfying the conditions for commencement, and receiving communication of the ruling. RIPE NCC’s description connects the database measure to the first and last of those events, while the stated ruling period runs from commencement. Without the dates for each milestone, the publications cannot establish total elapsed time from a request to a ruling.

Adding two weeks to twelve would not produce a universal fourteen-week maximum. The periods have different triggers, the interval before commencement has not been established here, and the ruling period permits extension. For an invoice dispute, the payment condition is also relevant to cash planning before commencement; no amount or actual inability to obtain review is demonstrated by these provisions alone.

What remains outside this account

This is an examination of two dated publications, not a claim that the provisions were newly introduced. RIPE NCC’s descriptions of its own process are also not an independent record of how an individual challenge was handled.

The current initial filing deadline and its trigger are not established in this briefing. A member should not infer that there is no deadline, or use the signature period as a substitute. The precise effect on closure, termination and deregistration likewise remains unresolved here, as do the lock’s detailed scope and any exceptions for corrections.

Nor does this account establish the full indemnification terms, the arbiter’s remedial powers, the binding force of a ruling or the mechanism for implementing it. No individual dispute, merits decision, court order, outage or commercial loss is established.

The bounded conclusion is useful nonetheless: access to arbitration, interim treatment of registry records and effective implementation of an outcome are different tests. A published decision period cannot answer all three. For members assessing continuity, the missing link is evidence of what remains usable while review proceeds—not simply the existence of a clock.