Network · data from 2026-11-12

AS209400 KurpfalzTEL

Registry name: KurpfalzTEL KurpfalzTEL GmbH, DE · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object

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

1RPKI invalid 0 origin · 1 maxLength

0No ROA 1 with no route object for this origin

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

1Route objects not announced registered with origin AS209400, seen from no peer

Announced routes

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


185.38.42.72/32	Invalid: maxLength	Nonecovered by 185.38.40.0/22	2 0%low visibility	6
37.228.140.0/22	Valid	RIR databaseRIPE	673 100%	66
45.66.120.0/22	Valid	RIR databaseRIPE	673 100%	66
85.208.244.0/22	Valid	RIR databaseRIPE	673 100%	66
94.199.208.0/22	Valid	RIR databaseRIPE	673 100%	66
185.38.40.0/22	Valid	RIR databaseRIPE	673 100%	66
2a00:fe20::/32	Valid	RIR databaseRIPE	635 100%	67

185.38.42.72/32

Invalid: maxLength

Nonecovered by 185.38.40.0/22

2 0%low visibility

37.228.140.0/22

Valid

RIR databaseRIPE

673 100%

45.66.120.0/22

Valid

RIR databaseRIPE

673 100%

85.208.244.0/22

Valid

RIR databaseRIPE

673 100%

94.199.208.0/22

Valid

RIR databaseRIPE

673 100%

185.38.40.0/22

Valid

RIR databaseRIPE

673 100%

2a00:fe20::/32

Valid

RIR databaseRIPE

635 100%

AS-SET

PeeringDB's irr_as_set for AS209400: AS-KURPFALZTEL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS209400 isn't in the set, or no route object for AS209400 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS209400 in it	Not covered
AS-KURPFALZTEL	RIPE	1	1	7	Yes	1

Name

Database

ASNs

Sets

Route objects

AS209400 in it

Not covered

AS-KURPFALZTEL

RIPE

Yes

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

ROA: maxLength1
Route object: none1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	185.38.42.72/32	ROA 185.38.40.0/22 AS209400 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 185.38.42.72/32.	2 of 673
Route object: none	185.38.42.72/32	No route object for it. A route object for 185.38.40.0/22 with origin AS209400 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS209400 in the RIR database for the space.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

185.38.42.72/32

ROA 185.38.40.0/22 AS209400 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 185.38.42.72/32.

2 of 673

Route object: none

185.38.42.72/32

No route object for it. A route object for 185.38.40.0/22 with origin AS209400 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS209400 in the RIR database for the space.

2 of 673

Route objects not announced

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


23.212.174.0/23	ARIN	Invalid: origin

23.212.174.0/23

ARIN

Invalid: origin

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.