Network · data from 2026-11-12

AS208089 UNZER-AS Unzer Group GmbH

Registry name: UNZER-AS Unzer Group GmbH, DE · not in PeeringDB

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

1IPv6 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

2Route objects not announced registered with origin AS208089, seen from no peer

Announced routes

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


185.126.154.0/23	Valid	RIR databaseRADB, RIPE	673 100%	67
37.221.74.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
37.221.75.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
2a09:ea00::/40	Valid	RIR databaseRADB, RIPE	636 100%	67

AS-SET

AS208089 isn't in PeeringDB, where networks name their 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 2 are in fix.csv.

Route object: not announced2

Route objects not announced

Route objects with origin AS208089 whose prefix no peer sees AS208089 announce. Many are kept on purpose (backup routes, space announced only in some places).


37.221.72.0/24	RIPE	Valid
37.221.73.0/24	RIPE	Valid

37.221.72.0/24

RIPE

Valid

37.221.73.0/24

RIPE

Valid

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.