Summary

  • ARIN records Groq, Inc. under handle GROQI as the holder of three autonomous system numbers and three directly allocated address blocks, and the Comments field on every one of the three network records is empty.
  • A buyer of inference capacity gets a holder name, a handle and one contact from that record. The site, the region and what each network actually does are nowhere in it — and Groq's own homepage answers with a capacity ambition instead of a map.

The line you can rely on if you are buying inference capacity from Groq is a name, a handle and a telephone number that someone else answers. Everything else you probably assume the registry confirmed was never in the registry to begin with.

That is not a scandal. It is what an address book does. ARIN's organization record for handle GROQI identifies the holder as Groq, Inc., registered 11 July 2024 and last touched 29 January 2025. It is a well-formed record of a company that exists.

Three networks, registered on the same afternoon

Follow the handle and you land on something more interesting. ARIN's related-ASN listing for GROQI resolves to exactly three autonomous system numbers, each with its own labels:

Recorded name Number Registration Last updated
GROQCLOUD AS40214 31 July 2024 23 July 2025
GROQ-PROD-5 AS46645 31 July 2024 31 July 2024
GROQ-MSP-1 AS40172 31 July 2024 31 July 2024

Three networks, one organization, one day. The naming has the texture of an internal convention: a cloud, a fifth production network, a first managed-service-provider network. A reasonable reader looks at those labels and concludes that Groq runs a cloud, a production estate and an MSP channel, and that someone at the company can tell you which is which.

Nothing in the record supports that reading. Read the three entries again and the column that would decide it is empty. Every one of the three AS-number records carries a blank Comments field. Not a short description. Not a region. Not a site. A blank.

That matters because the record does the opposite of what people think it does with naming. The registry repeats the registrant's own label and stops. GROQ-PROD-5 could mean a fifth production network or a fifth attempt to name a spreadsheet row; ARIN has no opinion, and neither the record nor the label resolves which.

One person, three roles, one phone

Beyond the numbering, the record concentrates accountability in a way worth naming. ARIN's contact listing for GROQI assigns the technical, abuse and administrative roles to a single point-of-contact record, GROQN-ARIN. All three.

The concentration is efficient. Registering infrastructure is much easier when one person can sign for it, and a small, fast-moving company with three networks has every incentive to file that way. The same concentration means that an abuse report, an administrative dispute and a routing problem all arrive at the same desk, and the record cannot even tell you how fast that desk answers.

Then came three quarters of address space

Registration of a network is not the same as holding resources, and this is where the record gets concrete. ARIN's network-resource listing for GROQI contains three blocks and no others, and each detail record makes the same statement of kind:

Block Size Registered Type
185.111.200.0/22 1,024 IPv4 addresses 9 September 2024 Direct Allocation
2607:EE40::/32 an IPv6 /32 9 January 2025 Direct Allocation
124.197.0.0/20 4,096 IPv4 addresses 28 April 2025 Direct Allocation

So the sequence is real and it is legible: an organization in July 2024, three network numbers at the end of that month, a first IPv4 block in September, IPv6 in January, a second and larger IPv4 block in April. Whatever else is true, Groq has been building something in registry terms, and the addresses are recorded as allocated, not merely pending. The IPv6 record even carries the name GROQI-IPV6-1, which reads like the first entry of a series.

What the same detail records will not tell you is the one thing a capacity buyer wants: whether any of it is visible on the internet. Net Type Direct Allocation describes how ARIN issued the block, not whether a router anywhere originates it. Which of the three networks announces which block is not in these records. Neither is any service, site or region.

What the operator itself does not say

Here the registry is not the only silent party. Groq's own site describes the company as a neocloud for AI inference and states, verbatim: "We're building hundreds of megawatts of capacity, with many more on the way." That is a capacity ambition in one sentence, and it is the kind of sentence that makes a procurement team feel good about a supplier.

It is also a sentence with no geography in it. The same page names no datacenter, no region and no network. There is nothing a reader can set beside AS40214, AS46645 or AS40172 and conclude which of the three serves Frankfurt, Helsinki or anywhere else.

Put the two surfaces side by side and the shape of the problem becomes obvious. The operator markets capacity in megawatts. The registry files identities and address blocks. Neither publishes the correspondence between them, and the correspondence is precisely what tells you whether your request stays inside one network or crosses three.

The boundary of this record

Two limits belong here, and only here.

No routing observation was obtained for any of the three networks or the three blocks, so this article neither establishes nor excludes an active announcement; the records simply do not speak to it. The GroqCloud console documentation page could not be read during research, and a page that could not be read is a gap in retrieval, not evidence about its contents. Elsewhere in this record, silence is the registry's silence, and I will not dress it up as a finding that something does not exist.

What a buyer can actually check

This is a shorter list than most people expect, and much of it is useful.

You can confirm that the entity you are contracting with is the entity the registry knows. You can confirm which autonomous system numbers are filed to that entity and on what dates, and whether the count matches what the sales deck implies. You can confirm whether the holder holds directly allocated address space rather than renting a slice of someone else's, and you can see that the allocation record names the same organization, which is a check you should run on every supplier and rarely do.

You cannot confirm, from this record, what any of those networks does. You cannot confirm which one carries traffic for a given model endpoint. You cannot confirm that a block is announced, that a region exists, or that a megawatt claim has a site behind it.

The operator can close most of this cheaply. Name the network that serves each region. Publish, per AS number, the prefixes it originates. Neither costs a press release. Until one of those exists, the most accurate description of Groq's network footprint is a registered identity with a documented silence attached to it — an address book entry for a company that is plainly doing something, and a blank column where the something should be.

If you are the buyer, price accordingly. The registry has told you who is accountable for the numbers. It has not told you what the numbers are for.