Summary

The name DFINFRA is not a company in the RIPE Database; it is a role object. Third-party mirrors reproduce it as nic-hdl DA9499-RIPE, Hamburg, maintainer EDDI-MNT, created 10 June 2021, last modified 27 October 2021, serving as both admin-c and tech-c of AS210860 (as-name 'edeka_digital', organisation ORG-EDG14-RIPE).https://whois.ipip.net/AS210860 https://ip.cc/topic/asn/AS210860/ That makes DFINFRA, on paper, the person or team a network operator, an abuse reporter or a registry would contact about this autonomous system. The question this briefing asks — and which seventeen prior BTW articles about this subject did not — is what the public record shows about the accountability that contact function implies when the network behind it went silent.

The routing side of the record is unambiguous in direction. Hurricane Electric's BGP toolkit reports AS210860 has not been visible in the global routing table since 26 March 2026, with zero prefixes announced across IPv4 and IPv6, a single historically originated prefix of 193.21.248.0/21 described as EDEKA DIGITAL GmbH, and one observed peer, AS9211 (Nawork Internet Informationssysteme GmbH).https://bgp.he.net/AS210860 CIDR Report independently classifies the AS as NOT Announced, meaning it is not currently used to announce prefixes nor as a visible transit AS.https://www.cidr-report.org/cgi-bin/as-report?as=AS210860&view=2.0 IPinfo labels the ASN Inactive with zero prefixes, holder 'EDEKA Verwaltungs- und Beteiligungs GmbH', registry RIPE, created 24 August 2021 and last modified 27 October 2021.https://ipinfo.io/AS210860

Against that measured silence stands a self-declaration. A PeeringDB-derived record, mirrored by HostDirhttps://whois.ipip.net/AS210860 https://hostdir.net/networks/as210860-edeka-digital, presents AS210860 as 'EDEKA DIGITAL' with an open peering policy, scope 'Not Disclosed', network type 'Other', ten IPv4 prefixes and one IPv6 prefix.https://www.peeringdb.com/asn/210860 Every independent observer retained contradicts it. The claim of ten announced prefixes conflicts with the single historic origin HE reports; the claimed peer picture conflicts with the one peer actually observed.https://bgp.he.net/AS210860 https://www.peeringdb.com/asn/210860

The registry plane is less clean than either side would like. The mirrors that reproduce the DFINFRA role also conflict with each other: on the organisation name for ORG-EDG14-RIPE ('EDEKA DIGITAL GmbH' in one mirror versus 'EDEKA Verwaltungs- und Beteiligungs GmbH', District court Hamburg HRB 90516, last modified 13 May 2026, in another), and on the observed peer (an excerpt attributing AS32787, Akamai Technologies, versus Hurricane Electric's AS9211).https://ip.cc/topic/asn/AS210860/ https://www.cidr-report.org/cgi-bin/as-report?as=AS210860&view=2.0 The RIPEstat announced-prefixes endpoint for AS210860 returned no payload during this research, so the zero-prefix conclusion rests on the three observers above plus prior reporting rather than a directly inspected RIPEstat response.https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS210860 A low-confidence aggregator, checkip.com, lists the AS as 'Active' with a 2025-03-25 registration date while leaving every routing field empty — a status label that conflicts with IPinfo's 'Inactive' and with the observers.https://checkip.com/asn/AS210860/ The authoritative RIPE REST record for DA9499-RIPE and the RIPEstat data endpoint were both not retrievable in this run, so every conclusion about the record's current content is second-hand until those endpoints can be re-checked directly.https://rest.db.ripe.net/ripe/role/DA9499-RIPE.json https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS210860

What the record does not contain is as telling as what it does. No incident notice, outage report or abuse-handling statement from or about DFINFRA appears anywhere in the retained corpus.https://btw.media/en/governance/rir-watchdog/ripe-ncc/story/dfinfra-as210860-routing-evidence-september-2026 https://btw.media/en/dfinfra-as210860-routing-continuity-evidence Absence in this corpus is not proof of absence — prior BTW reporting on this subject is also the only source so far to trace the record's continuity — but it means the seventeen existing articles covering registry identity, routing divergence, a lifecycle ledger and the absence of commercial evidence never touched the function a contact object nominally performs: incident response.https://btw.media/en/governance/rir-watchdog/ripe-ncc/story/dfinfra-as210860-routing-evidence-september-2026 https://btw.media/en/dfinfra-as210860-routing-continuity-evidence

The accountability picture that emerges is procedural, not personal. A role object has no authority, no mailbox that can be audited publicly and no obligation in the retained record to answer anything. When its network stopped announcing prefixes on 26 March 2026, no mechanism in the public record required a notification to anyone, no update followed, and the mirrors drifted: one org name was last modified in October 2021, the other in May 2026, describing what is nominally the same organisation handle.https://whois.ipip.net/AS210860 https://ip.cc/topic/asn/AS210860/ https://ipinfo.io/AS210860 Prevention and detection, where they existed, left no trace in public sources. The holders behind AS210860 — a Hamburg holding company per the mirrors — have made no statement retained here about the network's status.https://whois.ipip.net/AS210860

Three conditions would resolve this record, and each is observable. First, a direct retrieval of the authoritative RIPE REST object for DA9499-RIPE and a RIPEstat query for AS210860, replacing mirror-based inference with a primary read.https://rest.db.ripe.net/ripe/role/DA9499-RIPE.json https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS210860 Second, an identified change event: a modification to the role or aut-num object, or a statement from the organisation, that names the party responsible for the stale contact data. Third, re-observation after an interval — persistent, independently verified prefix announcements would contradict the current dormant picture, as would a service description connecting the footprint to real customers.https://bgp.he.net/AS210860 https://www.peeringdb.com/asn/210860 Until then, the honest finding is bounded: a registry contact that the public record cannot verify, attached to a network no observer has seen routing since March 2026, contradicted by a self-declaration no independent source supports, and answerable — as far as the public record shows — to no one.