Summary

  • AS211899 "SVEA" is registered to Svea Bank AB (ORG-SBA155-RIPE, reg-nr 556158-7634) with abuse contact SEAR1-RIPE and the mailbox jorgen.edstrom [at] svea [dot] com, while person object JE4899-RIPE (Jorgen Edstrom) still lists the address "Svea Ekonomi AB", Evenemangsgatan 31, Solna — the legal entity dissolved by merger on 3 January 2022.
  • The remedy instruments exist and are public: the RIPE NCC reporting procedure for incorrect contact data, the ripe-705 policy mandating annual abuse-mailbox validation, proposal 2017-02 documenting escalation up to LIR closure and resource de-registration, and the ripe-844 arbitration procedure for contested registration disputes.
  • Every remedy rung above reporting depends on the resource holder: the RIPE NCC's own support page states there is nothing it can do if an operator chooses not to reply, and the RIPE Database terms place accuracy responsibility on the maintainer.
  • Finansinspektionen's SEK 170 million sanction against Svea Bank AB (2025-12-17) demonstrates what a working supervisory remedy looks like in the banking track; no equivalent public instrument certifies the state of the Svea abuse-contact surface in the registry track.
  • The gap is therefore not absence of remedy, but a remedy path whose enforcement triggers have no publicly observable status, leaving reporters unable to tell whether the named contact is maintained by anyone at all.

The registry record and its two names

The RIPE record for AS211899, as reflected in publicly available mirrors of the registry, ties the corporate family together in a way that spans the merger. The aut-num is registered to organisation ORG-SBA155-RIPE with the name "Svea Bank AB", country SE, registration number 556158-7634, and carries the abuse-c attribute SEAR1-RIPE (IPIP.NET mirror of AS211899). The filtered WHOIS output reports: "Abuse contact for 'AS211899' is 'jorgen.edstrom [at] svea [dot] com'" (Sitezilla mirror of AS211899). The person object behind the technical contact, JE4899-RIPE for Jorgen Edstrom, still lists an address beginning "Svea Ekonomi AB" at Evenemangsgatan 31, SE-169 81 Solna (IPIP.NET mirror of AS211899).

These two names refer, under Swedish law, to a single continuous business. The merger instrument recorded by the supervisor makes that explicit: Svea Ekonomi AB, the parent, merged into Svea Bank, and all of its business is now run by Svea Bank (Finansinspektionen sanction decision). The registry record is not therefore pointing at an orphan; it is pointing at a live operator through labels that no longer match the operator's legal form. The question this article pursues is what a party who cares about that mismatch can actually do.

Which instrument grants the power

The authority over abuse-contact data in the RIPE region flows from a chain of instruments, each public. At the base is ripe-705, "Abuse Contact Management in the RIPE Database", which mandates the abuse-c contact attribute for inetnum, inet6num and aut-num objects and requires role objects used for abuse contact to carry a single abuse-mailbox attribute (ripe-705). Provider-reported excerpts from the document state that the mailbox "must be available in an unrestricted way via whois, APIs and future techniques".

The same document establishes the validation regime: "The RIPE NCC will validate the 'abuse-mailbox:' attribute at least annually. Where the attribute is deemed incorrect, it will follow up in compliance with relevant RIPE Policies and RIPE NCC procedures" (ripe-705). This is the first genuine remedy-adjacent power: the registry itself, not the reporter, is tasked with checking the contact surface on a schedule.

The escalation logic comes from proposal 2017-02, "Regular abuse-c Validation", the policy proposal that led to the validation regime. Its provider-reported text records the problem and the backstop: ripe-563 introduced the mandatory abuse-c attribute without validation; the RIPE NCC receives several hundred reports of invalid contact information each year; and "If a resource holder remains unresponsive or refuses to change incorrect contact information, existing RIPE policies allow the RIPE NCC to close LIRs for unresponsiveness or repeated policy violations, as well to de-register independent resources" (proposal 2017-02). The same proposal notes that more than 1,000 external reports on incorrect abuse-mailbox attributes had been resolved without triggering closure, and that even after closure is triggered a resource holder has a further three months to resolve the problem before actual closure or deregistration.

Finally, the RIPE Database Terms and Conditions place the standing obligation on the holder: "The Maintainer is responsible for keeping all data maintained by them accurate and up-to-date, including correct Contact Details", with data required to be "good enough to contact the Maintainer or Registrant within a reasonable time" (RIPE Database Terms and Conditions). The RIPE NCC, for its part, expressly disclaims a guarantee of accuracy, completeness or availability of the database.

The reporter's remedy path

For a person who finds the Svea record unsatisfactory — an abuse mailbox that does not answer, a person object naming a dissolved company — the documented entry point is the RIPE NCC reporting procedure. For the category "Incorrect contact information in the RIPE Database", the procedure states that where a reporter has already tried to contact the maintainer, the RIPE NCC will forward the report to the person responsible for the registration and track it (RIPE NCC Reporting Procedure). The procedure also draws a boundary: it is not intended for network abuse such as spam or phishing outside the registry's responsibilities, and actual disputes are routed to the Arbiters Panel.

The boundary of the registry's substantive authority is stated plainly on the abuse-support page: "Our role is to ensure that all abuse contacts are valid and up-to-date in the RIPE Database. From there, it is the responsibility of the network operator to handle your abuse report. There is nothing we can do if a network operator chooses not to reply" (How to Find Abuse Contact Information). This sentence is the crux of the Svea remedy question. The registry can police whether a mailbox exists and is reachable; it cannot compel the operator behind it to answer the reports that arrive.

For contested data — a dispute over who is entitled to a registration, or what the correct contact data should be — the instrument is ripe-844, the RIPE NCC Conflict Arbitration Procedure, which implements paragraph 12.4 of the RIPE NCC Articles of Association. The arbiters rule on disputes between Members and the Management Team regarding decisions under the Standard Service Agreements, disputes between two or more Members regarding the registration of internet number resources, and disputes involving Legacy Internet Resource Holders. Parties must first document grievances and attempt resolution between themselves before requesting arbitration, and non-compliance with a ruling can, after two weeks and absent referral to a competent national court, lead to termination of the Standard Service Agreement (ripe-844).

Applying the path to the Svea record

Walk the instruments against the observed record. The mismatched names on AS211899 and JE4899-RIPE fall squarely within the reporting procedure's "incorrect contact information" category: a reporter who has tried the mailbox and failed can file, and the RIPE NCC will forward and track. If the holder remains unresponsive, proposal 2017-02's escalation ladder — annual validation under ripe-705, follow-up, and ultimately closure and deregistration — is the registry's own enforcement instrument. If the holder contests that the data is incorrect, ripe-844 arbitration is the dispute forum, with national courts as the backstop.

What the public record does not contain is any observable status for any of these rungs as applied to Svea. No published validation report, tracked-report outcome, arbitration request or compliance action certifies whether the Svea abuse-mailbox attribute has been validated, found correct, or found wanting. The registry's remedy path is real but opaque: it operates between the RIPE NCC and the resource holder, and neither party has a published instrument on this record. By contrast, the Swedish supervisory track shows what a completed public remedy looks like — Finansinspektionen's decision of 17 December 2025, a remark plus a SEK 170,000,000 administrative fine under chapter 15 of the Banking and Financing Business Act (2004:297), with the violation severity expressly weighed against withdrawal of authorisation and the fine computed against group turnover of roughly SEK 6,271 million (FI decision; FI English notice; Swedish-language notice). That sanction concerns anti-money-laundering compliance, not registry contact data, and FI's instruments are silent on RIPE matters — the two tracks do not link in any located document.

The governance conclusion is precise. The Svea record is not remedy-less, and it is not lawless: a named policy instrument, a validation schedule, an escalation ladder and an arbitration forum all apply to it. But the remedy path's every consequential rung is triggered by holder responsiveness, and its status is invisible to the public. An abuse reporter facing this contact surface today cannot determine from any public source whether the person object naming a dissolved company is an unvalidated legacy artifact, an accepted current address, or a matter already known to the registry.

That asymmetry — a functioning internal remedy machinery with a blank public scoreboard — is the finding this article leaves for the record, and the thing to watch for is any published validation or arbitration outcome touching the Svea objects.