RIPE NCC · RIR Watchdog
Story
BTW reporting and context linked to this RIR. For the proposal-by-proposal history, the people involved and their changing positions, start with Policy.
Story
Latest stories
332Stories
Story
RIPE's member-of Proves Authorized Set Membership, Not Live Route Propagation
RIPE's member-of Proves Authorized Set Membership, Not Live Route Propagation intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
Story
RIPE Database mnt-ref Authorises an Organisation Reference, Not Corporate Control
An accepted `org:` link in the RIPE Database has passed a meaningful authorisation test. That makes it evidence of an approved database reference—not a shortcut to proving ownership, group membership or control of the network behind the record.
Story
RIPE’s IPv6 PI Draft Makes Membership a Compliance Event
A router, a customer appliance and a `/56` can remain exactly where they were. Under RIPE’s current IPv6 PI draft, the moment the holder’s LIR account becomes active may nevertheless change whether that arrangement complies. A policy transition this quiet needs its own receipt.
Story
RIPE assignment-size Describes Aggregated IPv6 Assignments, Not Active Subscribers
A `/46` contains 1,024 possible `/56` prefixes. When a RIPE Database entity pairs that aggregate with `assignment-size: 56`, the arithmetic is exact—but the tempting subscriber count is not. The field records the size used for End User assignments inside an aggregate…
Story
RIPE NCC’s Fibre Returned in Minutes. Access Recovery Took About Thirty Minutes
On 27 May, a supplier’s work in a manhole disconnected RIPE NCC’s fibre for only a couple of minutes. The connection came back and recovery was automatic. Yet RIPE NCC says it took about thirty minutes for everything to recover. The useful question is not whether automation…
Story
RIPE NCC Counted 1,799 Registry Checks. Its Public Target Has No Cohort Ledger
Seven RIPE NCC member updates report 1,799 Assisted Registry Checks completed from January through July 2026. That is nearly three-quarters of the annual 2,400-check commitment. It is a clear production count. It is not yet a coverage account: the public series does not say how…
Story
RIPE Database sponsoring-org Records Administrative Sponsorship, Not Network Operation
The word “sponsor” can sound like ownership, financing or operational command. In the RIPE Database, `sponsoring-org` has a narrower and more useful meaning: it identifies the organisation administratively responsible for sponsoring an independent Internet number resource under…
Story
RIPE Database Now Composes Unicode. The Text Chain Needs a Normalisation Receipt
One visible name can arrive as two different code-point sequences. RIPE Database release 1.123 deliberately makes those sequences converge before the value passes through its remaining UTF-8 controls. That is good interoperability. It is also the moment when an evidentiary chain…
Story
RIPE RPSL aut-num Policies Declare Intended Routing, Not Observed BGP Behaviour
An import or export line in a RIPE Database aut-num entity is valuable evidence of a registered policy statement. It is not a measurement of what routers are doing now.
Story
A TTL Jump Can Make a RIPE Atlas Trace Invent an AS Link
A traceroute can place a destination directly after one visible network even when several unseen routers still forwarded the packet. The missing segment is not always silence or a tunnel. New RIPE Atlas research shows that an on-path device can raise the probe's TTL and let it…
Story
RIPE NCC’s RDAP Country Code Does Not Geolocate the Network
A two-letter country code looks ready for a map. In a RIPE NCC RDAP network entity, however, it is a registration field—not a set of coordinates and not live evidence of where routers, users, traffic or services are located.
Story
RIPE’s RDAP Type Classifies a Registration, Not the Route Origin
RIPE’s RDAP Type Classifies a Registration, Not the Route Origin intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
Story
A Failed RIPE Database Update Can Still Change Records
RIPE NCC's documentation describes an update message whose entities can finish differently. The useful response is therefore not just a verdict on the message: it is an account of the changes already made, those rejected and those the caller still cannot confirm.
Story
RIPE's Flip Chart Experiment and the Work After the Introduction
A paper board helped researchers and network operators find one another. RIPE NCC's new account points to a useful next test: whether a promising introduction becomes a question both sides can afford to pursue, without silently committing either to data access or production…
Story
RIPEstat’s Empty IP Lookup and the Route Beside It
A user’s two differently worded requests produced different views of a route. A successful retest leaves a narrower question than an outage: what did an empty answer actually establish?
Story
RIPE’s IRR Study Says RPKI Can Replace a Route Object, Not a Customer Cone
A new RIPE Labs study makes a useful distinction that is easy to lose in general talk about replacing the IRR. A prefix–origin record and the policy information used to discover a customer cone are not the same operational entity, so they cannot share one retirement decision.
Story
RIPE Rebuilt LatencyMON. A Chart Still Needs Its Own Interpretation Receipt.
RIPE NCC has rebuilt LatencyMON, the RIPE Atlas view used to compare latency trends across probes. The update makes a great deal more of the measurement surface visible: more test types, a choice of grouping logic, an option to reach beyond the aggregated time range and a…
Story
RIPE NCC Fixed a Cross-Service Vulnerability. The Remediation Needs a Chain Receipt.
“Fixed” is a useful word only when a reader can tell what changed its meaning. RIPE NCC’s June account of a multi-service vulnerability disclosure makes that distinction unusually visible. It describes several issue categories across more than one service, and it also says that…
Story
RIPE’s RPKI Key Plan Is Not Yet a ROA Scope Receipt
RIPE NCC’s plan to move RPKI API keys toward OpenID Connect is a statement about a future access mechanism. It is not yet a public way to reconstruct which resource authority and which state-changing action stood behind an individual ROA change.
Story
RIPE NCC’s RIS Is Updating Its Peering Policy. The Archive Needs a Selection Receipt
An archive becomes a public institution long before anyone gives it a constitution. A researcher downloads a route dump; an operator compares an incident against a collector feed; a policymaker treats a graph as a picture of the network. Each act lends the archive a little…