Summary

  • Anthropic, PBC's ARIN organization record AP-2440 links five autonomous systems — AS4167, AS60808, AS399358, AS400243 and AS401551 — to four network records, and not one of the nine pages read prints an OriginAS on a network or a network list on an ASN.
  • Three of the four blocks carry the type Direct Allocation; 216.73.216.0/22, printed under the name AWS-ANTHROPIC, carries the type Reassigned inside Amazon's AMAZO-4 parent. That is a printed name and a printed parent handle, and nothing that says what runs behind either.

The file, as printed

ARIN's organization record for Anthropic, PBC is short enough to read in one pass. Handle AP-2440. Street 548 Market St. PMB 90375, San Francisco, California, postal code 94104-5401, country US. Registration Date 2023-07-31. Last Updated 2023-08-22. That is the whole of it: a name, a mailing address, two dates and a handle.

Everything else about Anthropic's presence in the North American registry hangs off that handle in two directions. One direction is a list of autonomous systems. The other is a list of address blocks. The two lists are printed on separate pages, in different shapes, with different fields, and the only value they share is AP-2440.

The organization-to-ASN listing prints five rows and nothing but names and handles:

  • AP-2440-4167, AS4167
  • AP-2440-60808, AS60808
  • ANTHROPIC, AS399358
  • ANTHROPIC-2, AS400243
  • ANTHROPIC-3, AS401551

No registration date. No last-updated date. No status. No comment. Five identifiers and the organization they hang from. Four of those five names are not the company's name; they are handle-derived labels, two of them a straight concatenation of the organization handle and the number, two of them the company name with a counter bolted on.

The organization-to-network listing prints four rows, three IPv4 and one IPv6, with a name, a handle and an address range for each:

  • AP-2440, NET-153-61-0-0-1, 153.61.0.0 to 153.61.255.255
  • AP-2440, NET-160-79-104-0-1, 160.79.104.0 to 160.79.111.255
  • AWS-ANTHROPIC, NET-216-73-216-0-1, 216.73.216.0 to 216.73.219.255
  • ANTHROPIC-V6, NET6-2607-6BC0-1, 2607:6BC0:: to 2607:6BC0:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF

Again no dates, no status, no comment, and no pagination marker anywhere on the page — which is what leads me to describe this as four rows rather than four rows of some larger set. The absence of a pagination marker supports the completeness of the retrieved view. It does not prove that nothing was omitted server-side, and I am not going to dress it up as proof.

Two pages. Nine identifiers. One shared value.

Four blocks, with their paperwork attached

Open the blocks individually and the record thickens. Each network detail page prints a net range, a CIDR, a name, a handle, a parent, a net type, an organization, a registration date and a last-updated date.

153.61.0.0/16 is the largest of the four and the newest. Net type Direct Allocation. Parent APNIC-ERX-153 (NET-153-0-0-0-0). Registration Date 2026-06-17. Last Updated 2026-07-09. A /16 is 65,536 IPv4 addresses, and this one is a fresh allocation, not an inherited block: it registered in June 2026.

160.79.104.0/21 is Direct Allocation, parent NET160 (NET-160-0-0-0-0), registered 2023-09-14, last updated 2025-01-23. A /21 is 2,048 addresses.

2607:6BC0::/32 is the IPv6 companion, printed under the name ANTHROPIC-V6. Direct Allocation, parent NET6-2600 (NET6-2600-1), registered 2023-09-14, last updated 2026-01-08. A /32 is 65,536 /48 site prefixes — the same count as the /16's address total, in a different unit, which is exactly the kind of coincidence a reader should not read as a coincidence.

216.73.216.0/22 is the odd one. Name AWS-ANTHROPIC. Net type Reassigned. Parent AMAZO-4 (NET-216-73-208-0-1). Registration Date 2024-06-05, Last Updated 2024-06-05, no movement in the record since the day it was made. A /22 is 1,024 addresses.

Three of four are what ARIN calls Direct Allocation. One is what ARIN calls Reassigned, and the parent handle on it is Amazon's. That is a documentary distinction with consequences, and the consequences are about who stands where in the chain — not about who is doing what with the addresses.

The two lists never meet

Here is the finding, and it is not a number.

On every one of the four network records, the field that would name an originating autonomous system is absent. On 153.61.0.0/16, absent. On 160.79.104.0/21, absent. On 216.73.216.0/22, absent. On 2607:6BC0::/32, absent.

On the other side, the autonomous-system records do not carry a network list. AS4167 prints Number 4167, Name AP-2440-4167, Handle AS4167, Organization Anthropic, PBC (AP-2440), Registration Date 2026-03-03, Last Updated 2026-03-03. AS399358 prints Number 399358, Name ANTHROPIC, Handle AS399358, Organization Anthropic, PBC (AP-2440), Registration Date 2023-09-20, Last Updated 2024-01-08.

Neither page prints a field labelled Status. Neither page carries an address block.

So the join ARIN supplies is the organization handle, and only the organization handle. Five ASNs in one column, four blocks in another, AP-2440 in both. If you want to know which of those five systems originates 153.61.0.0/16, or 160.79.104.0/21, or the /22, or the /32 — or whether any of them is announced at all — the registry page will not tell you, because on the pages read there is no field in which it could be said.

That is not a complaint about ARIN's completeness. The registry attests custody of an identifier. Custody of an AS number and custody of an address block are two separate acts of registration, and ARIN's file keeps them separate, joined by the party who holds both. Which network an address appears from is a routing fact, produced by whoever advertises it.

Two Comments fields, one certificate, one blank

The Comments row is where the interesting defect lives, and it is different on each of the two ASN records I read.

AS4167 carries a Comments row that is blank. Nothing at all. An autonomous system, registered 2026-03-03, whose entire prose content in the record is nothing.

AS399358 carries, in place of prose, a PEM certificate block. So does NET-153-61-0-0-1. Decoding the base64 embedded there is my work, not ARIN's, and I will label it as mine: the decoded block's subject names Anthropic, PBC, its common name reads byoip-prov, and its validity runs from 8 January 2026 to 8 January 2027.

I am not going to build a service claim on a common name. A certificate in a Comments field is a certificate in a Comments field. What it demonstrates is that two of the registry objects in this file carry a machine artefact where a human reader would look for a sentence, and one carries nothing. If you want to know what the holder of AP-2440 says about why it holds five AS numbers, the public record does not say it in words anywhere I read.

The arithmetic, and it is mine

Four printed blocks, converted into counts. These are my calculations from ARIN's printed prefixes, not figures ARIN prints.

  • 153.61.0.0/16 holds 65,536 IPv4 addresses.
  • 160.79.104.0/21 holds 2,048 IPv4 addresses.
  • 216.73.216.0/22 holds 1,024 IPv4 addresses.
  • The three IPv4 records together, added by me, are 68,608 addresses: 65,536 plus 2,048 plus 1,024.
  • 2607:6BC0::/32 holds 65,536 /48 site prefixes.

Dates, also mine, also subtraction. The organization handle registered 2023-07-31. The /21 and the /32 both show Registration Date 2023-09-14, which is 45 days after the handle. AS399358 shows 2023-09-20, which is 51 days after the handle and six days after those two blocks. AS4167 shows 2026-03-03. The /16 shows 2026-06-17, which is 106 days after AS4167's registration date.

I am not going to narrate those intervals into a story about what was being built when. A registration date is the date a record was registered. It is not a date of first use, a date of first announcement, or a date anyone plugged anything in.

What the intervals do establish is the shape of the file: the organization handle came first in mid-2023, an IPv6 /32 and a small IPv4 /21 arrived together in September 2023, an ASN arrived a week later, a second ASN arrived two and a half years after that, and the /16 arrived in the summer of 2026. Then four numbers of one sort and one of another sit in the same file with no line drawn between them.

The one printed name that names somebody else

216.73.216.0/22 is the only block of the four that does not carry a name derived from Anthropic's own handle. It carries AWS-ANTHROPIC. It is the only one of the four whose net type is Reassigned rather than Direct Allocation. It is the only one whose parent handle is not a legacy ARIN or APNIC range but a company: AMAZO-4.

Everything I can say about it is documentary. It is a /22 registered on 2024-06-05 inside a block ARIN attributes to AMAZO-4, printed under a name that joins a cloud provider's abbreviation to an AI lab's name, with the organization value on the page reading Anthropic, PBC (AP-2440).

What that does not establish: an operating relationship. A service. A traffic path. A facility. A contract. A machine. Somebody typed AWS-ANTHROPIC into a name field in June 2024, and ARIN recorded it, because that is what a registry does with a name field.

The distinction that matters is the documentary one. Three of Anthropic's four blocks sit on the record as allocations to Anthropic. One sits inside somebody else's parent, in the record type ARIN uses for a block administered under a parent allocation. A reader who wants to know what the difference means in practice is holding a registry question that the registry does not answer.

Why a lab that rents compute still wants an AS number

Set the file beside the ordinary public argument about AI infrastructure. That argument is about chips, megawatts, cooling, land, capital. It is a supply argument, and the numbers in it are counted in accelerators and watts.

The registry file is a different kind of object. An autonomous system number is the unit in which the global routing table is organised: a network advertises reachability for its prefixes under an originating system, and other networks make forwarding decisions on what they see advertised. Holding an AS number is holding a name in that system. Holding address blocks is holding the thing to advertise.

Five AS numbers and four blocks do not make a network. They make the administrative precondition for one. Which is precisely why the file is interesting and why the file is thin: the registry can tell you that a company took custody of the identifiers. It cannot tell you that anything was ever announced, because announcing is not a registry act.

That asymmetry is the finding. For a company whose product is a service reached over the public internet, the layer that decides who can reach it — the routing layer — is the layer whose public record is the least informative of the layers you can read. You can read a data-centre announcement and count megawatts. You can read a filing and count dollars. You can read the ARIN file for Anthropic, PBC and learn that five numbers and four blocks exist, and learn nothing whatever about which of the two lists touches the other.

What this record cannot establish

Four things, stated once, where they belong.

First: announcement. Nothing in these nine pages establishes that any of the five autonomous systems is announced in the global routing table, or that any of the four prefixes is originated by any of them. The registry does not carry that fact, and I have not gone and measured it.

Second: use. No page states that any address in any of the four blocks is assigned to a host, a service, an office, a router or a customer. An allocation is not a use.

Third: traffic. Nothing here says what traffic crosses anything, or for whose benefit.

Fourth: identity. The organization record names Anthropic, PBC, at a San Francisco mailing address, with handle AP-2440. Whether the entity printed in ARIN's file is the same legal person as the AI laboratory is a question for a company registry, not a number registry, and AP-2440 does not answer it.

There is a fifth limit, about scope. The nine pages I read were read on 22 November 2026. Two ASN detail pages were read in full; three ASNs — AS60808, AS400243 and AS401551 — appear only as names and handles on the organization listing, and I assert nothing about their registration dates, their status or their comments. Anyone who tells you otherwise is quoting a page I did not read.

Where the missing answer actually lives

The gap is not mysterious. It is a well-known division of labour, and the artefacts that close it have names.

A route origin authorisation would state which AS number is authorised to originate a given prefix; that is the object a reader wants and the registry file does not contain. An internet routing registry entry would state an origin relationship, in whatever the registrant chose to file. A border gateway protocol collector or a looking glass would show the announcement as observed from a particular vantage point, on a particular date. And a transfer or reassignment filing would explain the one block whose parent handle belongs to a cloud provider.

Each of those is a document someone holds. None of them is this document.

So the honest conclusion is not that Anthropic's holding is large or small, or that a lab is or is not building a network. It is that the join between five identifiers and four blocks exists in one field of one registry, that the field says AP-2440, and that everything a reader actually wants to know about the relationship between those numbers is answered outside it, by whoever is doing the announcing, on evidence they choose to publish.

BTW's directory record for Anthropic, PBC carries the entity; the registry record carries the identifiers; the routing table carries the answer.

A company can accumulate the paperwork of network identity without the registry ever printing a sentence about what the network is. ARIN's file for Anthropic, PBC is a clean example: five autonomous systems, four blocks, one handle, zero OriginAS, and a Comments row that either says nothing or says it in base64.