Summary
- The directory identifies PacLink Communications LLC as the exact operator entry linked to AS10501, while ARIN’s Registration Data Access Protocol (RDAP) object records the same number and registrant in an administrative ledger. Neither record is a test of a running route or service.
- A frozen RIPE Routing Information Service (RIS) response with query time 7 August 2026, 08:00 UTC reports zero qualifying IPv4 visibility among 327 listed full-feed peers and zero qualifying IPv6 visibility among 320. Those product-, collector- and time-bounded zeros do not prove universal unreachability.
- IPinfo labels its AS10501 profile inactive and returns zero address and relationship rows in the captured page. That independent classifier is not ARIN status, corporate status or proof of an outage, just as ARIN’s active object status is not proof of a live route.
One number joins records with different jobs
The Border Gateway Protocol, usually shortened to BGP, is the system independently operated 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. The number is useful precisely because organisation names can be abbreviated, restyled or duplicated.
AS10501 ties four records to the same subject. The BTW directory provides the exact public identity and navigation entry. ARIN RDAP provides the administrative autnum object. RIPE RIS provides a frozen routing-status observation assembled from its collectors. IPinfo provides an independent ASN summary. Agreement on the number and the PacLink name makes the identity bridge stronger, but it does not merge the records into one all-purpose verdict.
That separation matters whenever an operator, researcher, security team or customer is trying to understand a dependency. A registry can identify the recorded holder of a number resource. A routing collector can report what its vantage points observed. A third-party profile can publish a classification based on its own dataset. None of those sources alone proves legal ownership, route authorization, end-to-end reachability or service quality.
The directory fixes the subject, not the network state
The directory route rendered the exact name PacLink Communications LLC and displayed AS10501 when it was frozen. Its final URL and canonical matched, its robots instruction allowed indexing and following, and the page did not show a soft-404 marker. The linked entity is classified as an operator entry.
These checks prevent an identity error: evidence about AS10501 should not be attached to a similarly named organisation or a generic search result. They do not make the directory an independent source for routing, customers, facilities or operating condition. A published profile can remain useful for navigation even when the network evidence it points toward needs separate measurement.
The legal suffix in PacLink Communications LLC does not change the directory’s operator classification. This Briefing keeps the exact linked subject as the PacLink operator record rather than substituting a broader category.
ARIN RDAP records an administrative object
RDAP is a structured protocol for retrieving registration data about internet number resources. ARIN’s response covers exactly one ASN: its starting and ending autonomous-system values are both 10501, and the handle is AS10501. The object name is PACLINK. Its registrant handle is PCL-51, whose recorded name is PacLink Communications LLC.
The object status is active. ARIN records a registration event at 28 August 1997, 04:00 UTC and a last-changed event later that day at 18:54:53 UTC. Those fields establish a reviewable administrative record and an exact bridge between the number resource and the named registrant.
The word active belongs to that ledger. It does not report whether a router is powered, whether a BGP session is established, whether a route is visible, or whether a customer-facing service is available. Nor does it establish that any observed origin is authorized or that the registrant legally owns every piece of infrastructure associated with the number. Those questions require evidence designed for operational, authorization or legal analysis.
Reading RDAP as a ledger is not a dismissal of registration data. Unique identifiers and accurate records help operators coordinate, investigate mistakes and record changes. The discipline is to keep that administrative function separate from running-code evidence. A durable record can exist while routing conditions change, and a routing observation can change without rewriting the administrative history.
The frozen RIPE RIS response describes one observation
RIPE RIS collects BGP information from participating observation points and publishes products derived from those views. The frozen routing-status response for AS10501 carries a query time of 7 August 2026, 08:00 UTC and a response time of 7 August 2026, 18:51:56.433085 UTC. Retaining both timestamps prevents a later reader from mistaking the bytes for a timeless statement.
For IPv4, the response reports qualifying routes visible to zero of 327 listed RIS full-feed peers. Its announced-space fields contain zero prefixes and zero addresses. For IPv6, it reports zero of 320 listed peers, zero prefixes and zero equivalent /48 blocks. The observed-neighbours field is also zero.
The denominators are essential. The claim supported by the response is about this product’s listed full-feed peers at the stated time, not every router or network on the internet. Zero of 327 and zero of 320 therefore cannot be promoted to universal unreachability. The same caution applies to the zero announced-space and neighbour fields: they do not establish that no historical, private, indirect, filtered or otherwise unobserved connection existed.
The captured response has an empty messages array. It does not state a low-visibility cutoff in these frozen bytes. Importing a threshold from another RIPEstat response would add a condition that this evidence does not disclose, so this Briefing does not do so. The result remains bounded by the named product, collector population and timestamps actually present.
RIS visibility also does not establish route authorization. A collector can describe an origin and path it observed without deciding whether that origin was permitted under the relevant authorization records. Conversely, the lack of a qualifying result in this response says nothing by itself about a company’s legal status, equipment, traffic, capacity or customer impact.
First seen and last seen are not one timeline
The routing-status response also includes historical fields. Its first_seen value names prefix 216.52.210.0/23, origin 10501, at 18 August 2000, 08:00 UTC. Its last_seen value names a different prefix, 206.71.128.0/21, with origin 10501 at 28 June 2001, 16:00 UTC.
Those timestamps are useful only with their prefix identities intact. Joining them into a single sentence such as “PacLink operated from 2000 to 2001” would create a continuous history the endpoint does not provide. The fields concern different prefixes, and the response does not claim that they bound all announcements associated with AS10501.
A defensible continuity account would need a purpose-built time series, stated collector coverage and an explanation of gaps and methodology. An outage finding would also need evidence tied to the affected service and interval. The two endpoint-selected historical fields support neither conclusion on their own.
IPinfo supplies a separate summary and classifier
The captured IPinfo page identifies the exact ASN as AS10501 and names PacLink Communications LLC. It lists the United States as country, paclink.net as domain, ARIN as registry and 28 August 1997 as its allocation date. These fields corroborate the ASN-name pairing and provide another way to locate the subject.
IPinfo classifies the profile as inactive. The captured page also reports zero IPv4 addresses, zero IPv6 addresses and no returned peer, upstream or downstream rows. These are fields in IPinfo’s independent ASN dataset. They are not an ARIN determination, a corporate filing, a legal finding or a universal survey of network relationships.
Empty tables require particular care. No returned peer row is not proof that no relationship ever existed. No address count in this summary is not proof that no resource is recorded elsewhere or that no system can communicate. The page does not disclose every possible private arrangement, indirect path, historical state or data-collection limit. Its evidence can support a bounded description of what the captured page returned, but not an inference about service condition or business continuity.
Active and inactive answer different questions
ARIN’s active status and IPinfo’s inactive label look contradictory only if both are treated as measurements of the same state. They are not. ARIN describes the status of an administrative autnum object in its registry. IPinfo publishes a classifier within its own ASN summary. RIPE RIS then adds a third layer: a routing observation from a stated product, time and peer view.
The disciplined reading does not choose one word as the truth and discard the others. It asks which system produced each field, what that system measures and what additional evidence a stronger conclusion would require. ARIN registration, IPinfo's independent ASN summary and the frozen RIPE RIS response are different evidence layers; none alone proves a live route, universal reachability or unreachability, route authorization, capacity, resilience or customer service.
This approach keeps public number-resource data useful without turning it into an all-purpose operational verdict. The registry records a unique identifier and accountable administrative history. Running observations test a different layer. Third-party summaries can point to questions worth checking. Authority comes from matching the evidence to the claim, not from stretching one label beyond its source.
A practical verification sequence
Start by fixing identity. Confirm the exact directory subject, ASN, RDAP number range, handle and registrant name. This guards against name collision and keeps later observations attached to the intended routing domain. Preserve the operator classification rather than substituting a different entity category.
Next, freeze the routing evidence with its endpoint, query time, response time, address family, numerator and denominator. If the response supplies no threshold message, do not import one. Keep historical prefix fields attached to their individual prefixes and timestamps.
Then compare an independent summary without granting it registry authority. Record the exact ASN, name and dataset label, and describe empty rows as returned fields rather than universal absence. If the question concerns current routing, collect suitable time-aligned observations. If it concerns authorization, inspect the relevant authorization material. If it concerns a service, use end-to-end tests and system records for that service and interval.
This sequence serves network operators and incident responders because it narrows the next question. It also protects customers from unsupported claims. A public ASN profile can help identify a coordination boundary, but it cannot diagnose an application, name-resolution dependency, access network or customer experience by itself.
What the records do not establish
The four sources support a narrow account of PacLink Communications LLC’s directory identity, the ARIN record for AS10501, one frozen RIPE RIS response and one independent IPinfo summary. They do not establish a current outage, dissolution, abandonment, transfer or loss of control. They do not establish universal reachability or unreachability, route-origin authorization, legal ownership, permission or jurisdiction.
They also do not establish customers, facilities, equipment, upstream contracts, service footprint, business scale or market position. No admitted field measures traffic, capacity, latency, physical topology, diversity, resilience, uptime or customer outcome. Those are different questions that require different, time-aligned evidence.
What to watch
Future checks should preserve the same layer boundaries. A registry review can look for changes to the exact AS10501 range, handle, registrant and event history. A routing review can compare later observations only when their product, timestamp, vantage set and denominators are disclosed. An independent profile can be tracked for classifier or table changes without treating them as legal or universal operational findings.
The most useful change would be evidence that answers a specific open question: applicable authorization material for an origin claim, a route-history series for continuity, or service-specific telemetry for an operational claim. Until then, the precise conclusion is modest. The frozen records align on the PacLink and AS10501 identity while describing different administrative, observational and summary layers.