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,337 articles
CASE FILE
Sanctioned but Not Ordered: Svea's Two Accountability Channels
When a Swedish financial regulator fined Svea Bank AB 170 million kronor in December 2025, the fine made headlines. What the decision itself ordered — and, more precisely, what it did not — tells a sharper story about where accountability for the bank and for its internet-facing…
CASE FILE
The Mailbox Was Never the Remedy: Where Accountability Actually Fired in the Svea Abuse-Contact Chain
Every abuse report has to land somewhere. For Svea's legacy routed network block 193.105.138.0/24, the landing place shown by independent mirrors of the RIPE Database is a shared mailbox on the Verizon Business domain — a carrier-era contact inherited from a lineage Svea never…
CASE FILE
The Mailbox That Exists Only in the Registry: Svea's Abuse Contact and the Limits of "Valid"
When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the group's abuse-contact surface in the RIPE registry did not follow the merger. Nearly four years later, the routed legacy netblock 193.105.138.0/24 still presents a mailbox on a third party's domain…
Afrinic SAGA
The Treaty That Says Nothing About the Registry: Inside Smart Africa's AFRINIC Authority Gap
Smart Africa's public engagement in AFRINIC governance runs on an internal board resolution and a series of statements, while its founding treaty — signed in Kigali, gazetted by Rwanda in 2023 — contains no provision mentioning AFRINIC or delegating any registry competence.…
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…
CASE FILE
GoCodeIT Support: a role label, a corporation, and where accountability actually sits
GoCodeIT Support is a name that looks like a person in the registry, but the public evidence shows it is an institutional contact role — and the accountability behind it sits with a company in two RIRs at once.
CASE FILE
The Chain That Was Touched: Where Attention Fell in the Svea Abuse-Contact Record
The Chain That Was Touched: Where Attention Fell in the Svea Abuse-Contact Record intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
CASE FILE
Filing the Complaint: The Public Remedy Path Behind the Svea Abuse Contact
Svea's abuse contact in the RIPE registry passes every automated check the registry runs, and no public source shows it has ever answered a report. This briefing sets out the filing test: the channels a reporter can actually use today, and the observable responses that would…
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…
CASE FILE
SensorThings Gains an SSN Relationship Map, Not a Round-Trip Guarantee
W3C has added a seven-row navigation crosswalk to its sensor ontology draft. It makes a migration choice visible, while leaving the conversion and its evidence to the teams that operate it.
CASE FILE
The Remedy That RIPE Policy Already Defines: What Compliance Would Look Like for the Svea Abuse Surface
Three BTW articles published on 29 September 2026 documented how the Svea group's abuse-contact surface in the RIPE registry splits between a renamed organisation entity, a person entity still carrying a dissolved company's name, and contradictory mirror displays. None of them…
CASE FILE
RFC 9643: The Service Beyond the Configured Proxy
Treating an accepted TCP egress configuration as evidence of service reachability confuses instructions with results. Operators need to establish which proxy admitted the connection, which remote identity answered and whether the intended application operation actually completed.
CASE FILE
The Named Custodian: Who Actually Holds a RIPE Abuse Contact, and What the Record Shows About Placeholder Accountability
Every network abuse complaint in the RIPE service region is directed at a mailbox named in the RIPE Database. Prior reporting has established that the registry validates only that this mailbox can receive mail, and that the escalation machinery above it has never fired for a…
CASE FILE
The Sensor Stream Went Quiet. The Sensor Had Not Promised to Stay Safe
A conditional CoAP observation can save power and bandwidth by reporting only selected changes. That silence is designed, not self-explanatory. Between the physical resource and the operator sit sampling, condition evaluation, notification timing, delivery and application…
CASE FILE
The ACL Read Back Clean. The Access Decision Had Not Yet Happened
NFSv4.2 can carry a POSIX Draft ACL without forcing it through a lossy translation. That closes an important representation gap. It does not turn a successful `SETATTR`, a matching `GETATTR`, or a familiar `getfacl` display into proof that a later user was allowed to open the…
CASE FILE
Four Databases, Four AlmazClouds: The Incompatible AS210328 a Buyer Meets in September 2026
Four Databases, Four AlmazClouds: The Incompatible AS210328 a Buyer Meets in September 2026 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
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…
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