AFRINIC saga currently tracked end-to-end.
Governance / Case File
CASE FILE
Case File governance intelligence tracks institutions, policy processes, standards activity, registry operations, accountability disputes, and implementation signals that affect internet infrastructure. BTW.
Institutional BreakdownLegal and Policy ConflictElection and Control Risk
Institution legitimacy and continuity risk mapping.
Primary-source based timeline and risk analysis.
Used for continuity and policy exposure planning.
Latest Coverage
Latest from CASE FILE
1,361 articles
CASE FILE
The License Said Active. The Device Could Still Say No
An entitlement inventory can show that a licence exists, belongs to the organisation, points at a router and permits a feature. That is valuable coordination. It is not yet proof that the device accepted the right, the feature is running within its limits, or the network service…
CASE FILE
The Signature Passed. The Workload Was Still Not Authorized
A cryptographic check can say who formed a workload request and which parts survived transit. It cannot decide whether that workload may perform the operation. Revision 07 of the WIMSE HTTP-signature draft makes this boundary unusually visible—especially when a replay reaches a…
CASE FILE
The Child Still Answered. The Parent Had Already Moved the Delegation
A DNS server can answer authoritatively from the old home of a zone after the parent has assigned that zone elsewhere. Revision 14 of the delegation-revalidation draft turns that paradox into an operating rule: child-side credibility must never be allowed to renew parent-side…
CASE FILE
The Filter Was Distributed. BGP Never Said It Was Installed
A mitigation rule can cross every expected BGP session and still fail at the only boundary that matters to the packets. Revision 08 of the Flow Specification Version 2 draft makes ordering and dependency more explicit, then states the unresolved operational fact plainly: BGP…
CASE FILE
The Probe Reported Loss. The Network Path Was Not Yet Guilty
A missing STAMP reply looks like a packet lost in the network. Revision 21 of the MPLS STAMP draft states something more awkward: the probe may have reached a provider edge and then been discarded by the rate limiter protecting that node’s control plane. The loss number is real…
CASE FILE
The Event Was Observable. The Responder Still Could Not Act
A protocol emits a perfectly structured warning. The SIEM receives it intact. Yet the record cannot say whether the change belonged to an approved maintenance window or an intrusion, because the asset, operator and authority around the event are missing. Observability has begun…
Afrinic SAGA
The Receiver Who Has Not Yet Left: Gowtamsingh Dabee's Control Surface at AFRINIC
A termination application filed in October 2025 was meant to end the court-appointed receivership of AFRINIC. A year later, the located public record shows no discharge order — and the receiver's consent is still being recorded on the registry's corporate acts.
CASE FILE
The Port Could Break Out. It Had Not Been Split
Four channels appear beneath a 400G port, and an orchestration screen is suddenly tempted to count four usable 100G interfaces. The inventory model may be entirely truthful. The mistake begins when a statement about hardware capability is promoted into a statement about present…
CASE FILE
A Hong Kong Cloud Company, Its Taiwan Routers, and Two Imclouds
APNIC records place IMCLOUD TECHNOLOGY COMPANY LIMITED in Hong Kong. The internet's routing tables place its traffic in Taiwan. Reconciling those two placements exposes a small operator with a large identity question.
CASE FILE
One Validated Mailbox, One Unresolved Holder: Reading NEXGENET's Accountability Surface Directly
APNIC's own whois confirms that the abuse mailbox behind three autonomous systems was validated on 7 July 2026 — but the holder of one of those systems is now written differently by different public mirrors, and the registry of record still cannot be read first-hand.
CASE FILE
The Manifest Was Signed. Support Was Still an Out-of-Band Fact
A device receives an authentic update manifest, the operator console shows a plausible required version, and the rollout remains motionless. The missing fact is not in the signature: whether that Recipient implements the optional command, which local profile gives the command…
CASE FILE
The Server Was Healthy. The Dashboard Counted Its Prefetch Refusal as an Outage
A speculative request arrived before any reader had asked for the page. The server chose not to spend resources on that wager. Nothing had failed—yet the familiar status code made the refusal look exactly like a service incident.
CASE FILE
The Subscription Kept Running. Its Schema Had Changed Underneath It
The telemetry graph never went dark. Counters arrived on schedule, the subscription identifier stayed familiar, and the collector reported no transport break. Yet an upgrade had changed the schema that gave those values meaning. Continuity of delivery had concealed a…
CASE FILE
Seven W3C Directors Elected by Members Are Not Standards Delegates
W3C's 2026 election changes the people who oversee its corporation. It does not hand seven employers the Web's technical agenda. The consequential question is how the incoming directors distinguish the organizations that put them forward from the institution to which they now owe…
CASE FILE
The Value Was the Same. The Reconstructed Bytes Were Not: Deterministic CBOR
The signer and verifier held the same decoded map, agreed on every field and still computed different signature inputs. Nothing in the value had changed. One encoder had merely exercised freedoms that the other had silently removed. The failure was not “CBOR versus cryptography.”…
CASE FILE
The Proof Was Unlinkable. The Envelope Was a Fingerprint: BBS Signatures
Two BBS proof values arrive at different verifiers. The bytes do not betray that they came from the same signature. Yet both presentations carry the same rare header, the same ten-slot credential shape, the same unusual disclosed indexes and a public key used for only twelve…
CASE FILE
The Registry Said `co`. The Handshake Had Said Nothing: RFC 9952
The same two bytes appear in an IANA row, a DNS service advertisement and an endpoint configuration. Yet the packet trace contains no ALPN extension. All three records may be accurate. None can be promoted into the missing wire event.
CASE FILE
The Primitive Kept Its Name. The Reuse Rule Changed: RFC 10032
Three adjacent functions accept an AEGIS key and nonce. One encrypts and authenticates, one emits a keystream after discarding authentication, and one creates a MAC under the only reuse exception in the document. The shared primitive name is technically accurate. Treating it as…
CASE FILE
One Sequence Number Was Asked to Tell Two Histories: RFC 9721
EVPN can advertise a MAC address and an IP address together, then attach one number to say which reachability is newer. That bargain works until the two identities stop moving as a pair. RFC 9721 preserves the compact wire record, but only by creating a deeper operational duty…
CASE FILE
The Complaint That Never Reaches the Registry: Who Answers When You Report Abuse in the RIPE Region
Every spam wave, phishing kit and botnet C2 eventually produces a human being who clicks "report abuse" and waits. In the RIPE service region, the routing of that report — and the removal, in May 2026, of a paper notification channel from the registry's enforcement procedure…
Member Unlock
Restricted Profile Intelligence
Login is required to unlock full profile briefings and deep-dive sections.
Strategic Circle Briefing
Join to unlock strategic briefings after signing in.
Join Strategic CircleLeadership Alliance Briefing
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership AllianceSession Map
Active Dossiers
AFRINIC Saga
Multi-year governance and legal crisis with implications for RIR accountability worldwide.
Open AFRINIC Saga