Summary
- AS210860 has not appeared in the global routing table since 26 March 2026, and the Hurricane Electric listing — page updated 14 July 2026 — still shows zero announced prefixes, zero RPKI-valid originations and a single observed peer, AS9211 (Nawork Internet Informationssysteme GmbH) https://bgp.he.net/AS210860.
- The PeeringDB-derived record for EDEKA DIGITAL still self-declares 10 IPv4 prefixes, 1 IPv6 prefix and an open peering policy, in direct contradiction of every routing observation retained here https://hostdir.net/networks/as210860-edeka-digital.
- The aut-num AS210860 and the DFINFRA role object (nic-hdl DA9499-RIPE) remain last-modified 27 October 2021; the only 2026 registry change observed is the organisation object's 13 May 2026 modification, which predates September coverage https://whois.ipip.net/AS210860.
- RIPEstat's snapshot of 14 September 2026 shows no prefixes visible in RIS and renders the RIR registration status as RESERVED with no holder — unexplained against the mirror's ASSIGNED status https://stat.ripe.net/resource/AS210860.
- Nothing in the retained sources shows any observable change after BTW's 26-27 September 2026 reporting. The contradiction persists unremediated, and no party bears the cost of resolving it. This directory record tracks the subject: https://btw.media/en/directory/dfinfra
The state difference is null, and that is the finding
The question this report set out to answer was narrow: after BTW documented in late September 2026 that AS210860 had gone silent — no announced prefixes since 26 March 2026 — did anything observable change? The retained evidence answers no.
Hurricane Electric's BGP Toolkit listing for AS210860 states the network "has not been visible in the global routing table since March 26, 2026" and shows Prefixes Announced (all): 0, with zero RPKI-valid and zero RPKI-invalid originations https://bgp.he.net/AS210860. The page carries an update stamp of 14 July 2026, which limits how current the claim can be; it is a listing, not continuous measurement. RIPEstat independently shows, on a snapshot dated 2026-09-14, that the AS does not originate prefixes visible in RIS and is not seen transiting https://stat.ripe.net/resource/AS210860. Neither source records a re-announcement.
What did not change
The registry layer is equally static. The RIPE Database mirror shows aut-num AS210860 (as-name edeka_digital, org ORG-EDG14-RIPE, status ASSIGNED) with admin-c and tech-c DA9499-RIPE — the role object named DFINFRA — created 24 August 2021 and last modified 27 October 2021, with declared upstreams AS9211 and AS13237 https://whois.ipip.net/AS210860. The organisation object ORG-EDG14-RIPE records EDEKA Verwaltungs- und Beteiligungs GmbH (District court Hamburg HRB 90516) with a last-modified timestamp of 13 May 2026. That is the only post-2021 registry change in the retained corpus, and it predates the September coverage window.
The market surface did not change either. The HostDir record, sourced from PeeringDB, still self-declares that EDEKA DIGITAL operates AS210860 "announcing 10 IPv4 prefixes and 1 IPv6 prefixes" with an open peering policy and IRR AS-SET AS210860 https://hostdir.net/networks/as210860-edeka-digital. No timestamp is exposed, so whether the record was touched after September cannot be determined from the excerpt — but no alignment with observed routing is visible.
Where the mirrors disagree
The retained sources disagree with one another in ways that matter for anyone consuming them. IPinfo labels AS210860 "Inactive" with zero hosted addresses https://ipinfo.io/AS210860. IP.CC attributes one IPv4 prefix (193.21.248.0/21) and a peer AS32787 (Akamai Technologies) to the AS, conflicting with Hurricane Electric's single observed peer AS9211 https://ip.cc/topic/asn/AS210860/. RIPEstat renders the RIR registration status as RESERVED with no holder, while the mirror shows ASSIGNED https://stat.ripe.net/resource/AS210860. A DCXV transfer record dated 23 December 2025 ties an EDEKA DIGITAL GmbH to EDEKA Verwaltungs- und Beteiligungs GmbH movement to 193.20.0.0/15, while internally describing a single /24 — an inconsistency that caps how much weight the detail can carry, though the direction of the corporate movement is corroborated by the org-object update https://dcxv.com/ipv4/transfer/694b3b9e0f62eb0d918212e0. CIDR Report's classification of the AS as announcing no prefixes is relayed secondhand in this corpus and undated at source https://www.cidr-report.org/cgi-bin/as-report?as=AS210860&view=2.0.
Prior coverage as baseline
BTW's own reporting of 26 and 27 September 2026 established the baseline this report tests: unrouted since 26 March 2026, aut-num unchanged since 2021, DFINFRA as role DA9499-RIPE, and a PeeringDB self-declaration of ten prefixes https://btw.media/en/governance/rir-watchdog/ripe-ncc/story/dfinfra-as210860-routing-evidence-september-2026. The lifecycle-ledger article added the role object's 2021 creation date and revised the interpretation — administrative scaffolding preceded the ASN — while defining the next observable conditions: persistent re-announcement, a PeeringDB edit, a new route object, or a newer aut-num timestamp https://btw.media/en/governance/rir-watchdog/ripe-ncc/story/dfinfra-as210860-lifecycle-ledger. None of those conditions appears in the current evidence.
The bounded consequence
A dormant registry record that outlives its network imposes a quiet tax: every counterparty, register consumer or observer who consults the self-declared PeeringDB surface must reconcile it against observed routing at their own expense. Six months after the routing silence began, the retained record shows no party has done so publicly. The contradiction is not self-correcting because no mechanism assigns the correction to anyone.
The next observable condition that would change this picture remains the one prior coverage defined: persistent, independently corroborated re-announcement by AS210860, a PeeringDB edit, or a newer registry timestamp. Until one of those appears, the honest description of the state is exactly what the evidence shows — unchanged.
Member Briefing
Deeper Profile Context
Sign in with the right membership level to unlock the full briefing and source notes.
Only for Strategic Circle
Strategic Circle
Open to all readers. Unlock profile briefings after joining and signing in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance
For qualified IP-asset owners and management; sign in to unlock alliance briefings.
Join Leadership Alliance
