Network · data from 2026-11-12

AS201790 Respawnhost

Registry name: Respawnhost Joshua Eliah Gerke, DE · PeeringDB

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

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

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

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

Announced routes

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


2a07:cec0:3::/48	Valid	None	636 100%	67
5.175.214.0/24	Valid	RIR databaseRIPE	673 100%	67
5.83.151.0/24	Valid	RIR databaseRIPE	670 100%	67
2a09:3f00:3b00::/48	Valid	RIR databaseRIPE	627 99%	67

AS-SET

AS201790'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	2a07:cec0:3::/48	No route object for it. Add a route object with origin AS201790 in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a07:cec0:3::/48

No route object for it. Add a route object with origin AS201790 in the RIR database for the space.

636 of 636

Route objects not announced

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