Topic
Membership Accountability
Within the Topic facet, Membership Accountability topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.

Leaders
John Curran and ARIN’s 2019 Resilience Test
ARIN’s December 2019 outage exposed a gap between a high-availability design and a recovery path that could survive a shared-storage failure. The public record shows how the registry restored its website and customer application on separate clocks, then made remediation and…

Story
ARIN’s Grant Page Lists 18 Applications. Board Minutes Say 10.
ARIN’s live 2026 grant summary lists 18 applications and two selected projects. Draft minutes from the Board’s August meeting say two of ten applications were selected. The public record does not say whether those totals count different stages.

Story
Two-Thirds, Not Unanimity: How the RIR Governance Document's Version 3 Rewrites Who Decides
The draft that would replace ICP-2 does not merely modernise twenty-five-year-old criteria for recognising Regional Internet Registries. Its Version 3 quietly redraws the voting arithmetic of recognition, derecognition and amendment — and those thresholds, not the prose around…

Story
The 2019 Excess-Contribution Redistribution: How the RIPE NCC's Own Instruments Authorised and Applied a Contested Remedy
When the RIPE NCC returned EUR 8,365,249 to its members in 2020, the money did not move by improvisation. It moved under Standard Service Agreement Article 7, a Clearing House Procedure that predates the decision, and a General Meeting vote that split hard enough to show how…

Story
Call for Nominations to the RIPE NCC Executive Board: What the 2026 Record Actually Publishes
The RIPE NCC has run a complete Executive Board nomination cycle for its May 2026 General Meeting. Reading the registry's own instruments — the call for nominations, the candidate and nomination procedure pages, and the document submission guidelines — shows a process that is…

CASE FILE
The Architecture of No Recourse: RIPE's Formal Abuse-Escalation Map
Every abuse complaint in the RIPE service region ends in a mailbox the registry validates for deliverability — and in an escalation architecture that, on the published record, offers the reporter no route into any binding mechanism. This investigation reconstructs that…

Story
The Ladder That Has Not Fired: What the Public Record Shows About Enforcement on the Svea Abuse-Contact Surface
When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the RIPE Database inherited a problem that no merger clause can settle by itself: the group's registered abuse-contact surface. Nearly four years later, that surface still carries the dissolved company's identity in…

Story
The First October General Meeting Under RIPE NCC's New Board Structure
On 28 October 2026, at 16:00 (UTC+2), the RIPE NCC membership convenes for the October 2026 General Meeting — held online over 22–24 October and running alongside RIPE 93. By the draft timetable, the formal members-only section begins on Wednesday 28 October, electronic voting…

Number Resource Society
RIPE NCC's Excess-Contribution Redistribution: A Codified Remedy, Not a Gesture
When the RIPE NCC returned EUR 8,365,249 to its members in 2020, the money moved under a written procedure that predates the decision — and the October 2019 General Meeting vote that authorised it was split hard enough to reveal how contested the choice between reserve and…

CASE FILE
The Mailbox Is Not the Complaint: A Four-Layer Test for Whether RIPE's Abuse-Contact System Actually Works
Every network abuse complaint in the RIPE service region ends, at some point, in an email address recorded in the RIPE Database. The registry proves each year that tens of thousands of those mailboxes can receive mail. What nobody can prove — because nothing published measures it…

Europe and Middle East Institutional
The Campaign That Counts Mailboxes: Inside the RIPE abuse-c Validation Machine, 2018–2025
Every year, the RIPE NCC sends a machine's worth of checks against nearly ninety thousand email addresses in the RIPE Database, publishes the tally in its annual report, and calls the exercise complete. This report reconstructs that validation campaign from its own primary…

Story
The abuse chain that validates its first link and stops there
Every year the RIPE NCC proves that tens of thousands of abuse-contact mailboxes work. Nothing it publishes measures whether a single third-party abuse report ended in verified remediation. This report traces that gap to the policy text that created the validation mandate, and…

Story
RIPE NCC’s 2027 Fees Count Accounts and Resources Separately
The annual fee is attached to an LIR account; several other charges attach to particular resource registrations. Reading the schedule by its units makes the 2027 change clearer—and exposes what public totals still cannot tell an operator.

Number Resource Society
Where the Power Sat: RIPE NCC's 2020 Surplus Redistribution and the Contract Clause Behind It
When the RIPE NCC returned EUR 11,035,874 to its members, the instrument of authority was not a board discretion or an Articles-of-Association clause, but a single provision of the Standard Service Agreement — and one recorded General Meeting resolution exercised it.

Story
Who Controls Abuse in the RIPE Region? The Measurement Surface and the Remedy Surface
Every malformed abuse report in the RIPE service region eventually arrives at the same question: who is actually responsible for stopping abusive use of internet number resources? The RIPE NCC's own published documents give an unusually precise answer, and it is not the one…

Number Resource Society
RIPE NCC's 2020 Surplus Redistribution: One Recorded Resolution, One Number, and What Changed Since
When the RIPE NCC returned 11 million euros to its members, the instrument of authority was a single General Meeting resolution — and the record of how it was granted still frames how the membership controls the registry's money today.

Story
APNIC’s 93% Service Score Needs a Member-Only Comparator
APNIC’s published service-quality line reads 94%, 95%, then 93%. The numbers remain high, but the 2026 endpoint brings a broader respondent mix into a measure previously reported for Members. A Member-only bridge would preserve the trend without erasing the wider community’s…

Story
RIPE NCC’s October Vote Sends Surplus and Deficit in Opposite Directions
The draft resolution for RIPE NCC’s October General Meeting assigns a 2026 surplus to reserves but a deficit to members in 2027. If members reject it, the agenda describes the reverse allocation; the 2025 meeting approved that alternative.

Story
LACNIC Warned About Attendee-Database Emails. That Is Not Yet a Breach Notice.
A sales pitch can prove that somebody was targeted. It cannot, by itself, prove how the sender found the target. LACNIC's warning about emails offering attendee databases is useful precisely because it stops at that boundary. The next useful step is to make the changing evidence…

Story
The Remedy Path Audit: What AFRINIC's Appeal Committee Can and Cannot Hear Under Receivership
When AFRINIC's Board appointed a CEO designate on 24 August 2026, it wrote four words into the first sentence of its own announcement: "with the consent of the Receiver." Four days later, when the same Board constituted the Policy Development Appeal Committee, those words were…
