Summary

  • As of the 2026-11-09 retrieval, AS402324 announces four IPv6 prefixes and originates three, with zero IPv4 in either count.
  • The only interconnection counterparty the page lists for that ASN is AS20473, The Constant Company, LLC — one visible door for a company that sells GPU capacity.

Anyone buying GPU hours is buying two things at once: silicon and a path. The silicon gets the benchmark, the invoice and the conference slide. The path gets a line in a contract, if it gets anything at all. Yet the path decides whether a training job's checkpoints reach storage, whether inference replies come back inside a latency budget, and whose engineers answer when a route flaps at three in the morning.

For a GPU cloud, that path is unusually cheap to inspect. An autonomous system number is a public claim: a network identifier a company registers so that routing observers can watch it. GPULOL Inc. has one, AS402324. As of 2026-11-09, Hurricane Electric's BGP toolkit page for AS402324 reports four prefixes announced, three originated, and — in both counters — not a single IPv4 prefix.

Two counters, and they do not match. The mismatch is the interesting part, so it is worth saying what each means. Originated means the network itself declares that a block is its own and that traffic for it should arrive here. Announced means the block turns up in the global routing table under this ASN, which can include blocks the network merely passes along on someone else's behalf. Four announced against three originated is not a scandal. It is a one-line demonstration of the difference between owning an address and carrying it.

Zero IPv4 in both counts is the sharper fact. Corporate networks, hotel Wi-Fi and a large share of mobile carriers still reach the world over IPv4. A company with no IPv4 in its own announcement record is not invisible to those users — it can sit behind somebody else's blocks — but nothing in its own record places it directly in their path.

The interconnection table is shorter still. Under the heading "AS402324 IPv6 Peers" there is exactly one row: AS20473, The Constant Company, LLC. In this table, a peer is an adjacent network the observer lists for the ASN. One row is a dependency, not a fault. A company can run excellent infrastructure and buy transit from a single provider; plenty do. It does mean the visible edge between GPULOL's network and the rest of the internet passes through one named counterparty. Any redundancy behind that edge is not visible in the address record, and the address record is what a customer can check without a sales call.

Put the four observations together — four announced, three originated, zero IPv4, one counterparty — and the shape is a thin, single-doored interconnection posture. That describes a record, not a business verdict. GPULOL's directory entry Only for Strategic Circle, which ties the company to AS402324 and a CA location across 9 supporting public references, says nothing about how many accelerators it runs or where they sit.

The asymmetry is what deserves a long look. A GPU cloud's public surface is rich: model support, throughput, price per hour, region lists. Its network surface is a handful of counters on a page maintained by a third party. Both describe the same company. Only one of them can be checked by an outsider in a browser in under a minute.

What this retrieval could not read

Three of the four sources behind this piece came back empty on 2026-11-09. RIPEstat's page for AS402324 returned its interface shell without routing data. ARIN's RDAP record for autnum 402324 and PeeringDB's entry for ASN 402324 both failed to return content, so the registration detail and the exchange-and-facility detail were not read here.

That boundary governs how far the argument travels. A failed read is not evidence that a record is empty, and it is certainly not evidence that a network is a letterhead. What can be stated is what the readable page showed on the date it was read, and that the rest is open.

The question a buyer actually needs answered is not "is this a real network". It is "who operates the path between the accelerator I rent and the user I serve". Address records cannot close that question. They narrow it. On 2026-11-09 the public record gave AS402324 four IPv6 prefixes, three of its own, no IPv4, and one visible counterparty.

Four prefixes and one door is not a small company's shame. It is a specific, checkable description — and it is the description a procurement team should be able to improve on, by asking a vendor for the ASNs its traffic traverses and holding that answer against the page.