Network · data from 2026-11-12

AS218208 Jaeger Tom Jaeger

Registry name: Jaeger Tom Jaeger, DE · not in PeeringDB

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

2IPv6 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 AS218208, seen from no peer

Announced routes

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


217.216.176.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67
2a0c:9a40:e1c0::/48	Valid	RIR databaseRIPE	636 100%	67
2a14:7581:5500::/40	Valid	RIR databaseRIPE	633 100%	67

AS-SET

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