NBNET

NBNET is a dormant autonomous system number registrant (AS10618) with no observable routing activity. Evidence is limited to a single RDAP record naming The National Business Network Inc. as the organizational contact and Larry Hampshire as a technical contact. The entity's operational status, services, and ownership are not documented in public sources, creating high uncertainty. Watchpoints include any prefix announcements, website launches, or registry updates that would signal an active network presence.

NBNET

NBNET is a network institution registered as the holder of Autonomous System 10618, as shown in public RDAP records accessed via rdap.org. The entity is listed under the organizational contact 'The National Business Network Inc.' with technical contact Larry Hampshire, though no operational details, routing activity, or geographic location are confirmed by the available evidence.

Its profile rests on a single public registry entry, making its current capabilities and market role largely opaque.

Why It Matters

The concrete impact of public signals about NBNET is currently low because the ASN is not announced in the global routing table. However, the mere existence of a registered ASN without active prefixes can be a precursor to network launches or transfers. If NBNET were to become active, it could introduce new routing policies, potential traffic engineering, or security events.

The primary impact today is the informational gap—network operators must decide whether to trust or filter routes from an entity with no verifiable operational track record.

What Sources Show

NBNET is the registered holder of Autonomous System 10618, a numeric identifier that can be used to originate internet routes. The ASN is publicly listed in RDAP records, but no operational routing activity has been observed. For network operators, the existence of an inactive ASN represents a potential future routing source that could affect traffic paths or introduce security risks if it becomes active without warning.

The sole public evidence is the RDAP entry for AS10618 at rdap.org. It names “The National Business Network Inc.” as the organizational contact with entity handle “NBNT,” and lists “Larry Hampshire” with handle “LH540-ARIN” as a technical contact. No IP prefixes, geographic location, or corporate website are present in the registry data. The record does not include a business description or evidence of active network operations.

The available data suggests NBNET is an administrative shell in the ARIN registry. The organizational contact implies a corporate entity, but no incorporation documents or business registrations are confirmed. The technical contact may manage the ASN record, but there is no public indication of routers, data centers, peering arrangements, or customer relationships. The entity’s footprint is effectively invisible beyond the registry entry.

An inactive ASN like 10618 is a negligible factor today. However, many network-layer events—such as prefix hijacks, route leaks, or spam campaigns—originate from ASNs that were previously unknown or dormant. If NBNET begins announcing prefixes, it could rapidly transition from a paperwork registration to an operational network with real internet effects. Readiness to monitor any announcement is a prudent posture.

Concrete signals that would update this assessment include: the appearance of IP prefix announcements in BGP looking glasses; creation of a PeeringDB entry; publication of a corporate website at a domain linked to the organization; changes in WHOIS contact details; or association with known network operators, hosting providers, or content delivery platforms. Any of these would move the entity from dormant to active and warrant deeper investigation.

The profile is built on a single RDAP record with no corroboration from independent public sources. The nature of “The National Business Network Inc.”—its industry, size, and ownership—is unknown. The role of Larry Hampshire is limited to a technical contact field, which does not confirm employment or operational control. Until additional data surfaces, NBNET remains a registry entry with no demonstrated internet impact.

Operating Surface

NBNET's public-facing role is that of an autonomous system number registrant within the ARIN system, as evidenced by the RDAP record for AS10618. The designation implies a potential function in internet routing or network management, but the institution has not been observed to advertise any IP prefixes or participate in global BGP routing tables at the time this evidence was collected.

The entity exists as a legal or administrative placeholder in the registry, with no confirmed operational infrastructure, services, or commercial engagement.

BTW readers should track NBNET because any autonomous system holder can become an active network operator capable of originating routes that affect internet traffic paths, security, and competition. Although AS10618 is currently dormant in routing observations, a shift in its operational posture—such as the announcement of prefixes, acquisition by another entity, or emergence of a business website—could have consequences for regional or global internet routing.

In the absence of activity, it serves as a baseline watchpoint for registry-introduced risks.

Watchpoints

NBNET represents a low-probability but non-zero risk of future network disruption if it becomes active. The absence of routing data means the entity currently poses no operational threat, but it also means there is no basis for trust. Network operators should set cautious filtering policies for AS10618 and monitor for announcements.

Monitor BGP feeds and PeeringDB for AS10618. A change in contact details or the appearance of a corporate website would indicate a shift in status. Association with known network entities or registration of IP prefixes would require a full profile update.

Lack of any ownership, business registration, or operational infrastructure data. No historical routing information. Unknown geographic footprint. No reference in third-party databases, news, or technical forums.

Sources

• Public registry source - supports public-source identity and registry context for NBNET.