Summary

  • ARIN's Whois-RWS record for AS7843 lists Organization Charter Communications Inc (CC-3517) alongside Name TWC-7843-BB: registry recognition moved with the roll-up, the operational label did not.
  • ARIN's manual routes transfer recipients to section 8.5, restricts transferred resources to use on an operational network and gates additional space on documented utilisation of at least 50% of cumulative blocks. A legacy estate is a use obligation with continuity value, not inventory a holder can liquidate at a scarcity price.

Two fields on one page carry the whole story. ARIN's Whois-RWS record for AS7843, read on 11 November 2026, shows Number 7843, Name TWC-7843-BB, Handle AS7843 and, on its own line, Organization Charter Communications Inc (CC-3517). It is short enough to print on a card and specific enough to settle an argument that usually runs on rumour: whatever the network is named after, the organisation the registry recognises is Charter.

Read the two lines as different instruments, because that is what they are. The Organization field names the entity the registry holds responsible for the resource, with its own handle, CC-3517. The Name field is the label carried on the autonomous system object itself, TWC-7843-BB. Only the first is a registrant. The second is a name plate, and name plates in routing are famously conservative: engineers keep them because peer configurations, filters and monitoring dashboards point at them long after the corporate entity behind them has been folded into something larger.

What the record does not do is date itself. It reports current registry state, not a filing, and nothing on the page establishes the day the organization field changed. Anyone claiming to know the exact moment recognition moved is reading something else. What can be said is narrower and still useful: at the moment of reading, the registry attributed AS7843 to Charter Communications Inc while the object still displayed the predecessor's operational label.

The interesting part is not the archaeology. It is what the registry permits a holder to do with what it recognises.

Read ARIN's Number Resource Policy Manual and the scarcity story develops a puncture. The manual is explicit that issuance is not a sale: “Number resources are issued, based on justified need, to organizations, not to individuals representing those organizations.” Transfers are not a shortcut around that logic. “The recipients must meet the transfer requirements as defined in section 8.5,” and “ARIN allocates or assigns number resources to organizations via transfer solely for the purpose of use on an operational network.” The manual then converts “use” from a slogan into arithmetic: “Organizations may qualify for the transfer of a larger initial block, or an additional block, by providing documentation to ARIN which details the use of at least 50% of the requested IPv4 block size within 24 months.”

The cumulative test is stricter still, because it follows the space wherever it went: “Organizations with an IPv4 allocation from ARIN must have efficiently utilized at least 50% of their cumulative IPv4 address blocks in order to receive additional IPv4 addresses. This includes all IPv4 space reallocated and/or reassigned to their customers.” A second door opens at a higher threshold: “Organizations may qualify for additional IPv4 address blocks by demonstrating 80% utilization of their currently allocated space.” The page identifies itself as Version 2025.1, dated 3 March 2026, and states that it supersedes previous versions.

Nothing in that text prices an address. Everything in it conditions one. That distinction is where most roll-up arithmetic quietly goes wrong. In the buyer's model, a legacy estate resembles a store of value: acquired with the plant, carried at zero, marked up in the imagination whenever scarcity makes headlines. In the registry's model, the same estate is a record of justified need, an operating obligation and a set of utilisation figures somebody has to produce when the next block is requested.

For a consolidator the consequence runs in both directions. Absorbing an operating network inherits the addresses with their history attached, including the fact that reallocations to customers count toward cumulative utilisation rather than against it. The estate is not stranded by policy; it is chained to use by it. That is a very different asset: it supports service, it supports growth, and it does not support a story in which the block is quietly sold at a scarcity premium to whoever pays most, because the buyer at the other end must also satisfy section 8.5 and put the space on an operational network.

There is a legitimate counter-argument, and it deserves stating plainly. Transfers do happen, registries do approve them, and an estate nobody uses is worth less than one in service. A policy that demands utilisation also pushes unused space toward someone who will use it, which is the point. My claim is narrower than “addresses cannot change hands.” It is that the change of hands is gated on operational use and documented utilisation, so the estate's value to this holder is continuity, and its value to a buyer is conditional. A consolidator that models legacy space as cash has modelled the wrong instrument.

A consolidator that models it as a licence to keep serving customers it already bills has modelled the right one.

The same test applies to the label. TWC-7843-BB persists because continuity is cheap and renumbering is not; whether it persists from operational caution, legacy routing convention or administrative inertia is not something the record settles, and this article will not pretend otherwise. What the record does settle is who the registry currently recognises, and what the manual says that recognition entitles them to do. Serve the network. Document the use. Ask again later.

Charter Communications (7843) is tracked in the BTW directory: Charter Communications directory entry.