Network · data from 2026-11-12

AS216093 SERVERGUARD Root Localhost LLC

Registry name: SERVERGUARD Root Localhost LLC, US · not in PeeringDB

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

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

Announced routes

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


166.88.170.0/24	Valid	RIR databaseARIN, RADB	673 100%	67
193.124.4.0/24	Valid	RIR databaseRIPE	673 100%	66
194.87.11.0/24	Valid	RIR databaseRIPE	673 100%	66
195.133.51.0/24	Valid	RIR databaseRIPE	673 100%	66
194.87.28.0/24	Valid	RIR databaseRIPE	670 100%	67
212.192.242.0/24	Valid	RIR databaseRIPE	670 100%	67
2a0e:97c0:df1::/48	Valid	RIR databaseRIPE	636 100%	67
2a0e:97c0:df2::/48	Valid	RIR databaseRIPE	636 100%	67
2a0e:97c0:df0::/48	Valid	RIR databaseRIPE	635 100%	69
2a0e:97c0:df3::/48	Valid	RIR databaseRADB, RIPE	633 100%	68

AS-SET

AS216093 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 AS216093 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.