Summary

  • The BTW directory fixes the exact subject associated with AS57611, while RIPE NCC RDAP records the one-number ASN object, the registry name ROMGAZ-AS and the exact registrant name.
  • A frozen RIPE RIS response reports IPv4 visibility among zero of 327 listed full-feed peers, IPv6 visibility among zero of 322, no announced space and zero observed neighbours; these product-, collector- and time-bounded values are not a universal network verdict.
  • CAIDA AS Rank independently matches AS57611 with ROMGAZ-AS, but its seen, rank, cone and degree fields remain bounded to that dataset and do not prove route authorization, ownership or service status.

One ASN connects records with different jobs

BGP is the protocol independently run networks use to exchange information about which internet address blocks they can reach. An autonomous system groups routing decisions under a common policy, and its ASN distinguishes that routing domain from others. Organisation names can be long, abbreviated or written differently across systems. The number provides a less ambiguous join key.

AS57611 connects four public evidence layers in this briefing. The BTW directory establishes the chosen subject and a navigation path. RIPE NCC's Registration Data Access Protocol, or RDAP, provides a structured administrative record for the number resource. RIPE RIS supplies a frozen observation derived from routing collectors. CAIDA AS Rank supplies a separately processed, BGP-derived profile.

Agreement on the ASN and the ROMGAZ-AS registry name reduces the risk of attaching records to the wrong subject. Agreement does not make the sources interchangeable. A directory is not a route monitor, an administrative object is not an authorization decision, a collector response is not an end-to-end reachability test, and a derived profile is not proof of live operations.

That separation is the central reading rule. Each source remains useful when it answers the question it was designed to answer. Trouble begins when an administrative label, an observation counter or a profile field is stretched into a broader operational conclusion.

The directory establishes the subject

The captured BTW directory route rendered the exact H1 SOCIETATEA NATIONALA DE GAZE NATURALE ROMGAZ SA and visibly displayed AS57611. The requested address, final address and canonical address matched, and the page did not meet the bounded checks for a page-level soft 404. Those details make the page useful for identifying the exact subject of this briefing.

The directory does not independently establish whether a route was announced, accepted or authorized at any moment. It does not measure reachability, traffic, latency or service availability. Nor does it prove ownership of routers, address space or other physical assets. Its role is narrower and still important: it fixes which directory identity the other evidence is being compared with.

This distinction matters because a name match alone can be weak. An ASN visible beside the exact subject provides a stronger key for checking whether administrative and routing-oriented records concern the same number. It is an identity bridge, not an operational diagnosis.

RIPE NCC RDAP is an administrative ledger

The captured RIPE NCC response describes an autnum object whose starting and ending values are both 57611. Its handle is AS57611, its registry name is ROMGAZ-AS, and its status array contains active. The one-number range removes any need to infer which ASN the object covers.

The registrant handle is ORG-SNDG2-RIPE, and the corresponding name is the same full subject shown in the directory. The exact ASN and exact registrant name make the administrative bridge unusually direct.

The word active belongs to the administrative object. It does not say that a route was visible to a particular collector, that an origin was authorized, or that a service was reachable. It does not establish legal ownership, operating control or permission to announce a prefix. Those questions require evidence designed for routing, authorization, legal or operational analysis.

Treating RDAP as a ledger preserves its value. Accurate number-resource records help with uniqueness, coordination and the recording of changes. An administrative object can remain active while routing observations vary because the registry and the routing system describe different layers. A stable registry entry is therefore compatible with a frozen observation containing zero qualifying values.

The RIPE RIS result is a frozen observation

RIPE RIS collects BGP information from participating observation points and publishes derived data products. The frozen routing-status response used here retained a query time of 8 August 2026, 00:00 UTC and a response time of 8 August 2026, 05:27:27.608973 UTC. Keeping both timestamps prevents its returned fields from being treated as timeless.

Its messages array was empty. The response therefore supplied no threshold or exclusion notice to carry into the interpretation. This briefing does not invent one. It reports the denominators and fields exactly as they appeared in the captured product.

For IPv4, qualifying visibility was zero of 327 listed RIS full-feed peers. For IPv6, it was zero of 322. The announced-space fields reported zero IPv4 prefixes and zero IPv4 addresses, together with zero IPv6 prefixes and zero equivalent /48 blocks. The observed-neighbours field was also zero.

These figures describe one endpoint's product, collector set and timestamps. They do not prove that every possible vantage point saw no route, that no private path existed, or that every destination was unreachable. They also do not identify a cause. A zero returned by a routing-status product cannot, by itself, distinguish among routing policy, filtering, collector coverage, a deliberate absence of announcements or another condition.

Zero is a measurement, not a diagnosis

The safest way to read the visibility values is to retain both numerator and denominator. “Zero of 327 listed peers” is more precise than “not visible,” because it identifies the observation population. Keeping IPv4 and IPv6 separate also avoids turning a result for one address family into a claim about the other.

The announced-space and neighbour counters require the same restraint. They do not measure traffic, capacity, latency, route preference, physical topology, diversity, resilience, uptime or customer experience. They do not prove a shutdown, abandonment, transfer or loss of control. A route-origin authorization question would require appropriate authorization material, while a service question would require evidence tied to the affected service and interval.

This does not make the observation uninformative. The frozen response records exactly what the named product returned under a documented query and capture time. That is a reproducible statement about the evidence package. The disciplined conclusion is bounded rather than dramatic: the captured RIPE RIS routing-status fields were zero on their stated observation surface.

First seen and last seen are historical endpoints

The response also contains historical fields. Both first_seen and last_seen select 91.233.106.0/24 with origin 57611. The first timestamp is 13 December 2011, 16:00 UTC; the last is 18 April 2019, 08:00 UTC.

The prefix is the same, but that does not make the two endpoint-selected timestamps a continuous operating interval. The fields do not describe every announcement associated with the ASN, explain any gaps, or establish how collector coverage changed between the endpoints. They also do not say that a service was continuously available.

A defensible continuity analysis would need a purpose-built time series, stated vantage points and an explicit method for handling gaps. A service-continuity finding would need additional service-specific records. The two fields here support only two historical observations selected by the endpoint.

CAIDA AS Rank corroborates identity

The frozen CAIDA AS Rank profile identifies ASN 57611, gives the name ROMGAZ-AS, names RIPE as the source and records country code RO. The exact ASN and registry-style name provide an independent BGP-derived identity match.

The same response records seen=false, rank 79459, one ASN in the customer-cone field, zero cone prefixes, zero cone addresses and total degree zero. These are outputs of CAIDA's dataset and processing. They are not universal measurements of the entire routing system and cannot establish that a route, network or service was absent everywhere.

The profile's role is therefore twofold but bounded. It strengthens confidence that AS57611 and ROMGAZ-AS are the intended record, and it preserves a frozen set of dataset fields. It does not prove announcements, authorization, peerings, traffic, facilities, capacity, physical ownership or service availability.

Active, zero and seen-false answer different questions

RIPE NCC's active status, the RIPE RIS zero counters and CAIDA's seen=false field can look contradictory if they are read as one health score. They are not contradictory. The registry status describes an administrative object. The routing-status response describes a product observation at stated times. CAIDA supplies a separately processed profile with its own coverage and method.

RIPE NCC RDAP registration, the frozen RIPE RIS response and CAIDA AS Rank's BGP-derived profile are separate evidence layers; none alone proves current route authorization, universal reachability or unreachability, capacity, physical-asset ownership or service status.

The ASN is what allows these layers to be compared carefully. It provides continuity of reference, not authority for one source to answer every question. Keeping the layers separate is not excessive caution; it is what makes each record useful without overstating it.

A practical verification sequence

Start with identity. Confirm the exact directory subject, visible ASN, RDAP range and handle, registrant name, and independent profile identity. If those elements do not align, stop before combining facts from the sources.

Next, freeze observational evidence with its endpoint, query time, response time, messages, address family, numerator and denominator. Preserve raw response bytes when possible. Keep historical timestamps attached to the prefix that the endpoint selected.

Then match evidence to the question. For authorization, inspect relevant authorization material rather than inferring from RDAP status. For visibility, compare time-aligned observations from stated vantage points. For continuity, use a route-history method that handles gaps. For service condition, use end-to-end measurements and system records tied to the service and interval.

This sequence helps researchers decide what evidence to gather next. It also prevents a public ASN record from being used as a diagnosis for an application dependency, customer connection or outage that none of these sources measured.

What the records do not establish

The four public sources support a narrow account: an exact directory identity, the RIPE NCC administrative object for AS57611, one frozen RIPE RIS response and one independent CAIDA profile. They do not establish universal reachability or unreachability, route-origin authorization, legal ownership, permission or jurisdiction.

They do not establish a present outage, shutdown, abandonment, transfer or loss of control. They do not establish customers, facilities, equipment, service territory or physical topology. None of the admitted fields measures traffic, capacity, latency, diversity, resilience, uptime or customer outcomes.

The records also do not explain why the frozen counters were zero or why CAIDA returned its dataset fields. Any explanation would require additional evidence matched to a specific hypothesis. The responsible result is to preserve the captured values, identify their boundaries and avoid substituting a narrative for missing measurements.

What to watch

Later checks should keep the same evidence roles. A registry review can examine whether the exact ASN range, handle, registrant or object status changes. A routing review can compare observations only when it preserves product identity, timestamps, peer denominators and address-family separation. A derived-profile review can track identity and dataset changes without treating the profile as proof of operations.

The strongest next evidence would answer a defined open question: authorization data for an origin claim, a time series for route history, additional collector views for visibility, or service-specific telemetry for an operational finding. Until such evidence is available, the precise conclusion remains modest. The public records align on the directory subject and AS57611, while the administrative registry, frozen routing observation and independent BGP-derived profile continue to describe distinct layers.

Sources