Network · data from 2026-11-12

AS209509 SERVATOR Servator Consulting GmbH

Registry name: SERVATOR Servator Consulting GmbH, DE · not in PeeringDB

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

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

6Route objects not announced registered with origin AS209509, seen from no peer

Announced routes

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


152.89.176.0/24	Valid	RIR databaseRIPE	673 100%	67
152.89.177.0/24	Valid	RIR databaseRIPE	673 100%	67
152.89.178.0/24	Valid	RIR databaseRIPE	673 100%	67
152.89.179.0/24	Valid	RIR databaseRIPE	673 100%	67
2a09:3340::/32	Valid	RIR databaseRIPE	635 100%	67
2a09:3344::/32	Valid	RIR databaseRIPE	635 100%	67
2a09:3346::/32	Valid	RIR databaseRIPE	635 100%	67
2a09:3347::/32	Valid	RIR databaseRIPE	635 100%	67

AS-SET

AS209509 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 6 are in fix.csv.

Route object: not announced6

Route objects not announced

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


152.89.176.0/22	RIPE	Valid
2a09:3340::/29	RIPE	Valid
2a09:3341::/32	RIPE	Valid
2a09:3342::/32	RIPE	Valid
2a09:3343::/32	RIPE	Valid
2a09:3345::/32	RIPE	Valid

152.89.176.0/22

RIPE

Valid

2a09:3340::/29

RIPE

Valid

2a09:3341::/32

RIPE

Valid

2a09:3342::/32

RIPE

Valid

2a09:3343::/32

RIPE

Valid

2a09:3345::/32

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.