Network · data from 2026-11-12

AS210235 JULIANKUHN

Registry name: JULIANKUHN Julian Kuhn, DE · PeeringDB

0IPv4 routes

2IPv6 routes 100.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

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

Announced routes

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


2a0f:b240:7c01::/48	Valid	Nonecovered by 2a0f:b240:7c00::/40	1 0%low visibility	2
2a0f:b240:7c00::/40	Valid	RIR databaseRIPE	636 100%	69

2a0f:b240:7c01::/48

Valid

Nonecovered by 2a0f:b240:7c00::/40

1 0%low visibility

2a0f:b240:7c00::/40

Valid

RIR databaseRIPE

636 100%

AS-SET

AS210235's PeeringDB record names no 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 1 are in fix.csv.

Route object: none1

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a0f:b240:7c01::/48	No route object for it. A route object for 2a0f:b240:7c00::/40 with origin AS210235 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210235 in the RIR database for the space.	1 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a0f:b240:7c01::/48

No route object for it. A route object for 2a0f:b240:7c00::/40 with origin AS210235 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210235 in the RIR database for the space.

1 of 636

Route objects not announced

Every route object with origin AS210235 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.