Network operator associated with ASN/IP network resources
DFINFRA
DFINFRA has public ASN/IP network-resource records in United States, including AS210860, AS197909, AS9211 +2.
- Network operator associated with ASN/IP network resources
At a glance
- Autonomous system numberLinked with AS210860, AS197909, AS9211, AS13237 +1High confidence
Basic information
- Display nameDFINFRAHigh confidence
- Directory categoryCompanyHigh confidence
- Last updatedJun 15, 2026High confidence
Locations
- Geography scopeUnited StatesHigh confidence
- ASN/IP network resourcesUnited StatesMedium confidence
Network identity
- Autonomous system numberAS210860High confidence
- Autonomous system numberAS197909High confidence
- Autonomous system numberAS9211High confidence
- Autonomous system numberAS13237High confidence
- Autonomous system numberAS32787High confidence
Other network resources
- NetworkDFINFRA United States ASN/IP network resources · United StatesHigh confidence
People and contacts
- ContactsTechnicalMedium confidence
- Available contact typesTechnicalMedium confidence
Registry and related records
- Editorial contextEDEKA's organisation object stays live while the AS210860 aut-num record returns no entries, On 8 October 2026 the registered layer around EDEKA splits into two very different observations: the RIPE organisation object ORG-EDG14-RIPE is present and carries a 2026 last-modified date, while the aut-num record for AS210860 returns no entries on both RIPE Database query paths checked. The routing layer is simpler and firmer: 193.20.0.0/15 is announced live, solely by AS197909.Medium confidence
- Editorial contextWho answers for a silent network: DFINFRA's contact layer, the EDEKA merger and the accountability gap, The registered contact object behind AS210860 has been frozen since October 2021, names no individual, and sits behind an authoritative query endpoint that cannot be read. The legal entity it was created for no longer exists. This report examines what, if anything, the contact layer still proves about who is accountable for a network that has been silent in global routing since March 2026.Medium confidence
- Editorial contextWhen the registry cannot be read: DFINFRA, AS210860 and the broken verification chain, The EDEKA network stack behind BTW's directory entry [DFINFRA](https://btw.media/en/directory/dfinfra) has now been observed in a stable, contradictory state for months: a registered layer frozen since 2021, an autonomous system silent since March 2026, and a 1996 address block routed live by a different network inside the same group. That two-tier split is no longer the story. The story this report examines is the measurement layer underneath it — because in the October 2026 evidence pass, the authoritative RIPE Database endpoint for the DFINFRA role object returned only an application shell with no readable attributes, while every mirror that purports to reproduce the same records disagrees with every other mirror on names, dates and even routing counts. When the source of truth cannot be read, what does a registry claim actually prove?Medium confidence
- Editorial contextDFINFRA's second tier: the live routing that a frozen registry cannot see, While the RIPE objects tied to DFINFRA — the role handle DA9499-RIPE, the organisation ORG-EDG14-RIPE and the silent AS210860 — have shown no meaningful change since October 2021, the 1996 legacy address block underneath them is being routed live and stably by a different network: AS197909, registered as EDEKA-RS. This briefing examines what that operational second tier actually does, how stable its routing is, and what the split between recorded holdership and routed reality can and cannot prove about control.Medium confidence
- Editorial contextTwo tiers of EDEKA: where the frozen registry ends and live routing begins, A registry layer tied to BTW's directory entry DFINFRA has been frozen since 2021, and its autonomous system has been silent since March 2026 — yet the 1996 address block beneath it is being routed live, today, by a different EDEKA network. That split between recorded holdership and operational routing is the story the public record now tells.Medium confidence
- Editorial contextThe frozen stack: what DFINFRA's address footprint can and cannot prove, A RIPE role object created in 2021, an autonomous system that has announced nothing since March 2026, and a 1996 legacy address block make up the entire observable footprint behind BTW's directory entry DFINFRA ([directory entry]( https://btw.media/en/directory/dfinfra )). Read together, they prove registration continuity and historical routing activity. They also disprove any current demonstration of live routed infrastructure. What they cannot prove is who operates anything.Medium confidence
- Editorial contextThe company behind the dormant network: what the Hamburg register can prove that AS210860's registry layer cannot, For months, BTW has followed AS210860 — a RIPE autonomous system registered under the as-name `edeka_digital` and administered through the role object DFINFRA — as a test case in how much of an internet network's reality the public record can actually prove. The routing verdict has been stable since spring: the network has announced zero prefixes to the global routing table since 26 March 2026, according to independent observers [https://bgp.he.net/AS210860]( https://bgp.he.net/AS210860 ) [https://stat.ripe.net/AS210860]( https://stat.ripe.net/AS210860 ). The registry verdict has not been stable in the same way. Two third-party mirrors of the RIPE Database render the organisation object ORG-EDG14-RIPE with two different company names, and the authoritative RIPE Database endpoint has repeatedly failed to return readable object values at all [https://ip.cc/topic/asn/AS210860/]( https://ip.cc/topic/asn/AS210860/ ) [https://ipinfo.io/AS210860]( https://ipinfo.io/AS210860 ) [https://apps.db.ripe.net/db-web-ui/lookup?key=AS210860&type=aut-num]( https://apps.db.ripe.net/db-web-ui/lookup?key=AS210860&type=aut-num ).Medium confidence
- Editorial contextAS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRA, For nearly a year, BTW has followed DFINFRA — a name attached to the RIPE role handle DA9499-RIPE — as a test case in how much of an internet network's reality the public record can actually prove. The September 2026 investigations established a careful conclusion: the association between DFINFRA and autonomous system AS210860 is a real registry signal, but it is not proof of operational control, service continuity or commercial consequence. That coverage carried an explicit concession. Every registry value in the record was mirror-derived, because the authoritative RIPE Database endpoint returned only an application shell, not object data. This article takes that concession seriously as the subject of its own investigation: it re-attempts the first-party read, documents the exact failure again, and then asks what an evidence chain can bear when its authoritative anchor is structurally unreadable — while two independent mirrors agree on the core object, disagree on the organisation, and a first-party-adjacent service renders a status value that first-party documentation says cannot exist.Medium confidence
Source basis
- public registry sourceDFINFRA's public recordHigh confidence
- RIPEstat overview for AS210860RIPEstat provides public routing and registry context for AS210860 in the RIPE region and can be used to cross-check the autonomous system's public footprint.High confidence
- RIPE Database web query for AS210860The RIPE Database query page is a public registry source for checking the authoritative object record behind AS210860 and related contact or organisation references.High confidence
Related research
- Primary articleEDEKA's organisation object stays live while the AS210860 aut-num record returns no entriesHigh confidence
- Primary articleWho answers for a silent network: DFINFRA's contact layer, the EDEKA merger and the accountability gapHigh confidence
- Primary articleWhen the registry cannot be read: DFINFRA, AS210860 and the broken verification chainHigh confidence
- Primary articleDFINFRA's second tier: the live routing that a frozen registry cannot seeHigh confidence
- Primary articleTwo tiers of EDEKA: where the frozen registry ends and live routing beginsHigh confidence
- Primary articleThe frozen stack: what DFINFRA's address footprint can and cannot proveHigh confidence
- Primary articleThe company behind the dormant network: what the Hamburg register can prove that AS210860's registry layer cannotHigh confidence
- Primary articleAS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRAHigh confidence
- Primary articleDFINFRA and AS210860: When the Verification Layer Contradicts ItselfHigh confidence
- Primary articleDFINFRA/AS210860: The Routing Table Says Zero, the Directory Says TenHigh confidence
- Primary articleAS210860 after the silence: what changed since September — and the answer is nothingHigh confidence
- Primary articleDFINFRA and AS210860: what changes after a registry record outlives its networkHigh confidence
- Primary articleDFINFRA and AS210860: the cost of verifying a silent registry recordHigh confidence
- Primary articleDINFRA and DFINFRA: correcting a name collision between a Siegen datacenter venture and EDEKA's registry roleHigh confidence
- Primary articleDFINFRA and AS210860: who answers when a registry contact's network goes silentHigh confidence
- Primary articleDFINFRA and AS210860: the lifecycle ledger of a silent networkHigh confidence
- Primary articleDFINFRA and AS210860: Running the Commercial Half of a Test BTW Defined but Never ExecutedHigh confidence
- Primary articleDFINFRA and AS210860: The Registry Says One Thing, the Routing Table Says Nothing — and Neither Has MovedHigh confidence
- Primary articleDFINFRA Is a Registry Contact Role, Not a Carrier: Reading AS210860 Against the RegistryHigh confidence
- Primary articleDFINFRA and AS210860: What the Public Record Can—and Cannot—Show About DeploymentHigh confidence
- Primary articleDFINFRA and AS210860: What Would Prove an Operating Network?High confidence
- Primary articleDFINFRA and AS210860: The Evidence Stops Before Operational ControlHigh confidence
- Primary articleDFINFRA and AS210860: The Missing Continuity LoopHigh confidence
- Primary articleDFINFRA and AS210860: The Missing Link Between Registration and Operational ControlHigh confidence
- Primary articleDFINFRA and AS210860: The Control Chain Is Defined, but Not Yet ProvenHigh confidence
- Primary articleDFINFRA and AS210860: The Control Chain Is Still UnprovenHigh confidence
- Primary articleDFINFRA and AS210860: The Evidence Chain Still Stops Short of Operational ControlHigh confidence