Summary

  • APNIC RDAP records AS136922 with the name AWPL-AS-AP and the description WELLS RESEARCH PTY LTD T/A Anttel Wholesale, preserving a specific administrative attribution for the number resource.
  • The registrant organisation is recorded as ORG-WRPL1-AP, displayed as Anttel Wholesale, while the administrative and technical role WRPL1-AP uses the longer WELLS RESEARCH PTY LTD TA Anttel Wholesale name.
  • The captured RIPEstat overview reports announced=false, and its current announced-prefix response contains no prefixes attributed to AS136922.
  • RIPEstat’s routing-status response reports no visible announced IPv4 or IPv6 space, no observed neighbours, and visibility at zero of 328 reporting IPv4 peers and zero of 322 reporting IPv6 peers.
  • Those zeroes form a consistent public-routing observation, but they do not prove absence from every collector, private network, bilateral interconnection or service arrangement.
  • An active status in the APNIC record describes the registry object. It must not be converted into a claim that a commercial service, customer network or public route is operational.
  • Conversely, public routing silence does not establish company closure, permanent ASN inactivity, an outage, customer impact, asset disposal or the cause of the silence.
  • The useful accountability finding is narrower: a named registry identity persists for AS136922 even though its selected public running-state observation is silent, leaving a durable steward against which future routing or registry changes can be assessed.

Two evidence layers describe one number resource

AS136922 presents two public facts that can look contradictory when read without context. APNIC retains an administrative record for the autonomous system number and ties it to WELLS RESEARCH PTY LTD T/A Anttel Wholesale. RIPEstat, in the captured running-state view, reports that the ASN is not announced. One system supplies a named identity; the other supplies an empty current routing surface.

There is no necessary contradiction. A regional internet registry and a routing-observation platform answer different questions. The registry records which organisation is associated with a unique number resource and preserves the fields used to administer it. A routing platform observes whether that number appears in routes visible through its data sources. Registration is an attribution layer. Public BGP visibility is an operational observation.

Those layers often align. When an ASN originates prefixes that public collectors can see, its registry identity and running state can be examined together. Alignment is useful, but it is not guaranteed. A registry record does not require every assigned ASN to be continuously visible in public routing, and the disappearance of an ASN from a selected routing view does not automatically erase its administrative record.

The distinction matters because each layer has a different authority. APNIC is the stronger source for the recorded name, handle, country field, roles and number-resource status. RIPEstat is the stronger source for the captured public-routing observation. It would be an error to ask the APNIC record to prove current packet forwarding. It would be equally mistaken to ask an empty routing view to decide who is recorded as responsible for the ASN.

The correct account therefore preserves both facts in full. AS136922 remains recorded under the Anttel Wholesale identity. At the captured query boundary, RIPEstat did not show a public announcement from it. Neither fact cancels the other, and neither should be inflated into a complete description of the company.

That separation creates a useful form of accountability. A future announcement can be compared with a known ASN and a named registry identity. A future registry change can be distinguished from a change in routing state. Until either occurs, the public record supports a precise baseline without supplying a causal explanation.

APNIC preserves a specific administrative identity

The APNIC RDAP response identifies the number resource as AS136922. Its network name is AWPL-AS-AP, and its descriptive organisation label is WELLS RESEARCH PTY LTD T/A Anttel Wholesale. The country field is AU, placing the record in an Australian administrative context within the APNIC service region.

Exact naming is important. The linked company identity appears as WELLS RESEARCH PTY LTD TA Anttel Wholesale, while the RDAP description uses T/A. Both refer to the same Anttel Wholesale identity within the accepted evidence. For readability, Anttel Wholesale is a reasonable short reference, but the longer registry wording should remain visible where attribution matters.

The RDAP object names ORG-WRPL1-AP as the registrant organisation and displays it as Anttel Wholesale. It separately associates WRPL1-AP with administrative and technical roles under the display name WELLS RESEARCH PTY LTD TA Anttel Wholesale. These fields are more useful than a loose similarity between brand names because they connect the ASN to specific registry objects and roles.

The record also carries an active status. That term has to be read within the system that supplies it. It indicates the recorded status of the number-resource object; it does not certify that AS136922 is currently originating a prefix, forwarding public traffic or delivering a service. The captured RIPEstat data demonstrates why that distinction is necessary: the registry object can be active while the observed public routing state is silent.

The reverse mistake would be to treat routing silence as proof that the APNIC identity is obsolete. The registry record still distinguishes AS136922 from every other autonomous system number and retains the organisation and role information associated with it. Unless the registry changes, that administrative attribution remains the appropriate public reference for stewardship questions concerning this ASN.

Registry contacts require similar restraint. Administrative, technical and abuse roles provide channels and responsibility labels within the registry structure. Their presence does not prove that every mailbox is currently monitored, that a particular person is available, or that an operating team is maintaining a live network around the clock. Those questions require their own evidence.

Even so, structured contact metadata is not trivial. It gives other operators and researchers a place to begin when an ASN returns to routing, becomes relevant to an incident or requires clarification. The value lies in preserving a traceable responsibility surface, not in assuming operational performance from the existence of the fields.

APNIC’s role is thus both important and bounded. It records the uniqueness and attributed stewardship of AS136922. It does not reveal the reason for the empty routing observation, the company’s current legal condition, its service catalogue, its infrastructure or its customer relationships.

RIPEstat reports a consistently silent current view

The captured RIPEstat overview marks AS136922 as announced=false. That is the clearest high-level statement in the routing evidence: the platform did not classify the autonomous system as currently announced at the query boundary represented by the response.

A second endpoint supplies a more concrete check. Its announced-prefix array is empty. There is no current IPv4 or IPv6 prefix listed as being originated by AS136922 in that response. The empty array supports the overview flag rather than contradicting or complicating it.

Routing status adds further detail. It reports no visible announced IPv4 space and no visible announced IPv6 space. It also reports no observed neighbours. Peer visibility is zero among the 328 reporting IPv4 peers represented in the response and zero among the corresponding 322 IPv6 peers.

Together, these fields describe a coherent observation. The platform does not show an ASN that is visible in one address family but not the other. It does not show a prefix that somehow failed to affect the overview flag. It does not report a residual neighbour relationship while the prefix list is empty. Across the selected endpoints, the current state points in one direction: no public routing presence was visible for AS136922.

The consistency gives the observation weight within its scope. A single failed lookup or blank presentation could result from many mundane problems. Here, several related fields agree: not announced, no prefixes, no announced address space, no visible peers and no neighbours. That agreement supports a firm description of what RIPEstat reported.

Scope remains decisive. RIPEstat’s figures describe the platform’s view, not every router on the Internet. The peer denominators show the size of the reporting set represented by the response; they do not turn that set into universal coverage. Zero of 328 IPv4 peers and zero of 322 IPv6 peers is meaningful, but it is still zero within an identified observation system.

The empty first_seen and last_seen objects in the captured routing-status response also require care. They provide no dated route endpoint in that response from which to construct a public-routing chronology. They do not prove that AS136922 was never announced, and they do not establish permanent inactivity. They simply leave those historical fields empty at the query boundary.

This means the current evidence is stronger on state than on history. It supports a dated observation that no current announcement was visible. It does not establish when any earlier route began, when it ended, whether routing was intermittent or whether another observation system retained historical sightings.

A restrained account does not weaken the routing finding. It makes it more durable. Future observers can repeat the same checks and compare like with like: overview status, prefix count, IPv4 and IPv6 visibility, peer denominators and observed neighbours. If any field changes, the change can be recorded without rewriting the earlier observation into something it never claimed to prove.

What the routing zeroes leave unresolved

The announced-prefix endpoint answers a narrow technical question: which prefixes does the platform currently associate with AS136922 as an origin? In the captured response, the answer is none. That fact is concrete. The reason for it is not present.

Public BGP silence can be described without assigning a cause. “No current announced prefix was visible” is supported. “The company stopped operating” is not. The latter would require evidence about the organisation, its decisions and its wider network arrangements that the prefix response does not contain.

The same boundary excludes an outage claim. An outage is not merely an empty row in a routing dataset. It implies that a service expected to be available became unavailable, usually with a duration, an impact and a technical or organisational cause. None of those elements appears in the accepted evidence for AS136922.

There is no verified customer list, service-level commitment, incident notice, traffic series or operator statement connecting the ASN’s current silence to a loss of service. Without that context, a routing observation cannot establish whether any customer expected AS136922 to be visible at the time. Permanent inactivity is also beyond the record: the response represents a point in time, and the current sources contain no authoritative declaration that the ASN has been retired.

Nor does the empty response prove absence from every technical environment. Public BGP collection does not expose all private routing, internal addressing, bilateral sessions or arrangements in which another ASN originates the relevant addresses. This is not evidence that any such arrangement exists for Anttel Wholesale. It is the boundary that prevents a public observation from becoming a universal negative claim.

Peer visibility figures can appear definitive because they contain precise denominators. Zero of 328 IPv4 peers and zero of 322 IPv6 peers is more informative than an undifferentiated statement that an ASN was “not seen.” It shows that the platform counted a substantial reporting population and found no visibility for AS136922 within it.

The figures still describe observation, not omniscience. A reporting peer is part of the platform’s measurement surface. It is not every possible transit provider, exchange participant, private peer, enterprise edge or internal router. The denominator tells readers how broad the represented view was; it does not authorise a claim about every location from which a route might theoretically be visible.

Neighbour data has a similar limit. No observed neighbours means that the routing-status response did not identify an adjacent autonomous system for AS136922 at the captured boundary. It does not prove that Anttel Wholesale has no contractual relationship with another network, no private session or no technical dependency. Contracts and private interconnections are not automatically exposed as public BGP adjacency.

The neighbour result is nevertheless useful. Publicly observed neighbours are one way to understand how an ASN reaches the wider routing system. When the count is zero alongside an empty prefix response and zero peer visibility, the selected data offers no present public handoff surface to examine. Outsiders cannot use the cited snapshot to identify a current upstream, peer, downstream or origin prefix, or trace a visible path from AS136922 into the public routing system.

This is where precise language matters most. “No neighbour was observed” is defensible. “The network has no neighbours” is broader. “No public route was visible among the reporting peers” is supported. “The ASN is absent everywhere” is not.

Chronology is equally bounded. Empty first_seen and last_seen objects supply no supported start date, last visible prefix or withdrawal date. They must not be converted into “never seen,” and they do not establish how long AS136922 had been silent before the query or whether the state was intermittent.

The evidence therefore cannot support causal sequencing. It does not show that a company event preceded a withdrawal, that a registry update followed one, or that any specific decision produced the current state. A disciplined baseline records the source, numerator, denominator and observation boundary together, while leaving the unexplained interval open.

Registry status and running state answer different questions

The APNIC record preserves attribution over time. That is one of the central purposes of a number-resource registry: an autonomous system number should remain uniquely identifiable, associated with a recorded organisation and accompanied by administrative metadata. Public routing, by contrast, can change much faster than a registry identity.

This difference in tempo explains how the two layers can coexist. The registry is not a continuously updated transcript of route propagation. It is not expected to change its organisation name each time a route is announced or withdrawn. Likewise, routing collectors do not wait for registry changes before recording what they can see in BGP.

A durable entry can therefore outlast a visible announcement without becoming false merely because the route is quiet. It still answers the administrative question of which entity is recorded against the resource. That is valuable for uniqueness, contact, security coordination and any future change in use.

But durability is not the same as operational continuity. The APNIC status and contact fields do not demonstrate that routers are configured, that prefixes are accepted by upstreams, that a network operations team is active or that traffic is being carried. Those are running-state questions.

The phrase “operational continuity” should be used with particular care. The registry helps preserve the continuity of attribution: the number does not become an anonymous string when it is not visible in BGP. It does not prove uninterrupted network service, staffing, commercial activity or public reachability. The recorded Australian country context likewise locates the resource within its administrative record; it does not establish the physical location of equipment, the geographic scope of a service or the location of customers.

For questions about present public routing, observed running state deserves priority over administrative implication. The fact that AS136922 is registered does not justify describing it as currently announced. The captured RIPEstat responses are the relevant evidence, and they report no visible route.

This principle prevents a common shortcut. A registry entry may look complete because it has a number, name, country, roles and status. That completeness can be mistaken for proof that the associated network is live. Yet a well-formed record and a running routing domain are different things.

Running-state priority is domain-specific. RIPEstat cannot replace APNIC as the authority for the recorded registrant, decide the legal status of WELLS RESEARCH PTY LTD, establish ownership of equipment or reveal contracts that never appear in public BGP. When asking whether the ASN was publicly visible at the observation boundary, inspect routing evidence. When asking who was recorded against it, inspect the registry. Other questions require evidence designed for their own domain.

The word active illustrates the distinction. In the APNIC response it belongs to the state of the registry object; it does not mean that public routes are active. APNIC can record AS136922 as active while RIPEstat reports it as not announced because the two labels describe different systems.

Reading active as proof of public operation would dismiss the empty prefix and peer data, giving administrative metadata authority over running state it was not designed to exercise. Reading not announced as proof that the registry object should no longer exist would give a routing platform authority over stewardship it does not possess.

The more accurate reading is procedural. AS136922 remains a live object in the number-resource ledger, associated with Anttel Wholesale. At the same time, it has no current public routing surface in the captured RIPEstat view. A future registry status change would be an administrative event; a future prefix announcement would be an operational event. Each should be dated and evaluated through its own source.

No legal corporate conclusion follows automatically from either layer. APNIC can retain an accurate administrative association while remaining outside the authority needed to decide incorporation, cancellation, insolvency or corporate control. A quiet route table is equally unable to decide those questions. Respecting that division allows both sources to remain useful without turning either into an all-purpose corporate record.

Accountability persists when the route table is quiet

A silent routing surface does not eliminate accountability. The APNIC record continues to attach AS136922 to a named organisation, giving the number a durable administrative context even when no current route can be examined.

That context is useful if the ASN becomes visible again. A new announcement would not appear as an unattributed technical event. Observers could compare the origin number with the existing Anttel Wholesale record, examine whether the registrant and roles had changed, and assess the new prefixes and neighbours on their own terms.

The record is also useful when questions arise during silence. An operator, researcher or prospective counterparty can identify the registry roles associated with the ASN and ask whether it is dormant, reserved, no longer used for public routing or expected to return. Those are questions for the recorded steward; the registry itself does not answer them.

Accountability should not be confused with blame. There is no evidence here of misconduct, service failure or an unmet obligation. The existence of a named steward merely prevents the number resource from becoming analytically detached from its administrative identity.

The same distinction applies to security metadata. Registry roles and an abuse contact can provide a coordination path. Their presence does not prove response times, staffing levels or the current operation of a security programme. Their absence from routing is not itself a security incident.

An accurate public record allows uncertainty to be assigned rather than hidden. The known identity belongs to the administrative layer. The known silence belongs to the routing layer. The reason for the difference remains unknown. This structure tells readers exactly where additional evidence would need to come from.

It also avoids the opposite error of treating an unannounced ASN as irrelevant. Number resources can matter before, during and after visible routing events. Historical attribution, later reuse, contact changes and transfers all depend on maintaining clear records even when the current route table offers nothing to inspect.

AS136922 therefore remains an accountability surface despite its public silence. That is a narrower claim than operational activity and a more defensible one than corporate failure.

The linked identity sets scope, not operational proof

The linked company entry identifies WELLS RESEARCH PTY LTD TA Anttel Wholesale, the same organisational identity connected to AS136922 in the APNIC evidence. That alignment helps readers distinguish the subject from unrelated companies or similarly named services.

Its value is identity resolution. It provides a stable place to understand which company this analysis concerns and avoids inventing a new entity merely because the registry uses the T/A punctuation variant. The readable short name Anttel Wholesale remains anchored to the longer recorded identity.

The directory entry does not independently prove facilities, network capacity, geographic coverage or current service delivery. A company identity can be accurate even when those operational details are unavailable. Treating the entry as a service certificate would exceed its role.

It also does not establish current legal status. Questions about incorporation, cancellation, insolvency or corporate control require current official corporate-registry evidence. The APNIC and directory identities should not be stretched to answer them.

Nor should the company identity be collapsed into the ASN. AS136922 is one number resource associated with Anttel Wholesale in the accepted evidence. It is not a complete map of every network, supplier, private arrangement or technical asset the organisation may use. The absence of a public route from this ASN cannot be applied automatically to the company as a whole.

The reverse is equally important. Any wider company activity would not prove that AS136922 itself is announced. Present public routing must still be demonstrated through the number’s observable state. Identity linkage and operational linkage remain separate questions.

An autonomous system number is also a routing identifier, not a catalogue of physical assets. Even a clearly visible ASN would not, by itself, prove ownership of fibre, spectrum, data centres, towers, racks, customer-premises equipment or other infrastructure. A silent ASN reveals still less.

No facility claim can be derived from the APNIC record. Registry names, role objects and country fields do not identify buildings or establish who owns them. They do not document power arrangements, interconnection capacity, resilience, staffing or physical security. The routing responses offer no such evidence either: prefixes and neighbours can show aspects of public routing when present, but they do not establish property ownership.

Coverage is outside the evidence as well. The AU country field supplies an administrative context for the ASN; it is not a service-area map. It does not establish national, regional or local reach, and it cannot show where any customer might receive connectivity.

Capacity and resilience cannot be assessed. No traffic volume, port speed, prefix utilisation, customer count, interconnection size, upstream set, redundant path, facility or failure domain appears in the accepted sources. Zero visible routing cannot be translated into zero installed capacity, just as a registry entry cannot be translated into a capacity figure.

Keeping these boundaries intact focuses the assessment on the control surface that is actually visible: a registered ASN with no current public route in the selected observation. That is enough for a useful accountability finding without turning the article into an unsupported company or infrastructure profile.

Public silence does not establish customer impact

Customer impact requires evidence about customers, services and expectations. None of those is identified in the accepted record for AS136922. The routing observation therefore cannot support a claim that anyone lost access, experienced degradation or faced an outage.

An ASN may be important to service delivery, but importance has to be demonstrated. A current origin prefix, dependency map, customer statement or operator disclosure could help establish the relationship. Here, the current prefix set is empty, and there is no independent customer evidence.

Even if a route had disappeared between two observations, the effect would depend on the surrounding design. Traffic might have moved to another origin, a service might not have relied on the ASN, or the number might not have been expected to announce at that time. These are generic possibilities, not explanations for AS136922. The evidence does not select among them.

That is why the word “outage” would be too strong. It converts a routing-state observation into a service-state conclusion. The data shows no route from AS136922 in the captured view; it does not show an interrupted customer session, failed application, unreachable destination or breached service commitment.

“Degraded service” would be unsupported for the same reason. There is no performance measurement, latency series, packet-loss report or before-and-after traffic comparison. An ASN can be either visible or silent in a routing dataset without that dataset measuring the quality of any commercial service.

Closure claims extend even further beyond the evidence. Company closure is a legal and organisational condition. It cannot be inferred from one number resource’s public-routing state, especially when APNIC still preserves the administrative record and no corporate-registry source is present.

The appropriate public-interest question is not whether silence proves harm. It is what the silence prevents outsiders from verifying. In the current snapshot, they cannot identify a public prefix or neighbour for AS136922, and they cannot examine a visible routing role. That is an observability limit, not an impact finding.

A prospective counterparty may reasonably seek clarification because of that limit. The relevant questions concern which ASN and prefixes would support an offered service, who is responsible for routing, and what public or contractual evidence describes the operating boundary. Asking those questions does not imply that a failure has occurred.

A practical diligence sequence starts with identity, then operation

A useful investigation of a quiet ASN begins by separating questions that are often bundled together. First identify the resource. Then examine current public operation. Only after that should broader service, corporate or infrastructure questions be asked through sources able to answer them.

For AS136922, identity is the strongest layer. APNIC supplies the number, network name, Australian country field, organisation objects and roles. The linked company entry points to WELLS RESEARCH PTY LTD TA Anttel Wholesale. Together, those records make the subject specific.

The second step is public routing. RIPEstat reports announced=false, no prefixes, no visible address space, zero peer visibility and no neighbours. That establishes the current observation without explaining it.

The third step is clarification. If Anttel Wholesale presents a service that is expected to use AS136922, a counterparty could ask which prefixes would be originated, whether another ASN is used, which party controls routing and what high-level interconnection arrangement applies. Those questions connect a commercial offer to a verifiable technical identity.

If AS136922 is not intended to support the service, identifying the relevant alternative network resource would prevent the quiet ASN from being treated as a proxy for the whole company. If the ASN is intended for future use, an attributed statement could explain the administrative continuity without pretending that a current route exists.

Technical contacts could also clarify whether the registry roles remain appropriate. The presence of role objects is helpful, but an operator statement or successful coordination would be stronger evidence of current responsiveness. No assumption either way should be made from the fields alone.

Corporate questions should follow a separate path. If legal continuity, trading status or corporate control becomes material, the appropriate current official corporate record is required. Neither RDAP status nor routing visibility can substitute for it.

Infrastructure questions require asset-level support. Facilities, fibre, spectrum, equipment, capacity and coverage should be documented through independent records or clear first-party evidence that can be evaluated directly. They cannot be reconstructed from the ASN.

This sequence produces better accountability because it keeps uncertainty attached to the correct layer. The registry supplies a named steward. Running-state data supplies a silent public view. Further questions are routed to the parties or records capable of resolving them.

What a future route would—and would not—change

The most direct change to the current assessment would be a new visible announcement from AS136922. A future RIPEstat response showing announced=true, one or more prefixes, peer visibility or observed neighbours would establish a new public-routing state.

Such a change should be recorded as a new event. The prefix, address family, observation time, peer visibility and neighbours would all matter. A new route would not prove uninterrupted operation before the observation, and it would not explain the earlier silence.

The registry should be checked at the same time. If APNIC still names WELLS RESEARCH PTY LTD T/A Anttel Wholesale, the administrative and operational layers would align again at that later boundary. If the registrant, roles or network name had changed, the new routing event would need to be assessed against the updated record.

A route alone would still not prove facility ownership, coverage, customer count, capacity or service quality. BGP shows reachability relationships and origin information; it does not function as an asset register or commercial audit.

An APNIC change without a route would alter the accountability layer but leave the public-routing observation quiet. A new registrant, role or status could be significant, yet it would not demonstrate that the ASN had begun operating publicly.

An attributed statement from Anttel Wholesale could narrow the uncertainty in another way. The organisation might identify the ASN as dormant, reserved, superseded or intended for a named use. Such a statement would explain intent from the registrant’s perspective, but its operational claims should still be compared with observed routing.

Repeated silent observations can also add information. They can establish that the selected public view remained unchanged across several dates. They cannot, by themselves, establish the cause or convert a measured interval into permanent inactivity.

The assessment is therefore designed to be updated field by field. Registry identity, prefix state, peer visibility, neighbours and attributed explanation each occupy their own place. That structure prevents a later change in one field from rewriting unrelated facts.

A dated baseline for AS136922

The present record can be reduced to a compact monitoring baseline without losing its boundaries:

Layer Captured observation Interpretation limit
Number resource AS136922 One ASN, not the whole company
Registry name AWPL-AS-AP A network-resource label, not a service description
Registry description WELLS RESEARCH PTY LTD T/A Anttel Wholesale Administrative attribution, not proof of current operation
Registrant organisation ORG-WRPL1-AP, displayed as Anttel Wholesale Does not establish corporate-law status
Administrative and technical role WRPL1-AP, displayed as WELLS RESEARCH PTY LTD TA Anttel Wholesale Contact metadata, not proof of current staffing or response
Country AU Administrative context, not a map of infrastructure or coverage
Registry status active Status of the record, not proof of public BGP activity
RIPEstat overview announced=false No current announcement in the captured view, not universal absence
Announced prefixes Empty No listed current origin prefix, not a causal explanation
IPv4 peer visibility Zero of 328 reporting peers Bounded public observation, not every possible router
IPv6 peer visibility Zero of 322 reporting peers Bounded public observation, not every possible router
Observed neighbours None No neighbour in the captured view, not proof of no private relationship
Visible address space No IPv4 or IPv6 space No current public space attributed in the response
Historical endpoints first_seen and last_seen empty No supported chronology or proof of never having routed

This baseline is useful precisely because it avoids a dramatic verdict. It tells a later observer which fields to recheck and which conclusions remain prohibited. If the routing state changes, the new values can be compared directly. If the registry changes, the stewardship record can be updated separately.

It also makes disagreement easier to resolve. An operator who believes AS136922 was visible can identify the collector, prefix and time that differ from the captured view. A registrant who says the ASN has a different role can supply an attributed explanation. A corporate-status claim can be tested against an appropriate official register.

A vague statement that Anttel Wholesale is “offline” would offer none of that precision. It would combine routing, service and corporate conclusions without proving any of them. The field-level baseline instead preserves the public evidence and leaves room for correction.

The method is especially appropriate for negative evidence. Absence becomes useful when the observation system, time and measured fields are explicit. It becomes misleading when detached from those boundaries.

Durable attribution and silent operation can coexist

AS136922 has not disappeared from the number-resource record. APNIC still presents a unique autonomous system number, a network name, an Australian country field, an active registry status, a registrant organisation and administrative and technical roles tied to the Anttel Wholesale identity.

What is absent is the selected current public-routing surface. RIPEstat reports no announcement, no prefixes, no visible IPv4 or IPv6 address space, no observed neighbours and no visibility among the reporting peers represented in the response.

That combination should not be sensationalised. It does not prove closure, outage, customer loss, permanent inactivity or a transfer. It does not expose private arrangements, facilities, capacity or service coverage. It does not explain itself.

It does, however, preserve a meaningful responsibility boundary. The ASN remains attributable even while its public running state is quiet. If it returns to routing, changes holder or becomes the subject of an operator explanation, there is a precise identity and dated baseline against which that development can be assessed.

The central finding is therefore neither that the registry proves a live network nor that routing silence erases the registrant. It is that administrative continuity and observed operation are separate, testable layers. For AS136922, the first remains visible and the second is currently silent in the captured RIPEstat view.

Sources