Summary
- The BTW directory fixes Raynet SAS as the exact company entry associated with AS206086, while RIPE RDAP links that number to a Raynet SAS registrant record in the administrative layer.
- A frozen RIPE RIS response reports zero listed-peer visibility, zero announced space and zero observed neighbours for its stated query, but those endpoint-, product-, collector- and time-bounded fields do not establish universal unreachability, shutdown or loss of control.
- Hurricane Electric independently pairs AS206086 with the Raynet SAS name; that identity corroboration does not by itself prove a current route, authorization, traffic, topology, capacity or service state.
One ASN connects records with different purposes
The Border Gateway Protocol allows independently operated networks to exchange information about which internet address blocks they can reach. An autonomous system groups routing decisions under a common policy, and its ASN gives researchers a precise number to use across datasets. That number is especially useful when a company name might be abbreviated, punctuated differently or shared with an unrelated organisation.
AS206086 joins the evidence in this briefing. The BTW directory establishes the public subject. RIPE's Registration Data Access Protocol, or RDAP, identifies the administrative number object and its linked registrant. RIPE RIS provides one frozen routing-status response. Hurricane Electric provides an independently maintained BGP profile. Agreement on the number and name reduces the risk of attaching records to the wrong subject.
Agreement does not make the records interchangeable. A directory page is not a route monitor. A registration object is not an authorization decision. A collector-derived response is not a test from every network. A BGP profile title is not proof that a service is available. The most useful account therefore begins with the role of each source rather than combining their fields into one score.
The directory fixes the subject
The exact BTW directory route returned HTTP 200 at the requested address. Its final address and canonical address matched that route, its H1 was Raynet SAS, and its page title identified a Raynet SAS network-infrastructure profile. The page allowed indexing and following, and AS206086 appeared in its rendered content.
Generic application bytes included phrases associated with missing-page handling, but the page itself was not a soft 404. The exact URL, canonical, H1, title and visible ASN all described the expected subject. That combination makes the directory useful for identity and navigation.
The directory entry classifies Raynet SAS as a company and links it to AS206086. That is the scope of the evidence. The page does not independently establish who may originate a route, which equipment exists, where infrastructure is located, whether customers are connected, or whether any service is operating at a particular moment.
RIPE RDAP supplies the administrative ledger
The RDAP response for the number is an autonomous-system object whose handle is AS206086. Its starting and ending values are both 206086, so the object covers exactly the ASN used throughout this briefing. Its registry name is RAYNET-AS, and it points to registrant handle ORG-RS142-RIPE.
The linked RIPE entity record identifies an organisation and gives its formatted name as Raynet SAS. The two records therefore provide an exact administrative bridge: the autnum object identifies the number, and the referenced organisation object identifies the registrant name. No looser company-name search is needed to make that connection.
Registration data matters because unique and accurate number-resource records support coordination, investigation and the recording of changes. Its authority is administrative, however. The record does not say that a route was visible at the time of the routing query. It does not decide whether an announcement was authorized. It does not prove ownership of physical assets, a contractual relationship, traffic volume, uptime or customer experience.
Treating the registry as a ledger preserves its value. It gives a durable identity layer against which observations can be checked, while leaving operational questions to evidence built for those questions. A registry record can remain meaningful even when a routing observation changes, because the two systems describe different aspects of the same number resource.
The frozen RIPE RIS response reports a bounded view
RIPE RIS collects BGP data from participating observation points and publishes products derived from those views. The captured routing-status response for AS206086 records a query time of 7 August 2026 at 16:00 UTC. Its response time is 8 August 2026 at 00:18:50.406538 UTC. Those timestamps are essential: the values belong to one response and should not be described as timeless.
The response's messages array is empty. This matters because no threshold or low-visibility exclusion rule can be attributed to this capture. A different response or product might explain filtering, but this one supplies no such message. The safest description is therefore limited to the fields actually returned.
For IPv4, the visibility object reports zero of 327 listed RIS peers seeing routes in the response. For IPv6, it reports zero of 321. Announced-space fields are zero IPv4 prefixes and zero IPv4 addresses, along with zero IPv6 prefixes and zero equivalent /48 blocks. The observed-neighbours field is also zero.
These are real returned values, but their meaning is bounded by the endpoint, product, collector population and time. Zero listed-peer visibility does not demonstrate that every possible network lacked a route. Zero announced space in this response does not prove that Raynet SAS had shut down, abandoned the ASN, transferred it or lost control. Zero neighbours does not measure contracts, private sessions or physical connectivity. The response does not diagnose an outage or a customer-facing service.
First seen and last seen do not prove continuity
The routing-status response also selects historical fields for one prefix. Its first_seen field names 194.156.24.0/24, origin 206086, at 20 June 2017, 16:00 UTC. Its last_seen field names the same prefix and origin at 25 November 2025, 08:00 UTC.
Using the same prefix at both endpoints makes the pair easy to read as a continuous interval, but the response does not support that inference. Two selected timestamps do not describe every moment between them. They do not reveal gaps, route changes, collector coverage, policy changes or events outside the endpoint's method.
A continuity claim would require a time series with stated vantage points and a method for handling missing observations. An authorization claim would require evidence designed for authorization. A service claim would require measurements tied to the named service and interval. The two historical fields alone answer none of those questions.
The final date also should not be used to calculate an outage duration. The frozen response reports when its selected route was last seen within the product's data, not why later fields are zero or what every external observer could see. A date difference is not a diagnosis.
Hurricane Electric corroborates identity, not operations
Hurricane Electric's exact page for AS206086 returned HTTP 200 and carried the title AS206086 Raynet SAS - bgp.he.net. That independently corroborates the pairing of the ASN with the Raynet SAS name outside the BTW directory and RIPE registry chain.
The role of that page in this briefing is deliberately narrow. No prefix total, peer count, graph, path or operational conclusion is imported from it. Its title does not prove that a route was visible at the RIPE RIS query time. It does not establish authorization, topology, traffic, capacity, resilience, uptime or service health.
RIPE RDAP registration, the frozen RIPE RIS response and Hurricane Electric's BGP profile are separate evidence layers; none alone proves current route authorization, universal reachability or unreachability, capacity, physical-asset ownership or service status.
Keeping the independent profile in that role avoids a common error: treating several websites that repeat an ASN-name pair as several independent measurements of network operation. Identity corroboration is useful, but repeated identity is not repeated evidence about routing or service.
Administrative presence and observed zeros can coexist
There is no contradiction between an administrative record that identifies Raynet SAS and a frozen routing response containing zero values. The sources describe different systems. RDAP answers how a number resource is recorded. RIPE RIS reports what its product returned from its observation environment for a stated query. Hurricane Electric corroborates a public ASN-name pairing.
The disciplined conclusion is neither that the registry overrides the observation nor that the observation invalidates the registry. Both remain evidence within their boundaries. The registration chain supports identity. The routing response supports a precise statement about one captured result. The independent profile supports an additional identity check.
That separation is also practical. If a researcher needs to ask whether a route was authorized, the next evidence should concern authorization. If the question is reachability, the next evidence should include time-aligned measurements from appropriate vantage points. If the question is service condition, the next evidence must be tied to the service and interval. Repeating an administrative lookup cannot answer those operational questions.
A practical verification sequence
Start with exact identity. Confirm the directory subject, entity classification, ASN, RDAP handle, number range and linked registrant. This guards against joining observations to a similarly named organisation or to the wrong autonomous system.
Next, freeze the routing response as bytes and retain its resource, query time, response time, messages, address-family numerators and denominators, announced-space fields, neighbour field and historical prefix timestamps. If every value is zero, preserve the zeros without supplying an explanation that the endpoint did not provide.
Then compare only like with like. A later routing response can show a different observation, but the comparison should disclose its product, time and vantage conditions. Movement in a live field does not rewrite the earlier captured result. A registry change should be evaluated as a registry change rather than treated as proof of an operational event.
Finally, choose evidence that matches the remaining question. Route-origin authorization material can inform an authorization inquiry. A route-history series can inform continuity analysis. Direct, time-bound operational records can inform a service investigation. Each additional source should narrow one question rather than inflate a general impression.
What these records do not establish
The four sources support a narrow account of Raynet SAS's directory identity, the RIPE administrative chain for AS206086, one frozen RIPE RIS response and one independent ASN-name profile. They do not establish universal reachability or unreachability. They do not establish a current outage, shutdown, abandonment, transfer or loss of control.
They also do not establish route-origin authorization, legal ownership, permission or jurisdiction. None of the admitted fields measures traffic, capacity, latency, physical topology, diversity, resilience, uptime or customer outcomes. The records do not establish customers, facilities, equipment, a service footprint, business scale or market position.
The zero values deserve the same discipline as positive-looking values. They should not be hidden, softened or replaced. They should be reported with their denominators, timestamps and source. But they should not be made to answer questions that the endpoint did not measure.
What to watch
Later checks should preserve the same evidence boundaries. A registry review can look for changes to the exact autnum object or linked registrant. A routing review can compare product outputs only when the resource, timestamps, messages, peer denominators and address families remain visible. An independent profile can corroborate identity without being promoted to a live-route test.
The strongest next step depends on the question. Authorization needs authorization evidence. Continuity needs an appropriate time series. Reachability needs time-aligned observations from relevant vantage points. Service condition needs service-specific telemetry. Until such evidence is collected, the precise conclusion is modest: public records align on Raynet SAS and AS206086, while the frozen routing response reports bounded zero values that do not explain themselves.