Topic
WHOIS/RDAP Accountability
Within the Topic facet, WHOIS/RDAP 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.
Global Cloud Services
NovaCloud-Hosting's registry administration is split across three maintainers: who actually runs the operator's record?
NovaCloud-Hosting's registry administration is split across three maintainers: who actually runs the operator's record? intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and…
Global Cloud Services
One operator, two RIPE organisations: the administrative layer BTW had not yet mapped
One operator, two RIPE organisations: the administrative layer BTW had not yet mapped intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
CASE FILE
Tideo Administration: The Registry Record That Refused to Move
Tideo Administration: The Registry Record That Refused to Move 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 CASE…
CASE FILE
Three Names on One Netblock: How Custody of Svea's Legacy Abuse Contact Split Across a Merger
When a Swedish bank merges, its internet number resources do not disappear — they inherit. The RIPE Database record for 193.105.138.0/24 is a rare case where you can read the aftermath directly in a public registry entity: three distinct legal parties, one dissolved predecessor…
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…
Story
AS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRA
AS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRA 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 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…
Story
Control Split: Who Held Prevention and Detection on the Svea Abuse-Contact Surface
Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, but the RIPE registry entities that describe the group's abuse-contact surface have barely moved since 2021 and 2022. A timestamp-by-timestamp reading shows that recent maintenance in this chain fell almost entirely on…
Global Cloud Services
Five prefixes, five answers: what AS210973's mirror disagreement teaches about trusting the record
Every monitor that watches the routing table tells a slightly different story about the small Vienna network operated by DATAMATIX Datensysteme GmbH. Reading those differences carefully — rather than averaging them away — is the fastest way to learn which layers of the internet's…
Global Institutional
DFINFRA and AS210860: When the Verification Layer Contradicts Itself
DFINFRA and AS210860: When the Verification Layer Contradicts Itself 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.…
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…
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
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
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…
Europe and Middle East Cloud Services
The Registry Says One Company, the Records Say Another: Inside AS210328's Identity Gap
The Registry Says One Company, the Records Say Another: Inside AS210328's Identity Gap intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
Europe and Middle East Institutional
Registered Valid, Operationally Unproven: Where the Svea Abuse Surface Stands After the Finansinspektionen Sanction
Nearly four years after Svea Ekonomi AB merged into Svea Bank AB, and months after Sweden's financial supervisor fined the survivor bank SEK 170 million for anti-money-laundering failures, the abuse-contact surface the Svea group presents in the RIPE registry still reads as a…
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…
Story
DFINFRA and AS210860: the cost of verifying a silent registry record
A German retail group's registry entry still names a contact for a network that has not announced a single prefix since March 2026, while a peering profile derived from the same network still promises ten address blocks and an open door. Every counterparty who consults these…