Summary

  • ARIN's record for AS3356 names the organization as Level 3 Parent, LLC under handle LPL-141, with a registration date of 10 March 2000 and a last update of 20 February 2018.
  • Brand, contracting entity and registry registrant are three different layers, so an address-resource valuation that starts from the brand starts in the wrong document.

The line worth reading twice

ARIN's own record states it plainly: "Autonomous System Number 3356 Name LEVEL3 Handle AS3356 Organization Level 3 Parent, LLC (LPL-141) Registration Date 2000-03-10 Last Updated 2018-02-20" (https://whois.arin.net/rest/asn/AS3356). Three things in that line do the work. The organization is a named legal person. The handle is LPL-141. And the file has not been refreshed since 20 February 2018.

A 2018 timestamp is a diligence trigger, not a verdict. Nothing in the record says Level 3 Parent, LLC has been dissolved, renamed or replaced as registrant, and a 2000 registration date proves neither uninterrupted operation nor present control. What the record does establish is narrower and far more useful: whoever holds registry-recognised authority over AS3356 is a specific entity with a specific handle, and that entity does not carry the Lumen name.

Three layers sharing one story

The brand is Lumen Technologies, which publishes its SEC filings through its investor-relations site (https://www.lumen.com/en-us/about/investor-relations/financial-reporting/sec-filings.html). The routing identity is AS3356, which public routing data associates with Level 3's global backbone (https://bgp.he.net/AS3356). The registry registrant is Level 3 Parent, LLC. Four names are doing different jobs here: Lumen Technologies is the brand and the filer; Level 3 Parent, LLC is the organization the registry lists for the backbone system; ARIN is the registry that publishes the handle; and AT&T is the counterparty named in secondary reporting of a fibre agreement, with Bean Capital Limited as the publisher of that item rather than a party to anything.

The BTW directory entry for Lumen (https://btw.media/en/directory/lumen Only for Strategic Circle) files the group under its operating brand, which is what a directory should do. The registry file is not a directory and cannot be read as one.

Why a fibre disposal does not answer the resource question

A market item dated 26 May 2025, carried by MENAFN and attributed to Bean Capital Limited, reports that AT&T agreed to acquire Lumen's Mass Markets fibre internet business (https://menafn.com/1109594315/Bean-Capital-Limited-Highlights-ATT-Agrees-To-Buy-Lumens-Mass-Markets-Fiber-Internet-Business). That is secondary market commentary. The executed agreement, the consideration and any asset schedules were not read for this article, so the item establishes an agreement as reported and nothing about closing.

It also says nothing about AS3356. A transaction can move fibre, obligations and customer relationships while number resources stay retained, shared, licensed or simply outside the perimeter. Only schedules and closing documents settle which of those happened. Anyone who reads a headline about Mass Markets fibre and infers something about address space has skipped the one document that would decide it — and that is a valuation error dressed as diligence.

What the record does not contain

No block-level inventory is asserted here. The organisation record behind handle LPL-141 could not be read for this article, so no count, delegation date or utilisation figure for IPv4 resources recorded to that registrant appears in these pages (https://whois.arin.net/rest/org/LPL-141). An autonomous system number and an organisation handle are not proxies for a portfolio. Treating them as one is how a scope limit quietly becomes an invented number.

What survives that boundary is still worth money. If registry-recognised authority sits with a named entity, then every step that requires the registry to act — a transfer, an update to the record, an authorisation that depends on whom ARIN recognises — runs through that entity's cooperation. That dependency has a price. The price is not the age of a database field.

The handle is the diligence trail

Trace LPL-141 and you arrive at the registrant. Trace the brand and you arrive at a press release. For anyone valuing Lumen's address resources, the second route is comfortable, conventional and wrong.