Summary

  • No current registered identity, exchange participation, facility relationship, announced-prefix count or routing-status value for AS19035 was verified in this run.
  • The operational question is not whether a directory entry exists, but who can demonstrate continuity when registry, interconnection and routing-observation records are incomplete.

A useful infrastructure investigation begins by separating three evidence layers.

Registry identity. ARIN RDAP is the appropriate registry layer for consulting the registration identity associated with AS19035. It can provide an authoritative record when a current response is available, but an endpoint description is not itself a verified organization name, handle or ASN record. The current run preserved the ARIN endpoint as a candidate source but did not retrieve its live response body. ARIN RDAP

Interconnection records. PeeringDB is a participant-maintained source for network, exchange, IX-LAN and facility relationships. Those records can help establish how an operator describes its interconnection surface at a particular time. They do not, without a captured and current response, establish that a participant is presently connected, exchanging traffic or operating a resilient path. The relevant network, IX-LAN, exchange-search and Honolulu-facility endpoints were preserved for verification, but their current fields were not established here. PeeringDB network IX-LAN exchange record search results Honolulu facilities

Observed routing. RIPEstat and other BGP observers describe what their collectors saw, when they saw it and through which measurement vantage points. They are therefore visibility layers, not direct proof of physical continuity. A route may be announced without proving that an exchange is carrying local traffic; an absent observation may reflect collector coverage, timing or policy rather than a complete outage. The preserved RIPEstat endpoints cover AS overview, announced prefixes and routing status, but no current value from them was verified in this run. RIPEstat overview announced prefixes routing status

That distinction matters more in an island market. Connectivity to Hawaii depends on a chain that may include submarine cable landings, terrestrial backhaul, facilities, exchange fabric, upstream transit, route policy and operational staff. A public directory can describe one link in that chain. It cannot by itself show whether the links are diverse, whether failover has been tested, whether spare capacity exists or whether the parties controlling recovery have aligned incentives.

The present evidence therefore supports a bounded conclusion: the run found no verified current public-record field value for Hawaii Internet Exchange or AS19035. It does not support a conclusion that the exchange is inactive, that AS19035 is unreachable, that a facility relationship exists or does not exist, or that any particular redundancy arrangement is in place. The absence is an evidence limitation, not an operational diagnosis.

For operators and public-interest readers, the next useful records would be timestamped registry and exchange responses, current facility and port information, route-server or looking-glass observations, and operational evidence of recovery arrangements. Those records should be compared rather than collapsed into a single status label. The practical question is who controls continuity and can demonstrate it when a cable, facility, transit path or routing policy fails.

The directory record for the subject is available here for future evidence updates: Hawaii Internet Exchange.

Sources preserved for this investigation also include BGP.tools and Hurricane Electric BGP views, which can provide additional observation points but were not treated as current factual observations in this run. BGP.tools Hurricane Electric BGP