Summary

  • The refreshed research mapped eight relevant RIPE NCC endpoints, but captured no live response values. Current holder, prefix, visibility, historical and neighbour status therefore remain unverified.
  • The meaningful next signal is not the existence of AS210775 alone. It is a dated chain linking the identifier, a current holder record, route origination, observed visibility, topology and actual corporate use.

The central distinction: a number is not a network

The earlier public profile of niceshops Niceshops GmbH described AS210775 as dormant and framed it as a latent network control surface. It also connected the company’s online retail and logistics context with the possibility that future announcements could change how its services appear to the Internet. That framing is useful as a watchlist, but it does not answer whether the network resource has remained unchanged, whether it was ever operationally used, or whether its administrative and corporate associations have persisted.

The refreshed research package identifies eight public RIPE NCC evidence surfaces for AS210775: RDAP, the canonical aut-num object, an AS overview, announced prefixes, routing status, ASN neighbours, routing history and Whois. The endpoint map is documented across the relevant RDAP record, RIPE Database aut-num object, AS overview, announced-prefixes endpoint, routing-status endpoint, ASN-neighbours endpoint, routing-history endpoint and Whois endpoint.

But endpoint discovery is the first rung of an evidence ladder, not the last. A relevant URL tells a researcher where a claim could be tested. It does not supply the response body, retrieval timestamp, raw field, returned value or observation window needed to publish that claim as current fact.

What this run establishes

The current run establishes that these eight RIPE NCC endpoint types are the appropriate public surfaces for testing the administrative and operational status of AS210775. It also establishes that the refreshed research retrieval captured no live HTTP response bodies. That means the package cannot verify a current holder name, organisation reference, object status, creation or modification date, declared routing policy, originated prefix, route visibility value, neighbour list or historical activity period.

This is not a finding that the ASN is inactive. Nor is it proof that it is active. It is a finding about the state of the evidence: the relevant test surfaces were mapped, while the values needed to classify the resource were not captured.

That boundary matters because several superficially similar statements imply different levels of knowledge. “AS210775 has a registry endpoint” means a source location has been identified. “AS210775 is administratively registered to a named holder” requires a captured registry response with the relevant field. “AS210775 is operationally observed” requires a route-origin or visibility observation for a stated time window. “AS210775 is used by niceshops’ online services” requires an additional corporate or technical link; an ASN association alone does not prove service dependency.

The absence of a captured value must also be separated from a returned negative value. A response showing no qualifying prefixes for a stated observation window would support a carefully bounded statement about what that measurement saw. No response captured at all supports only the statement that the measurement was not completed in this run.

The continuity question after the earlier profile

The unresolved issue is not simply whether AS210775 still exists. It is whether continuity can be demonstrated across several layers that can change independently.

First is identifier continuity: is the same AS number still present in the relevant registry object, with the same or a changed status? Second is holder continuity: does the current organisation or referenced entity still correspond to niceshops Niceshops GmbH, or has the relationship changed? Third is policy continuity: does the current aut-num object contain routing-policy attributes, and are those declarations current? Fourth is route continuity: are any IPv4 or IPv6 prefixes currently originated by the ASN? Fifth is visibility continuity: are those routes visible through the relevant measurement system, and for what period?

Sixth is topology continuity: which adjacent ASNs are observed, and can those adjacencies be distinguished from contractual peering, customer or transit relationships? Seventh is corporate-use continuity: is there public evidence linking the network resource to the company’s actual services, facilities or operating architecture?

These questions must be answered with dates. A registry modification date is not a route observation date. A route observation is not proof of corporate ownership. A declared import or export policy is not an observed AS-path relationship. An observed neighbour is not automatically a commercial peer or transit provider. Each layer describes a different mechanism and should remain separate in the article and in future monitoring.

A practical evidence ledger

For operators and infrastructure readers, the useful output is an evidence ledger rather than a stronger adjective. Each future observation should record the source type, exact endpoint, retrieval time, HTTP or capture status, raw field, returned value and the sentence that the evidence permits.

For the administrative layer, that ledger should preserve the exact RDAP or RIPE Database object and identify the holder, organisation reference, status and event dates as returned. For the routing layer, it should preserve the announced-prefix response, the routing-status result and the effective measurement window. For the topology layer, it should record observed ASN adjacency without converting path position into a commercial relationship. For the historical layer, it should record first-seen, last-seen or interval data together with the collector and time boundaries.

For the corporate layer, it should identify the public company source and explain precisely how it connects, or fails to connect, the company’s services to AS210775.

The BTW directory entry for niceshops Niceshops GmbH remains the appropriate place to track the bounded subject profile. It should not be treated as a substitute for a current registry or routing response. The directory’s watchpoints—registry changes, BGP announcements and corporate network disclosures—are useful precisely because they identify the next evidence that would change the classification.

What would change the classification?

The first upgrade would be administrative verification: a successful current RDAP, Whois or aut-num capture with holder or object fields and a retrieval time. That would move the assessment from “endpoint mapped; value unverified” to “administratively verified; operationally unverified.” It would still say nothing by itself about whether routes are being originated.

The second upgrade would be operational observation: a successful route-origin or visibility result for a stated window. That would support “operationally observed,” but only for the observed period and measurement coverage. It would not establish continuous use or universal reachability.

A third state would be intermittent observation: dated, isolated or discontinuous routing observations with a defined method and interval. This could distinguish a network that appears sporadically from one that is consistently visible, but it would not justify calling the ASN a continuously operating network.

The strongest classification in this framework is continuity observed. That would require sustained dated routing and topology evidence, supported by relevant administrative and, where material, corporate linkage. The standard is deliberately higher because continuity is a claim about persistence across time and mechanisms, not a snapshot.

Why the distinction matters for niceshops

niceshops Niceshops GmbH operates in an online retail and fulfilment context, so network reachability is commercially relevant in the abstract. But the current evidence package does not establish the role AS210775 plays in that operating model. It does not show that the ASN carries the company’s storefronts, warehouse systems, APIs, customer traffic or partner connectivity. Nor does it show that activation of the ASN would automatically move those services onto a new routing path.

The mechanism is conditional. If the ASN were to originate prefixes used by company services, the announcement could alter how those prefixes are seen by networks and how the company depends on upstream connectivity. If the announcements were withdrawn, filtered, misconfigured or only intermittently visible, the effect would differ. If AS210775 remained a registry-only resource, its significance would remain latent rather than operational.

This is why the appropriate conclusion is narrower than a claim about network autonomy. The public record supports an investigation target and a monitoring design. It does not yet support a current operational profile.

Conclusion

AS210775 should currently be classified as an endpoint-mapped network resource whose present administrative and operational values remain unverified in this run. The key unanswered question is continuity: whether the identifier, holder, policy, route origination, visibility, topology, history and corporate use still align.

The next credible update will need more than a changed label or a newly found URL. It will need a captured response, a retrieval date, the exact returned field and a bounded explanation of what that field proves. Until then, the responsible reading is neither “active network” nor “dead asset,” but a registry endpoint awaiting operational evidence.