Network · data from 2026-11-12

AS197909 EDEKA-RS

Registry name: EDEKA-RS EDEKA Rechenzentrum Sued Betriebs GmbH, DE · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object

5IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS197909, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS197909, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


94.154.2.0/24	Valid	RIR databaseRIPE	673 100%	66
185.240.72.0/22	Valid	RIR databaseRIPE	673 100%	66
193.20.0.0/15	Valid	RIR databaseRIPE	673 100%	66
193.35.80.0/22	Valid	RIR databaseRIPE	673 100%	66
2a0d:6140::/32	Valid	RIR databaseRIPE	635 100%	67
2a07:2680::/29	Valid	RIR databaseRIPE	634 100%	67
2a0c:7580::/29	Valid	RIR databaseRIPE	634 100%	67
2a0d:6140::/29	Valid	RIR databaseRIPE	634 100%	67
2a12:ee40::/29	Valid	RIR databaseRIPE	632 99%	67

AS-SET

AS197909's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS197909 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.