Summary

  • RIPEstat lists AS400106 with the holder string CLOUD9-VOIPNETWORKS-02 - VoIP Networks.
  • The same overview places the resource in an ARIN-assigned IANA 32-bit ASN block and marks it as not announced.

VoIP Networks is a useful directory-company case because the public evidence is precise and limited. RIPEstat's AS overview binds the company name to AS400106 through the holder string CLOUD9-VOIPNETWORKS-02 - VoIP Networks. It also places the resource inside the IANA 32-bit autonomous-system number block 399261-400284, described as assigned by ARIN, and reports announced=false for the current query window.

Those facts should not be stretched. They do not prove active VoIP traffic, customer relationships, facilities, peering sessions, transit contracts, private architecture, service reliability, or commercial scale. They prove a registry identity, a number-resource context, and a current routing-status boundary. That boundary is important because a company directory entry can become misleading when a named ASN is treated as live infrastructure without a current route signal.

The registry record still matters when the ASN is quiet. It gives analysts a stable holder string to compare against later BGP visibility, transfer signals, route-object changes, or directory updates. If AS400106 becomes announced later, the first check is whether the announcement remains consistent with the public holder and directory identity. If it stays unannounced, the record still helps prevent overconfident claims about a network that is not visible in routing data.

This is the Heng.lu surface for the article: an ASN and IP registry record should be treated as a ledger of names and identifiers, while running code and current routing behaviour remain the evidence for live operation. VoIP Networks therefore belongs in a directory-company coverage model only with explicit caveats. The evidence supports registry continuity and routing-state monitoring, not a story about live traffic. The image used here is generic public-domain network lab context and does not depict VoIP Networks equipment, customers, offices, facilities, traffic, or reliability.

Sources

  1. BTW directory: VoIP Networks
  2. RIPEstat AS overview for AS400106
  3. DVIDS public-domain image 8558192