Topic
Abuse-contact Economics
Within the Topic facet, Abuse-contact Economics 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.
CASE FILE
Completed According to Whose Plan? Svea Bank's Self-Reported AML Remediation Meets the Regulator's Record
When Sweden's financial supervisor Finansinspektionen (FI) announced a sanction against Svea Bank AB on 17 December 2025, the operational part of the decision contained exactly two points: a formal remark (anmärkning) and an administrative fine of SEK 170 million. There was no…
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
Three Months After the Fine: No Follow-Up, No Appeal, No Documented Remedy for Svea Bank
On 17 December 2025, Sweden's financial supervisor Finansinspektionen (FI) gave Svea Bank AB (org. no. 556158-7634) a formal remark (anmärkning) and a sanction fee of SEK 170 million for breaches of core anti-money-laundering rules…
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…
Story
The Svea Abuse-Role Record: Validated Contactability, No Documented Processing
The abuse contact recorded and mirrored for Svea's legacy netblock 193.105.138.0/24 is a carrier-era inherited mailbox on the Verizon Business/UUNET lineage — registry-validated for technical deliverability but never documented to have received, answered, escalated or remediated…
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…
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
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…
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 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…
Europe and Middle East Institutional
The Machinery That Never Rings for Abuse: Inside the RIPE NCC's Escalation Layer
The RIPE NCC possesses a complete, published, time-tested apparatus for escalating a dispute to a binding outcome: an arbiters panel appointed by its Executive Board, a twelve-week ruling clock, a published archive of rulings, and a 30/60/90-day termination ladder ending in the…
Europe and Middle East Institutional
What Would Prove the Repair Is Durable? The Svea Abuse Roles After the Finansinspektionen Sanction
Nearly four years after Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, and roughly nine 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…
Global Institutional
Nearly Four Years After the Merger, the Svea Abuse Surface Still Splits Between Record and Responsibility
When Sweden's financial supervisor restated in December 2025 that Svea Bank had assumed all of its parent's obligations, it confirmed where responsibility legally lives. The RIPE record tells a more complicated story: an organisation entity renamed to the survivor, a person…