Network · data from 2026-11-12

AS41167 REWE digital GmbH

Registry name: REWE-RIS-AS REWE digital GmbH, DE · PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No 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 AS41167, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41167, 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.


84.38.192.0/20	No ROA	RIR databaseRIPE	673 100%	67
217.110.62.0/24	Valid	RIR databaseRIPE	673 100%	67
217.111.44.0/24	Valid	RIR databaseRIPE	673 100%	67

AS-SET

AS41167's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 1 are in fix.csv.

ROA: none1

Change	Prefix or set	Detail	Full-table peers
ROA: none	84.38.192.0/20	No ROA covers it. Add a ROA for AS41167, maxLength 20.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

84.38.192.0/20

No ROA covers it. Add a ROA for AS41167, maxLength 20.

673 of 673

Route objects not announced

Every route object with origin AS41167 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.