Summary

  • RIPE-858, the RIPE NCC's closure and deregistration procedure, published 7 May 2026, sets the grounds and 90-day email escalation by which a member can lose the Standard Service Agreement over, among other grounds, unresponsiveness and repeatedly incorrect RIPE Database registration — and a valid abuse-mailbox address is part of proper registration (RIPE-858).
  • A member facing deregistration may submit evidence against it or request arbitration under the RIPE NCC Conflict Arbitration Procedure; during arbitration the RIPE NCC locks the relevant database records and adds a warning statement (RIPE-858).
  • The arbitration route is informal, not Dutch statutory arbitration: rulings within 12 weeks, compliance within two weeks, a one-year filing window, a €5,000 cost cap, and a standing option to take the dispute to a competent national court (RIPE-844).
  • The 7 May 2026 revision deleted postal-mail notice from the termination sequence, making email the sole notification channel; the challenge architecture was left untouched (ncc-services-wg announcement).
  • Prior BTW coverage established that the final sanction has never publicly fired for invalid abuse contacts; this report maps the remedy chain that would activate if it ever does — and finds it contract-bound, time-boxed and cheap relative to the stakes.

An enforcement ladder that never fires is, in one sense, a governance curiosity. In another, it is the most consequential paperwork in a registry: the moment it does fire, a member loses its service agreement, its internet number resources are deregistered, and every downstream network that depended on those resources inherits the disruption. The RIPE NCC has published, in exhaustive detail, the side of that instrument that describes its own power. The side that describes the member's remedy is thinner — but it exists, and it is readable if you assemble the four documents that actually govern it.

This report reads those four documents as one chain. RIPE-858 is the procedure that fires the sanction. RIPE-812, the Standard Service Agreement, is the contract that authorises it. RIPE-844, the Conflict Arbitration Procedure, is the forum where it can be contested. RIPE-602, the Articles of Association, is the constitution that decides who owns that forum. And the 7 May 2026 revision of RIPE-858 is the most recent change to any link in the chain — which is why its precise wording matters.

The instrument that fires: RIPE-858

RIPE NCC's closure document, in its current form published on 7 May 2026, distinguishes three termination tracks: a member leaving on its own initiative (section 1.1), RIPE NCC termination with three months' notice under Article 9.3 of the Standard Service Agreement (section 1.2.1), and termination with immediate effect under Article 9.4 (section 1.2.2) (RIPE-858). The three-month-notice track is the one that reaches abuse-contact conduct: its grounds include member unresponsiveness and repeatedly incorrect registration in the RIPE Database, and the document treats a valid abuse-mailbox email address as part of proper registration where such an address is referenced in inetnum, inet6num or aut-num objects.

The procedure itself is a clock, run entirely by email: an initial notification, a 30-day reminder, a 60-day second reminder, and at 90 days an official termination notification issued by the Managing Director (RIPE-858). Nothing in the document requires a hearing, a committee decision, or any body other than the registry's own staff to move the sequence forward. The Managing Director's notification at day 90 is the operative act.

The contract that authorises it: RIPE-812

The Standard Service Agreement is the instrument that makes RIPE-858 more than an internal policy. Article 9.3 permits the RIPE NCC to terminate if a member fails to meet its SSA obligations and does not remedy the failure within the period specified in the closure procedure; Article 9.4 lists immediate-effect grounds, including bankruptcy, damage to the RIPE NCC's name or trademarks, failure to provide a commercial trade register extract, and providing falsified or misleading data (RIPE-812). Article 11 selects Dutch law as the governing law and routes disputes arising from the SSA to the RIPE NCC Conflict Arbitration Procedure "as adopted by the RIPE NCC Executive Board after consultation with the RIPE NCC membership."

That last phrase is the hinge of the whole remedy chain. The forum that hears a challenged closure is not a court, not an independent regulator, and not a member-elected committee. It is a procedure adopted by the Executive Board of the very institution that fired the sanction — subject to a General Meeting veto over its design, as RIPE-602 makes clear.

The forum that hears it: RIPE-844

The Conflict Arbitration Procedure defines an Arbiters Panel appointed by the Executive Board, competent to settle disputes between members and the RIPE NCC regarding Executive Board or Management Team decisions on the SSA, "including RIPE NCC procedures and implementation of the RIPE Policies" (RIPE-844). An abuse-c-driven closure is a Management Team decision on SSA procedures, so it falls within that scope. The procedure explicitly does not apply where a service's Terms and Conditions designate a concrete competent national court.

The procedural parameters are tight and, unusually for internet governance, quantified. Arbitration must be requested within one year of the dispute commencing, and only after documented attempts to resolve it directly. The arbiter communicates a ruling within 12 calendar weeks of commencement, extendable at the arbiter's discretion. Parties must comply within two calendar weeks — or, in that same window, submit the dispute to a Dutch or other competent national court. Non-compliance with a ruling that was not taken to court leads to termination of the SSA under the closure procedure. Procedural costs are capped at €5,000 and borne by the losing party (RIPE-844).

Two features deserve emphasis. First, the procedure is formally informal: RIPE-844 states it is not "Arbitration" under Dutch civil law, which means the member's real judicial remedy is the retained right to go to a national court, not an appeal from the arbiters' ruling. Second, the RIPE NCC publishes a summary of arbitration rulings on its legal pages — the public window into how often the panel has actually ruled, and on what (Summary of arbitration rulings).

The lock that softens the interim

The most member-protective provision in the chain sits in RIPE-858 itself. If a member requests arbitration against deregistration, the RIPE NCC locks the relevant RIPE Database records and adds a warning statement until the arbiter's ruling is communicated (RIPE-858). This is not a stay of the termination decision — the SSA can still be closed — but it is a partial freeze on the registry data, which is the visible, routable surface of the sanction. A member that invokes the remedy chain in time does not see its resources silently deleted while the dispute is pending; it sees them marked.

For the parties on the other side of an abuse report, the picture is different. The RIPE NCC's reporting procedure directs abuse reports to the published abuse contacts and describes escalation paths through the RIPE NCC's own teams (Reporting procedure). The reporter has no standing in the arbitration procedure; the dispute is contractually between the member and the registry. The remedy chain this report maps is, structurally, a member's remedy chain.

What the 7 May 2026 revision changed

The revision to RIPE-858 announced on 7 May 2026 was narrow and mechanical: it deleted the postal-mail references from the notification sequences in sections 1.2.1.1 and 1.2.2.c, on the stated rationale that email is legally binding, postal mail is inefficient, and members are responsible for keeping their contact details current under the SSA (ncc-services-wg announcement).

Read against the remedy chain, the revision changed the notice channel and nothing else. The 90-day escalation, the termination grounds, the deregistration challenge route, the arbitration lock-and-warning, the 12-week ruling clock, the one-year filing window and the €5,000 cost cap all stand as they were. The one substantive asymmetry the revision introduces is evidentiary: since email is now the sole binding channel, a member that fails to monitor its registered email address loses the argument that it was never properly notified — the procedure presumes delivery to the address the member itself maintains.

That presumption makes the abuse-mailbox and contact-data validation regime more consequential, not less: the same data quality the registry polices is now the sole basis on which enforcement notice is legally presumed received.

The constitution above the forum

RIPE-602, the Articles of Association, allocates ownership of the dispute machinery. Operational decisions on the Standard Service Agreements are delegated to the Management Team; the Executive Board appoints arbiters and may propose dismissals or changes to the arbitration procedure; but the authority to approve new arbiters, dismiss current ones, or change the procedure itself is vested in the General Meeting (RIPE-602). The forum in which a closed member would contest an abuse-c enforcement outcome is therefore, in design terms, a membership-owned instrument — even though the panel itself is appointed by the Board and the sanction is fired by Management.

No instrument in the located record creates a dedicated internal appeal body for abuse-c closures specifically, and none grants the abuse reporter any challenge right. The member's remedy is arbitration within one year, then the national courts within two weeks of a ruling. That is the control surface as of this writing.

Sources