GetNet Inc.: The Economic Afterlife of a Phoenix ISP's Address Block
GetNet Inc. must be understood not as a high-speed access provider, a hosting company, or a currently visible ISP, but as the persistent shadow in the registries of an Internet company once active in the Phoenix area, whose most economically tangible asset was IPv4 address space. Public archives show a corporate lineage that was operationally real in the late 1990s and early 2000s: dial-up access, DSL-type access, web hosting, colocation, dedicated Internet connectivity, DNS, and customer messaging. They also show a present-day resource history in which the former network identity no longer appears to exercise active routing power. The central economic event is that the IPv4 block historically associated with GetNet, 216.19.192.0/19, is now registered at ARIN under the name Magnite, Inc., an advertising technology company, and no longer under GetNet. ARIN records list this /19 as a direct allocation to Magnite, Inc. under the organization ADMON, with a registration date of December 17, 2024, and an update on October 15, 2025.
This fact changes the interpretation. The directory listing points to GetNet Inc.; the ARIN organization registration still exists; the former address, phone number, and point-of-contact structure still refer to Phoenix. But the resource that made the identity economically interesting appears to have migrated. The inherited identity of GetNet matters less as an active local ISP and more as a case study in how defunct or thinly staffed network companies can retain, monetize, transfer, or lose economically scarce number resources long after the business activity has disappeared.
The underlying ARIN organization registration is unambiguous about identity but not about operations. The public ARIN record for organization handle GTNT lists "GetNet Inc." at 333 E Indian School in Phoenix, Arizona, with a registration date of June 29, 2001, and last updated on August 22, 2024. The associated ARIN point-of-contact records show administrative, abuse, and technical roles linked to GetNet contacts. A historical network operations contact, GET-NOC-ARIN, gives the same Phoenix address, phone number +1-602-264-7000, and email addressadmin@getnetinc.net, but ARIN also indicates that it attempted to validate this point of contact without receiving a response since June 25, 2025. In the registry economy, this is a significant signal. It does not prove dissolution of the company. It suggests that the public administrative surface of the network identity is thin.
The older company was not fictitious. A public operator announcement in April 2001 stated that former executives and employees of GetNet/Internet Access Inc. had formed GetNet Inc., described the company as an ISP offering dedicated Internet connectivity, web hosting, colocation, dial-up access, and network consulting, and indicated that GetNet Inc. had licensed the rights to the domains getnet.com and neta.com. The same notice identified Jeffrey Gong as president and specified that network operations were to start immediately. This announcement reads as a successor formation after an earlier Internet Access/GetNet/Neta operation had already built a local customer base, names, and technical infrastructure. This is the opposite of a shell company origin. The empty-shell quality appears later, after the operational market evolved.
The visible resolution is therefore as follows: GetNet Inc. was an operational access/hosting/connectivity provider during its business period; it appears to have been the successor or continuation of an earlier GetNet/Internet Access/Neta.com network activity; it does not appear, based on currently visible public evidence, to be an active ISP; and the main historical IPv4 asset is now registered and routed under another company, Magnite. The residual identity of GetNet is economically important because it illustrates the conversion of a local service company into a number resource asset story.
The company as an economic entity
The tangible public record begins with names and addresses, but the economic entity is a bundle: corporate name, network reputation, customer messaging dependencies, DNS authority, domain names, routing relationships, local loop access agreements, and IPv4 registrations. In the early commercial Internet, these elements were often integrated within a single local ISP. The customer purchased an "Internet service," but the provider actually controlled several different bottlenecks: the dial-up access number, the DSL relationship with the incumbent telephone operator, the mailbox, the domain registration, the name servers, the hosted website, the static IP address, and sometimes the colocated server.
GetNet's public footprint matches this pattern. The April 2001 announcement indicated that GetNet Inc. offered access, hosting, colocation, dial-up access, and consulting. It also emphasized the continuity of email addresses on getnet.com and neta.com, which is commercially important because messaging identity was a retention tool in the dial-up and early DSL era. A third-party historical WHOIS mirror for a domain registration mentioned GetNet, Inc. as a registration service provider and indicated that GetNet could be contacted for domain passwords, DNS/nameserver changes, and general domain support. A later web directory snapshot for get.net described "Your Internet Service Provider From GetNet.Com" as a full-service Phoenix-area Internet provider offering web hosting, dedicated servers, virtual private servers, DSL, dial-up, wireless, email, Plesk, cPanel, and Linux services, with name servers in the 216.19.192.0/19 address range.
This combination is important. A small ISP with only retail access customers is exposed to price compression as cable, operator DSL, wireless, and national backbones scale up. A small ISP with email accounts, hosted domains, name servers, and static addresses benefits from higher switching costs. A customer can change dial-up or DSL lines more easily than they can renumber servers, transfer DNS, rewrite MX records, migrate mailboxes, preserve old email contacts, and move hosted applications. For business customers, the ISP is embedded not only in connectivity but also in identity and operations.
Early evidence also suggests that GetNet's market position depended on the incumbent telephone infrastructure. A 1999 public posting by Internet Access Inc. doing business as Getnet solicited former customers for evidence that US West had discouraged them from using Getnet/Internet Access or any independent ISP when ordering phone, DSL, or ISDN services. It stated that the company had filed a complaint with the Arizona Corporation Commission regarding US West's allegedly anticompetitive marketing. A separate Arizona Corporation Commission eDocket search result identifies a formal complaint filed by Internet Access, Inc. dba Getnet against U S West, filed by Jeffrey Gong. The mechanism is simple: the local exchange carrier controlled the copper loop and the customer order path, while independent ISPs attempted to sell service on top of that access layer. If the incumbent could influence the customer's choice at the time of provisioning, the independent ISP's acquisition funnel was fragile.
A 2001 Arizona State University listserv-type supply/channel listing listed GetNet, Inc. among Qwest-supported ISPs, with the Phoenix phone number 602-264-7000 and getnet.com, and separately listed Internet Access Inc. DBA or GetNet with another Phoenix number and getnet.com or neta.com. This is not a complete operational history, but it supports the picture of market structure: GetNet sat in the layer of independent ISPs that needed the incumbent's last-mile systems to reach DSL customers. The value proposition was local Internet service, but the strategic constraint was wholesale access.
The successor problem
The public history of GetNet is not a clean corporate lineage. It is a successor problem.
There exists an older "Getnet International" identity in ARIN-related records. Cidr-report's ARIN-derived listing for AS5784 identifies "GETNET - Getnet International, US," gives ASNumber 5784, ASName GETNET, a registration date of October 24, 1995, an update date of January 18, 2001, and an organization address at 333 E. Indian School Road, Phoenix. It also links abuse and technical contacts to Getnet Inc. and the email addressadmin@getnetinc.net. The later public ARIN organization registration for GetNet Inc.'s GTNT handle was registered on June 29, 2001, at the same Phoenix address. The two registry records are not identical, but the address, name family, and point-of-contact pattern make them economically linked.
The 2001 operator announcement helps explain why. It stated that former executives and employees of GetNet/Internet Access Inc. had formed GetNet Inc. and that the new company had licensed the rights to the neta.com and getnet.com names. This language suggests a deliberate continuity strategy rather than a simple new entry. Customers knew the names; the domains carried an installed base value; the staff carried local operational knowledge; the network identity could survive a legal or operational discontinuity.
There was also customer uncertainty. In a March 2000 Usenet discussion, a entity described neta.com as formerly GetNet/Internet Access, questioned DSL service via US West, and referred to GetNet having filed for bankruptcy and having been bought by Neta. This is a customer-side statement, not an official record, and must be treated as rumor rather than fact. But commercially, it is still useful: customers were trying to deduce continuity, reliability, and ownership from a confusing brand trail. Another customer in the same thread said they had been a customer for years, had encountered few problems, and had kept a neta.com account even while using another access provider for the physical connection. This is the retention mechanism in miniature. The access path could change; the account identity could remain.
The successor problem is important because number resources often survive operational companies. ARIN records are organized around organizations, points of contact, networks, and ASNs; they do not constitute a narrative corporate history. ARIN describes Whois/RDAP registration data as including number resources issued by ARIN or its predecessors, organizations, points of contact, and ISP customer reassignment information. This registry model is operationally necessary, but it creates a risk of misinterpretation. A company name in a registry does not necessarily mean that a current ISP is selling service. It may mean that a resource holder exists, that a contact remains, that an old organization record has been maintained, or that a transfer path has been preserved.
For GetNet, the successor problem has at least three layers. First, the 1995 Getnet International identity and AS5784 appear to predate the 2001 GetNet Inc. organization handle. Second, Internet Access Inc. dba Getnet/Neta.com appears in customer, regulatory, and channel traces before the 2001 formation. Third, the post-2001 GetNet Inc. identity appears to have inherited or licensed the customer-facing names and possibly the infrastructure. The economic continuity is stronger than the legal continuity that can be established from open evidence.
The address block as a tangible asset
The historically important address resource is 216.19.192.0/19. A /19 contains 8,192 IPv4 addresses. A historical WHOIS mirror listed the block as GETNET-BLK1, NetRange 216.19.192.0 to 216.19.223.255, CIDR 216.19.192.0/19, NetType Direct Allocation, organization GetNet Inc., registration date June 29, 2001, and name servers ns1.getnet.net and ns2.getnet.net. The same historical mirror indicated that the addresses within the block were not portable.
The non-portability note is commercially important. For customers who obtained addresses from an ISP's allocation, those addresses normally belonged to the provider's addressing plan rather than the customer's independent registry rights. A business customer could run servers, email, VPNs, DNS, or access control lists on those addresses, but if they changed providers, they might need to renumber. This made the ISP's address block a retention asset. It also made the collapse or sale of the ISP a migration risk for customers.
In the pre-exhaustion era, a small regional ISP's IPv4 allocation was an input for service delivery. In the post-exhaustion era, it became a tradeable scarce resource. ARIN announced that its free IPv4 pool reached zero on September 24, 2015, and stated that approved requests could be fulfilled via a waiting list or the IPv4 transfer market. ARIN's current IPv4 guidelines indicate that the free pool is exhausted, that waiting list requests can only be fulfilled when ARIN receives inventory through returns, revocations, IANA distribution, or other sources, and that organizations can seek IPv4 space via transfers to specified recipients per NRPM 8.3 or 8.4.
This changed the balance sheet of former ISPs. A local access company could lose its commercial relevance while its IPv4 block appreciated or remained sellable. Public broker data should not be treated as a specific valuation of GetNet's block, but they provide scale. ipv4 market actor reported in May 2026 that market demand and transaction volume remained strong, with tightening supply and a slow increase in large block prices. The same broker described a correction in large block prices from early 2024 highs around $50 per address to levels around $20 per address for some large blocks, while other market commentary described recent IPv4 prices in wider ranges depending on block size, registry, reputation, and demand. At indicative prices of $20, $30, or $40 per address, a clean /19 would imply a gross address value of roughly $164,000, $246,000, or $328,000 before brokerage fees, legal costs, registry work, reputation discounts, or transition costs. These figures are not an asserted transaction price; they show why the identity of a former ISP can remain economically relevant even after its customers have left.
The transfer mechanism itself also has economic content. ARIN indicates that for specified transfers, the source organization must be the current registered holder, must not be involved in a dispute over the status of the resources, must provide a signed and notarized acknowledgment from an officer, and must meet minimum size and other requirements. ARIN also indicates that a source organization involved in an 8.3 or 8.4 transfer is responsible for a clean transition, including ROAs, IRR entities, reverse DNS delegation, and coordination with the recipient. These requirements mean that an old registry identity is not just a label. It is the administrative key through which scarce addresses can be transferred, regularized, or blocked.
Routing evidence
Routing evidence points far from active GetNet operations.
Hurricane Electric's BGP Toolkit page for AS5784 identifies it as Getnet International and indicates that the AS has not been visible in the global routing table since April 27, 2024. It shows no currently announced IPv4 or IPv6 prefixes and no valid or invalid RPKI prefixes originating from this AS. Cidr-report similarly indicates that AS5784 is not currently used to announce prefixes in the global routing table and is not visible as a transit AS. This does not prove that all private or internal function has disappeared, but for an ISP or hosting provider, absence from the global BGP table is strong counter-evidence. An access ISP, hosting network, or colocation provider normally needs visible routed prefixes, upstream transit, downstream customers, or peering.
The address block now tells a different story. Hurricane Electric's BGP Toolkit reports that the aggregate 216.19.192.0/19 is not visible in the global routing table. But the current AS26667 page for Magnite shows IPv4 prefixes originating from AS26667 that include 216.19.192.0/20 and 216.19.208.0/20, both under ADMON customer records. The current ARIN registration for the parent /19 lists Magnite, Inc. as the ADMON organization, and the ARIN reassignment record for 216.19.208.0/20 lists the ADMON customer at Ashburn, Virginia, with registration and update dates of September 10, 2025.
This routing pattern is economically coherent. The former aggregate has been re-homed into a larger platform operator's network and announced as two /20s rather than as the historical /19 aggregate. Magnite's AS26667 profile shows a substantially more modern routing posture: 19 announced prefixes, IPv4 and IPv6 presence, numerous observed BGP peers, and participation in Internet exchange points. Third-party application-network data from Netify also lists 216.19.192.0/19 among Magnite's network ranges, alongside other Magnite ranges. The resource has not disappeared. It has changed economic layers.
This matters because BGP visibility is a market signal. When an old ASN stops announcing prefixes, the associated company may still legally exist, but it has lost the external network function that made it an ISP. When the old address space appears under a buyer's ASN, the value has migrated from local connectivity to platform infrastructure. The asset is still productive, but no longer in the hands, brand, or operational context suggested by the old directory listing.
What Magnite changes
The current holder of the historical /19 is not a local Arizona ISP. Magnite describes itself as the world's largest independent sell-side advertising company, providing technology that enables publishers to monetize content across CTV, online video, display, and audio, and enables agencies and brands to execute advertising transactions. Its 2026 quarterly filing describes Magnite as an independent omnichannel sell-side advertising platform that automates the buying and selling of digital advertising inventory.
Why would an advertising technology platform want IPv4 address space? Public sources do not indicate Magnite's motive for this specific block, so the explanation must be inferential. Programmatic advertising infrastructure depends on large-scale, low-latency, reputation-controlled network operations: ad serving, auction requests, measurement, fraud controls, user sync endpoints, data exchange, logging, and geographically distributed distribution. IPv4 addresses are not simply connectivity inputs. They support traffic segregation, reputation management, geolocation, access control, reverse DNS, operational isolation, and migration flexibility. A platform that processes billions of advertising transactions each month has a different address demand profile than a small local ISP, but it still values clean routable IPv4. Magnite indicates that leading agencies and brands use its platform to execute billions of advertising transactions each month.
The movement of the /19 into Magnite's registry and routing environment thus represents a structural shift in where IPv4 scarcity is monetized. In 2001, a Phoenix ISP needed IPv4 addresses to allocate to dial-up pools, DSL users, hosted domains, virtual hosts, and dedicated servers. In 2025, a sell-side advertising platform may need addresses to run distributed digital infrastructure with reputational and operational separation. The same 8,192 addresses support different business models over time.
This is the broader thesis: the address space of former ISPs is not dead inventory. It is a scarce input that can be revalued when control passes from declining local access companies to large-scale platform operators. The old corporate identity is economically significant because it can be the administrative bridge through which the resource moves.
Residual holder or acquired company?
Public evidence does not permit asserting that Magnite acquired GetNet Inc. as an operating company. It does permit asserting that the IPv4 block historically associated with GetNet is now registered with Magnite and appears in Magnite's routing footprint. ARIN records show the /19 as a current direct allocation of Magnite, not as an allocation of GetNet. Routing data shows more specific /20s originating from Magnite's AS26667, not from AS5784.
This distinction is crucial. Number resource transfers, merger/reorganization transfers, and corporate acquisitions are different economic events. ARIN's transfer guide distinguishes transfers based on mergers, acquisitions, and reorganizations from transfers of released number resources to specified recipients. The public ARIN output visible here does not say which path was used for the resource change from GetNet to Magnite. Therefore, the economically prudent conclusion is that the resource changed registry control; the company was not necessarily sold as a going concern.
The likelihood of an active ISP acquisition seems low based on public evidence. There is no visible modern GetNet service website comparable to a live ISP product catalog. Current broadband provider listings for Phoenix emphasize large cable, telco, fixed wireless, satellite, and fiber providers; GetNet does not appear in these modern consumer access listings. The ARIN POC validation failure in June 2025 also points to low current operational contact capability. The older domain and directory traces point to past service offerings, not current sales.
A residual number resource holder is not necessarily legally inactive. It may hold an ASN, domain names, trademarks, messaging systems, or customer remnants. But from an infrastructure economics perspective, a resource holder without visible BGP announcements, without current product pages, without validated POCs, and without the historical /19 in its name is not economically equivalent to an operational ISP.
Customer dependency and lock-in
The former GetNet activity likely generated customer lock-in through four mechanisms.
The first was email identity. The 2001 operator announcement specifically addressed people seeking long-term use of email addresses on getnet.com and neta.com and invited them to contact GetNet. In the early commercial Internet, email address continuity was a powerful switching cost. A residential user might tolerate changing access methods; a small business with printed materials, customer contacts, and account records tied to an ISP mailbox had more to lose. The Usenet customer who kept a neta.com account while using another access provider illustrates this separation of access and identity.
The second was DNS and domain administration. A third-party historical WHOIS record described GetNet as a registration service provider that could manage domain credentials/passwords, DNS/nameserver changes, and domain support issues. For small businesses, this role is sticky. The provider can host authoritative name servers, register the domain, administer email records, and hold login credentials. Migration requires not only a new circuit but also administrative recovery.
The third was hosting and server placement. GetNet publicly described itself as offering web hosting, colocation, dedicated Internet connectivity, and later directory traces refer to dedicated servers and virtual private servers. Hosting customers face data migration, DNS failover risk, IP renumbering, and downtime exposure. Colocation customers face physical movement, cross-connect changes, and routing changes. These switching costs can preserve revenue even as consumer access becomes commoditized.
The fourth was non-portable addressing. The historical WHOIS mirror for GETNET-BLK1 indicated that the addresses in the block were not portable. This language turns number resources into a provider-controlled customer tie. If a customer's server, VPN, or email system relied on an address inside GetNet's block, changing providers meant renumbering, unless the customer had its own portable space or negotiated special arrangements. For the ISP, non-portability protected against attrition. For the customer, it created a dependency.
These mechanisms also explain why an old block can carry hidden obligations. If live customers remain on a block, the transfer is not a pure asset sale. It requires renumbering, service continuation, or management of customer assignment/reassignment. ARIN's transfer guide explicitly highlights clean transition tasks such as ROAs, IRR records, and reverse DNS delegation. The public record does not show whether any GetNet customers remained in 2024. If none remained, the /19 was a cleaner monetizable asset. If some remained, the transfer would have required migration or service absorption.
The incumbent operator constraint
GetNet's local economics were shaped by the structure of Phoenix's telecom access layer. Independent ISPs in the late 1990s and early 2000s often depended on incumbent local loop operators for DSL, ISDN, and provisioning interfaces. The 1999 Getnet/Internet Access posting regarding US West's allegedly anticompetitive marketing shows that GetNet understood the incumbent's customer contact role as a strategic threat. The Arizona Corporation Commission docket trace supports the existence of a formal complaint on this matter.
This is not a secondary issue. It helps explain why local ISPs could be operationally competent and yet structurally disadvantaged. They could manage email, DNS, hosting, dial-up modems, and local support. But when broadband replaced dial-up, the customer acquisition path moved closer to the phone or cable company. The incumbent could bundle access, billing, installation, modem equipment, and support. The independent ISP's differentiated assets narrowed to service quality, technical support, email continuity, hosting, local reputation, and static addressing.
GetNet's channel traces suggest participation in the Qwest-supported DSL ecosystem. But participation did not remove the structural constraint. In a transition to broadband, scale mattered: backbone purchasing, peering, modem pools, DSL aggregation, support staff, billing systems, abuse management, and marketing. Local ISPs that did not consolidate or specialize often became hosting shops, domain/DNS caretakers, or residual resource holders.
Phoenix's current access market underscores the structural change. Modern provider listings for Phoenix are dominated by large cable, telco, fixed wireless, fiber, and satellite brands, not by early local ISP names. This does not prove GetNet has no remaining customers, but it does mean GetNet is not visible as a significant current access competitor in the consumer provider discovery layer.
Namespace confusion
There is also a brand confusion problem. A modern search for "Getnet" frequently returns Getnet by Santander, a payment platform operating in Latin America and Iberia, not the Phoenix ISP identity. The current Getnet payment site calls itself "The Leading AI Payments Company in Latin America and Iberia," and Santander documents describe Getnet as a payment company with e-commerce and merchant payment services. This is unrelated to the ARIN target, except as an information retrieval risk.
This risk has economic significance. When an old network brand stops producing current web signals, other entities with similar names can occupy the search surface. The directory listing and ARIN handle become more important because ordinary web search no longer identifies the relevant infrastructure identity. For investigators, lenders, customers, or counterparties, the risk is false continuity: a "Getnet" brand alive in payments must not be confused with the Phoenix GetNet Inc. network resource holder.
The same problem appears inside the historical GetNet/Neta/Getnet International/Internet Access chain. Different names appear in different records. Some sources use GetNet Inc.; others use Getnet International; others use Internet Access Inc. dba Getnet; others use Neta.com. Economic continuity is plausible, but legal continuity is not fully resolved from public sources. For number resource analysis, this ambiguity matters because the party able to sign a transfer, maintain a POC, or enforce rights is the legally recognized holder, not necessarily the brand remembered by customers.
What unresolved facts would change
Several facts remain unresolved, and each carries different economic weight.
The first is the transfer basis for 216.19.192.0/19. If the block was moved through an ordinary specified-recipient transfer, the story is one of a former resource holder monetizing scarce IPv4. If it was moved through a merger, acquisition, or reorganization transfer, the story could involve a broader asset or corporate transaction. The public ARIN record establishes Magnite's current registration, but not the underlying commercial agreement. ARIN's transfer guide shows that different transfer categories exist and have different requirements.
The second is customer continuity at the time of transfer. If GetNet had no active downstream customers on the block, the transfer was largely a registry, routing, and reverse DNS exercise. If customers remained, the transfer also involved service migration, renumbering, or disposition of customer contracts. Public routing evidence suggests that AS5784 is now inactive, but it does not reveal whether private customer migrations occurred before public visibility ceased.
The third is the status of AS5784. The AS remains historically associated with Getnet International, but it is not currently visible in global routing. An ASN without routed prefixes can still be kept as an administrative entity, but its economic value is far below that of a routed IPv4 block. It could regain relevance if paired with address space or used in a private/interconnection context, but no public evidence supports that today.
The fourth is control of domain names and customer identity assets. The 2001 announcement stated that rights to getnet.com and neta.com were licensed to GetNet Inc., and that the GetNet brand and some domains belonged to Jeffrey Gong. Later public directory traces show infrastructure tied to get.net and getnet.com, but not a current operational product surface. If the domain assets remain under common control with the former registry entity, there may still be residual mailbox, DNS, or brand value. If they have been sold, expired, or reassigned, the residual value is narrower.
The fifth is reputation. IPv4 buyers care about abuse history, blacklisting, geolocation, prior PTR records, and customer residues. Hurricane Electric's page for 216.19.192.0/19 shows historical DNS records, including old names such as ns1.inficad.com and ns2.inficad.com inside the range. Such traces can help reconstruct prior use, but they do not by themselves prove current risk. For a buyer, the key question is whether the block can be cleaned, re-geolocated, routed, and used without inherited reputation penalties.
The economics of disappearance
The GetNet case shows a general pattern in Internet infrastructure economics: the company can disappear before the resource identity does, and the resource identity can remain valuable after the company's disappearance.
The visible disappearance of a local ISP can occur gradually. First, new access sign-ups slow because cable and telco broadband scale up. Second, dial-up access revenues collapse. Third, hosting and email customers remain because they are sticky. Fourth, the provider stops large-scale marketing but continues to maintain legacy services. Fifth, technical staff or owners preserve registry records, domains, and name servers. Sixth, the remaining IPv4 block becomes more valuable as IPv4 scarcity deepens. Seventh, the resource is transferred to a platform, hosting company, cloud operator, security firm, adtech company, or a buyer intermediated by a broker. The old company name remains in historical WHOIS mirrors, BGP archives, customer memories, and business directories.
GetNet appears to largely fit this arc. It was a genuine Phoenix ISP and hosting provider; its predecessor/successor chain carried customer identity assets; it operated in a market structurally pressured by incumbent access providers; its historical /19 became a scarce IPv4 asset; and the block now appears under Magnite rather than under GetNet.
The most important analytical caveat is not to overestimate the current company from the old registry line. ARIN's GTNT record is real. It identifies GetNet Inc. But the current economics of the historical network cannot be inferred from that organization record alone. The best evidence is the combination of registry control, POC validation, BGP visibility, RPKI/IRR posture, product visibility, and historical operational traces. That combination says: once an operational ISP; now a residual identity; the main address asset transferred or re-registered to Magnite; AS not visibly active; no strong evidence of current access or hosting operations.
This is exactly the kind of case where address resource economics creates an information gain. Without the ARIN and BGP evidence, GetNet could look like a dormant small local business. With the resource evidence, it becomes a transactional-style story about how scarce IPv4 migrates from first-generation local ISPs to large-scale digital platforms.
Evidence register
ARIN organization record for GetNet Inc. The public ARIN record for organization handle GTNT lists GetNet Inc., 333 E Indian School, Phoenix, Arizona, registration date June 29, 2001, and last updated August 22, 2024.
Associated ARIN POC record for GTNT. ARIN lists administrative, abuse, and technical POCs linked to the GetNet organization registration.
ARIN GET-NOC-ARIN POC. ARIN lists Getnet Inc. at the same Phoenix address, phone +1-602-264-7000, emailadmin@getnetinc.net, and indicates that ARIN attempted POC validation but received no response since June 25, 2025.
Current ARIN parent network record for 216.19.192.0/19. ARIN lists NetRange 216.19.192.0 to 216.19.223.255, CIDR 216.19.192.0/19, NetName ADMON, NetType Direct Allocation, organization Magnite, Inc., registration date December 17, 2024, and last updated October 15, 2025.
Current ARIN subrange/customer record. ARIN lists 216.19.208.0/20 as MAGNITE-IAD6-2, reassigned to customer ADMON at Ashburn, Virginia, with registration and update dates of September 10, 2025.
Historical WHOIS mirror for GETNET-BLK1. A third-party WHOIS mirror preserves older data listing 216.19.192.0/19 as GETNET-BLK1, direct allocation to GetNet Inc., with non-portable addresses and name servers tied to GetNet. This is useful as historical evidence but not as current authority.
Cidr-report ARIN-derived AS5784 page. Cidr-report identifies AS5784 as GETNET / Getnet International, shows the Phoenix address, and indicates that the AS is not currently used to announce prefixes in the global routing table nor visible as a transit AS.
Hurricane Electric BGP Toolkit for AS5784. HE identifies AS5784 as Getnet International and indicates it has not been visible in the global routing table since April 27, 2024, with no currently announced prefixes.
Hurricane Electric BGP Toolkit for 216.19.192.0/19. HE indicates that the /19 aggregate is not visible in the global routing table and shows historical DNS traces inside the block.
Hurricane Electric BGP Toolkit for AS26667. HE identifies AS26667 as Magnite, Inc. and shows active prefixes including 216.19.192.0/20 and 216.19.208.0/20 under ADMON records, with a wide peering and routing footprint.
Netify network intelligence for Magnite. Netify lists 216.19.192.0/19 among Magnite's network ranges, corroborating the association of the former GetNet block with Magnite's current infrastructure footprint.
April 2001 GetNet Inc. operator announcement. A public Google Groups posting states that former executives and employees of GetNet/Internet Access Inc. formed GetNet Inc.; describes services including dedicated connectivity, web hosting, colocation, dial-up access, and consulting; identifies licensed rights to getnet.com and neta.com; and names Jeffrey Gong as president.
October 1999 Internet Access Inc. dba Getnet posting. A public posting solicits former customers regarding US West's allegedly anticompetitive conduct and references a complaint before the Arizona Corporation Commission.
Arizona Corporation Commission docket trace. ACC eDocket search results identify a formal complaint by Internet Access, Inc. dba Getnet against U S West, filed by Jeffrey Gong.
March 2000 Usenet customer discussion. A customer discussion references the Neta.com/GetNet/Internet Access continuity, includes an unverified rumor of bankruptcy/acquisition, and separately includes a customer comment about keeping a neta.com account while using another access provider.
ASU Qwest-supported ISP list. A 2001 channel/supply trace lists GetNet, Inc. and Internet Access Inc. DBA/GetNet among Qwest-supported ISP options, with Phoenix contact numbers and getnet.com/neta.com references.
Historical domain/DNS service provider trace. A third-party domain record lists GetNet, Inc. as a registration service provider for domain support, DNS/nameserver changes, and associated account functions.
Historical web directory trace for get.net/GetNet. A directory snapshot describes GetNet as a full-service Phoenix-area Internet provider offering hosting, dedicated servers, VPS, DSL, dial-up, wireless, email, Plesk, cPanel, and Linux services, with name servers in the former address range.
MIT traceroute document. A 2000 traceroute from trojan.neta.com shows a Phoenix Neta/GetNet host reaching MIT via Alter.net, supporting the existence of an operational Phoenix network before the 2001 formation of GetNet Inc.
Deaf Magazine 1995 trace. A 1995 page references Getnet International, Inc. in Phoenix and a GetNet name server involvement, supporting the older Getnet International layer of the lineage.
ARIN Whois/RDAP explanatory source. ARIN describes public registry data as covering Internet number resources, organizations, points of contact, legacy resources, and reassignment information, which frames why a registry identity is not the same as a current operational company.
ARIN IPv4 exhaustion announcement and current IPv4 guidelines. ARIN announced the exhaustion of the free IPv4 pool on September 24, 2015, and describes current options via waiting lists, special-use policies, IPv6 adoption, and transfers to specified recipients.
ARIN transfer guide. ARIN's transfer documentation defines requirements for source and recipient and highlights clean transition tasks for ROAs, IRR records, and reverse DNS.
IPv4 market price sources. ipv4 market actor and ipv4 market actor provide market commentary indicating that IPv4 addresses remain monetizable scarce resources, with prices varying by block size, registry, reputation, and demand.
Magnite corporate sources. Magnite describes itself as a large independent sell-side advertising company and a platform for monetizing content and executing digital advertising transactions; its 2026 filing describes technology that automates the buying and selling of digital advertising inventory.
Modern Phoenix provider listing traces. Current consumer provider listings for Phoenix emphasize large broadband, fiber, wireless, and satellite providers and do not show GetNet as a visible consumer access competitor.
Getnet payment company disambiguation. Current Getnet/Santander sources describe a payment company in Latin America and Iberia, which is a different identity from the Phoenix ARIN target and creates search-name ambiguity.
Watchpoints
The first watchpoint is the ARIN history of 216.19.192.0/19. A future ARIN record, transfer log, court filing, or broker disclosure clarifying whether the move to Magnite was an 8.3 specified transfer, an 8.2 merger/reorganization transfer, or another administrative path would change the economic interpretation. A specified transfer would support an address asset monetization thesis. A merger/reorganization transfer would increase the likelihood of a broader asset relationship.
The second watchpoint is AS5784. If AS5784 begins announcing prefixes again, especially prefixes unrelated to Magnite, it would weaken the inactive ISP conclusion. If it remains unrouted, its value is primarily historical and administrative.
The third watchpoint is RPKI, IRR, reverse DNS, and geofeed posture for the former GetNet block. Clean ROAs, updated IRR entities, and stable reverse DNS under Magnite would indicate full technical absorption. Legacy reverse DNS or stale route entities would indicate a slower or messier transition.
The fourth watchpoint is any evidence of remaining hosted customers at GetNet. Old mailboxes, DNS zones, web hosting accounts, colocation remnants, or static IP users would mean the former company had more than registry residues at the time of resource transfer. No public evidence of this type is currently strong enough to establish ongoing operations.
The fifth watchpoint is corporate control of GetNet Inc., Getnet International, getnet.com, neta.com, get.net, and getnetinc.net. Control of these names would determine whether the residual identity still has brand, mailbox, DNS, or customer recovery value. Loss or sale of these names would leave little beyond historical records and any remaining ASN.
The sixth watchpoint is the abuse reputation and geolocation of 216.19.192.0/19. For the current holder, the commercial value of the block depends not only on registry control but also on the addresses being clean, correctly geolocated, accepted by counterparties, and free of inherited blacklists or stale customer associations.
The seventh watchpoint is any expansion of Magnite's network that would use the block in new markets. If the two /20s remain announced under AS26667 and appear in more application intelligence datasets, the block's economic role will be confirmed as platform infrastructure rather than local access infrastructure.
The final watchpoint is the stale registry contact ability. ARIN's POC validation failure for GET-NOC-ARIN is a small but important warning signal. If GetNet POCs are updated and validated, the residual entity may still be maintained administratively. If they remain unvalidated, public evidence will increasingly support the idea that GetNet Inc. is a historical network resource identity whose main monetizable IPv4 asset has already been transferred elsewhere.