Summary

  • APNIC’s Registration Data Access Protocol record covers exactly AS137427 and names KIDC LIMITED as registrant. Its active status belongs to the administrative object; it does not establish route authorisation, running equipment or service availability.
  • Hurricane Electric’s BGP Toolkit independently pairs AS137427 with KIDC LIMITED in the exact returned page title. That supports an ASN-and-name link, not unstored claims about prefixes, peers, topology, ownership or commercial relationships.
  • A frozen RIPE Routing Information Service response at 7 August 2026, 00:00 UTC reports qualifying IPv4 visibility at 323 of 325 listed peers and qualifying IPv6 visibility at 0 of 320. Those product-, time- and collector-bounded values are not universal reachability or capability verdicts.

One number connects three different jobs

An autonomous system is a network, or group of networks, that presents a common routing policy to the wider internet. Its autonomous system number, usually shortened to ASN, is a unique identifier used when networks exchange reachability information through the Border Gateway Protocol, or BGP. BGP carries statements about which network can be used to reach an address prefix; it does not by itself explain the company behind the number, the legal authority for an announcement or the health of a customer service.

AS137427 is the stable join key across the evidence considered here. The BTW directory entry identifies the selected company subject. APNIC records an administrative autonomous-system object. Hurricane Electric publishes an independent public profile that pairs the ASN with the KIDC LIMITED name. RIPE’s Routing Information Service, or RIS, gathers BGP information from selected observation points and feeds products such as the frozen routing-status response used in this briefing.

The shared number reduces name ambiguity. It lets a researcher verify that each record concerns the same numeric routing identifier even when sources serve different purposes. That is useful for routine due diligence, incident triage and coordination between networks.

The shared number does not make the records interchangeable. A registry supports uniqueness, recorded identity and contact continuity. A public ASN profile can corroborate a name-number pairing. A collector response describes what met a product’s method at a particular time and set of vantage points. Each may be accurate within its scope while leaving other questions unanswered.

The directory fixes the subject, not the network state

The directory entry is used here to identify KIDC LIMITED as the subject attached to AS137427. That is an editorial identity boundary. It helps prevent evidence about one ASN from being assigned to a similarly named company or to a different routing domain.

The directory is not counted as independent operational corroboration. Its company name, region and category fields are not measurements of routes, traffic, equipment, capacity or service availability. The global value in the Overview is an editorial classification; it is not evidence that KIDC LIMITED operates globally. Likewise, the directory’s HK field does not establish a complete service territory, jurisdictional conclusion or physical footprint.

APNIC RDAP is an administrative ledger

APNIC’s Registration Data Access Protocol, or RDAP, response covers exactly autonomous-system number 137427. The starting and ending numbers are both 137427, the handle is AS137427, and the object name is KIDC2-AS-AP. The country field is HK. The response names KIDC LIMITED as the registrant under handle ORG-KL20-AP and also contains administrative, technical and abuse entities.

The captured record gives both its registration and last-changed event as 21 September 2023, 05:52:54 UTC. Those fields provide a reviewable administrative identity and event history for the number resource. They are valuable when an operator needs to confirm that a question is attached to the intended ASN and recorded organisation.

The object’s active status must stay within that administrative context. It does not report that a router is forwarding packets, a BGP session is established, a prefix is visible, an announcement is authorised or a customer-facing service is reachable. Treating it as a network-health label would ask the registry to answer a running-system question it does not test.

A sound reading treats the registry as a ledger rather than a sovereign verdict on the live network. Number-resource coordination needs unique identifiers, accurate associations, event recording and useful contacts. Operational reality still depends on running equipment, accepted routing policy, transport, power, people and procedures. The registry entry can anchor the subject without certifying those systems.

Hurricane Electric adds an independent name pairing

The exact Hurricane Electric BGP Toolkit page returned a title that pairs AS137427 with KIDC LIMITED. Because Hurricane Electric is separate from APNIC and RIPE NCC, that returned page supplies an independent public ASN-and-name profile. It supports a narrow continuity point: another network-focused publisher associated this exact number with the same company name.

That is where the admitted claim stops. The captured base page referred to functions that can load prefixes, peers, graphs, organisation data, WHOIS and RDAP details dynamically, but those subresources were not fetched for this evidence set. No count or relationship from them is stored here. The page title therefore cannot support a claim about current originated prefixes, neighbours, upstreams, exchange presence or physical topology.

Nor does the title establish ownership, corporate control or route authorisation. A public profile can label an ASN consistently without deciding who owns every asset, whether a particular announcement has permission, or whether a commercial relationship exists. Those questions require records designed for legal identity, origin authorisation, contracts or operating state.

Used within this boundary, the profile remains useful. It gives a reader a second, independently published place where the company name and ASN appear together. It strengthens identification while leaving operational and corporate conclusions open.

The frozen RIPE RIS response is a routing observation

The routing-status response used here has a query time of 7 August 2026, 00:00 UTC. It reports qualifying IPv4 routes visible from 323 of 325 listed RIS full-feed peers. For IPv6, it reports qualifying visibility at 0 of 320 listed peers. Its announced-space fields contain four IPv4 prefixes representing 1,024 addresses and zero IPv6 prefixes or equivalent /48 units. The response reports one observed neighbour.

These numbers describe one product response at one time. The peer denominators identify the listed observation set; they do not represent every network or user on the internet. The response also states that its results exclude routes with very low visibility, defined as fewer than ten RIS full-feed peers seeing them. A route outside that qualifying threshold would not be represented in the same way.

The IPv4 value is broad within the listed set, but it is not proof of universal reachability. It does not show that every source could reach every address, that every path worked, or that an application answered. It does not measure traffic, latency, loss, congestion, capacity or customer experience. A route can be visible to a collector while a local access link, name-resolution path or application remains unavailable.

The IPv6 zero needs equal care. It reports no qualifying IPv6 visibility for AS137427 in this product and listed peer set at the frozen query time. It does not prove that KIDC LIMITED lacks IPv6 capability in every system or arrangement. The sources do not establish whether IPv6 may exist behind another ASN, inside private environments, through a customer arrangement, in testing or outside the product’s qualifying view. Those possibilities are not claims that such deployments exist; they explain why a bounded zero cannot support a universal negative.

The four IPv4 prefixes and 1,024 addresses are observation fields, not measures of business scale or service coverage. They do not reveal customer count, usable capacity, utilisation, facilities or geographic reach. The one observed neighbour is not proof of a particular peer, transit contract, path diversity or resilience design.

First seen, last seen and query time are separate fields

The same frozen response contains historical fields that are easy to compress into an unsupported story. Its first_seen field names prefix 103.151.173.0/24, origin 137427, at 23 June 2022, 16:00 UTC. Its last_seen field names a different prefix, 45.91.227.0/24, with the same origin at 7 August 2026, 08:00 UTC. The response query time is 7 August 2026, 00:00 UTC.

Those are three distinct fields, and the two historical records concern different prefixes. They should not be rewritten as the start and end of one route, an operating interval or an outage. The endpoint selected those examples within its own response logic. A continuity conclusion would need a purpose-built route-history series with explicit coverage, thresholds and vantage points.

The apparent ordering of query time and the returned last_seen time is also a reason to preserve field names rather than invent a chronology. The accurate account reports what the response returned and keeps each timestamp attached to its field. It does not infer a causal sequence, a data error or a service event.

How to match a question to the evidence

A useful verification sequence starts with identity. Confirm the exact ASN and company association in the directory and APNIC RDAP record. Check the number range, handle and registrant name. This reduces the risk of evaluating a similarly named organisation or unrelated routing domain.

Next, decide whether the question is administrative or operational. For registry association and contacts, RDAP is the relevant layer. For a second public name-number pairing, the frozen Hurricane Electric page provides limited corroboration. For observed routing, preserve the RIPE RIS product, query time, address family, peer denominator, qualifying threshold and returned prefixes.

If the decision concerns authorisation, add origin-authorisation and number-resource evidence appropriate to the prefixes in question. Collector visibility alone cannot decide permission. If it concerns continuity, use a route-history method with a defined interval and coverage. If it concerns performance or customer service, use end-to-end measurements and evidence from the specific service boundary.

During an incident, begin with the symptom: which user, site, prefix, destination or application is affected, and when? Then compare external routing evidence with operator and customer observations from the same window. A route visible to RIS can coexist with a local service failure. A route absent from one product can coexist with visibility elsewhere. The snapshot is a signal, not the verdict.

This method respects the role of each source. APNIC registration, Hurricane Electric’s independently published ASN profile and the frozen RIPE RIS response are different evidence layers; none alone proves route authorisation, universal reachability, current service health, capacity, resilience, topology or customer experience.

What the records do not establish

The admitted evidence supports a focused account of an administrative ASN identity, an independent public name pairing and a frozen collector observation. It does not establish KIDC LIMITED’s services, customers, facilities, equipment, upstream contracts, exchange presence, corporate ownership, market position or operating footprint. The datacenter category is publication metadata and does not prove a data-centre facility.

The records also do not establish a live peering session, route-origin authorisation, path preference, traffic, throughput, latency, spare capacity, physical diversity, resilience, uptime or a customer outcome. They do not show whether every relevant asset is owned, leased or shared.

These limits are not allegations. KIDC LIMITED or other authorised parties may hold operational, commercial or engineering evidence that is not public. The source set defines what an external reader can responsibly conclude from the cited records and which questions require additional evidence.

What to watch

  • changes to the exact AS137427 number range, registrant identity, administrative status or event history in APNIC RDAP;
  • later independently published ASN profiles that disclose exactly which fields and subresources were captured;
  • routing observations that preserve product, query time, address family, listed-peer denominator and low-visibility threshold;
  • purpose-built route-history or origin-authorisation evidence when the question concerns continuity or permission;
  • authorised operational evidence when the question concerns a live session, performance, resilience or customer experience;
  • any claim that turns a directory category, registry status or collector count into an ownership or service verdict.

Sources