Network · data from 2026-11-12

AS219399 US-SERVINGA servinga GmbH

Registry name: US-SERVINGA servinga GmbH, DE · not in PeeringDB

10IPv4 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

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

Announced routes

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


89.127.199.0/24	Valid	RIR databaseRIPE	673 100%	67
95.133.228.0/22	Valid	RIR databaseRIPE	673 100%	67
130.17.3.0/24	Valid	RIR databaseRIPE	673 100%	67
130.17.29.0/24	Valid	RIR databaseRIPE	673 100%	67
194.154.27.0/24	Valid	RIR databaseRIPE	673 100%	67
199.195.196.0/24	Valid	RIR databaseRIPE	673 100%	67
217.177.75.0/24	Valid	RIR databaseRIPE	673 100%	67
31.172.69.0/24	Valid	RIR databaseRIPE	672 100%	67
31.172.79.0/24	Valid	RIR databaseRIPE	672 100%	67
81.85.77.0/24	Valid	RIR databaseRIPE	672 100%	67
2a0b:7140:8::/48	Valid	RIR databaseRIPE	634 100%	67

AS-SET

AS219399 isn't in PeeringDB, where networks name their 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 AS219399 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.