Network · data from 2026-11-12

AS50873 David Doepelheuer

Registry name: AS50873 David Doepelheuer, DE · PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50873, 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.97.5.0/24	Valid	Nonecovered by 185.97.4.0/22	673 100%	66
94.247.143.0/24	Valid	RIR databaseRIPE	673 100%	66
185.97.4.0/22	Valid	RIR databaseRIPE	673 100%	66
194.104.114.0/23	Valid	RIR databaseRIPE	673 100%	66
194.104.149.0/24	Valid	RIR databaseRIPE	673 100%	66
37.228.130.0/24	Valid	RIR databaseRIPE	672 100%	66
2001:678:fb4::/48	Valid	RIR databaseRIPE	634 100%	67
2a06:1c0::/30	Valid	RIR databaseRIPE	633 100%	67
2001:678:580::/48	Valid	RIR databaseRIPE	125 20%	42

AS-SET

PeeringDB's irr_as_set for AS50873: AS-50873. 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 (AS50873 isn't in the set, or no route object for AS50873 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	AS50873 in it	Not covered
AS-50873	RIPE1 member set in no database: AS-MWSQ	14	7	103	Yes	0

Name

Database

ASNs

Sets

Route objects

AS50873 in it

Not covered

AS-50873

RIPE1 member set in no database: AS-MWSQ

103

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.

Route object: none1
AS-SET: missing member1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.97.5.0/24	No route object for it. A route object for 185.97.4.0/22 with origin AS50873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50873 in the RIR database for the space.	673 of 673
AS-SET: missing member	AS-50873	AS-50873 (RIPE) lists AS-MWSQ; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.97.5.0/24

No route object for it. A route object for 185.97.4.0/22 with origin AS50873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50873 in the RIR database for the space.

673 of 673

AS-SET: missing member

AS-50873

AS-50873 (RIPE) lists AS-MWSQ; no IRR database read has it.

Route objects not announced

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


185.97.6.0/24	RIPE	Valid

185.97.6.0/24

RIPE

Valid

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.