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 Institutional
ACSK-RIPE’s May Timestamp Does Not Yet Explain AS210263
ACSK-RIPE’s May Timestamp Does Not Yet Explain AS210263 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 Global…

Story
ARIN’s Whois Snapshot Counts Query Types, Not the Organizations Behind Them
ARIN says 79% of Whois queries in a seven-day sample concerned IP addresses, while every one of the period’s ten most active queriers came from AWS addresses. The mix describes requests; it does not identify the organizations whose workflows may depend on them.

Leaders
Andrei Robachevsky and the RIPE Database Migration That Put Every User in Scope
On 14 May 2001, a RIPE Database user could no longer send RIPE-181 updates to the familiar `auto-dbm` address. RPSL was now required there; a separate `auto-181` path would translate legacy updates until 15 October. The change was not a single overnight conversion. It was a…

Story
RIPE Database incident stayed under monitoring for 24 hours after fix notice
RIPE NCC said some web-application requests were failing with 502 responses on 7 October. A fix moved the incident to monitoring one minute after the first public report; resolution was posted 24 hours and 34 minutes later. That interval measures status states, not the length or…

Europe and Middle East Institutional Trends
RIPE’s Abuse-Contact Check Stops at Mailbox Reachability
A registry can make an abuse address easier to find and test whether its technical path looks configured. Those signals matter. They still leave a separate question unanswered: what happens after a real complaint arrives?

Europe and Middle East Institutional
Tideo Administration: The RIPE Contact Handle That Outlived Its Operator
Tideo Administration: The RIPE Contact Handle That Outlived Its Operator 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…

Europe and Middle East Regional ISP Trends
Inside almazcloud.network's Corporate Substance: A Fish-Farm Registration Behind a Cloud Storefront
Inside almazcloud.network's Corporate Substance: A Fish-Farm Registration Behind a Cloud Storefront intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Asia-Pacific Cloud Services Trends
One Mailbox, Two Companies, One Address: What Reproduced APNIC Whois Text Shows About NEXGENET COMPANY LIMITED's Accountability Surface
NEXGENET COMPANY LIMITED looks, from a distance, like an ordinary small internet provider in Yangon. Look directly at the registry records that define who answers for its networks, and the picture becomes more complicated: one generic role entity named "NEXGENET COMPANY LIMITED…

Story
EDEKA's organisation object stays live while the AS210860 aut-num record returns no entries
EDEKA's organisation entity stays live while the AS210860 aut-num record returns no entries intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

History
The Directory Tree Grew Sixfold. The Client Still Needed a Map.
RFC 3663’s Referral LDAP experiment made domain-registration data easier to query in principle. Its own engineering record shows how much work moved into data layout, referrals and clients before a familiar protocol could feel like a usable service.

Global Cloud Services
Who answers for AS209874: Novacloud's contact surfaces, registry objects and the handle that resolves to nothing
Who answers for AS209874: Novacloud's contact surfaces, registry entities and the handle that resolves to nothing intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…

CASE FILE
Who answers for a silent network: DFINFRA's contact layer, the EDEKA merger and the accountability gap
Who answers for a silent network: DFINFRA's contact layer, the EDEKA merger and the accountability gap intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…

Story
Record Hygiene or Real Movement? What AS210328's 2026 Ledger Edits Actually Changed
Record Hygiene or Real Movement? What AS210328's 2026 Ledger Edits Actually Changed intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…

Global Institutional
Tideo Administration: The Contact Handle That Outlived Its Network
Tideo Administration: The Contact Handle That Outlived Its Network 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…

Asia-Pacific Regional ISP
NEXGENET COMPANY LIMITED and the Question the Registry Still Cannot Answer
NEXGENET COMPANY LIMITED and the Question the Registry Still Cannot Answer 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…

Europe and Middle East Cloud Services
NovaCloud-Hosting's paperwork does not match its storefront: the commercial-legal trace BTW had not yet examined
NovaCloud-Hosting presents one commercial face to customers, but the Portuguese registry, the LEI record and the operator's own checkout pages tell a different story about what kind of company is actually selling the hosting. This briefing reads that paperwork layer — the part of…

Story
ARIN’s Person-POC Workflow Links the Creator’s Account by Default
ARIN’s latest POC guidance identifies a consequential distinction at the moment a contact record is created: the person it is meant to represent may not be the user account that ARIN Online attaches to it.

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…
