Network · data from 2026-11-12

AS203865 OVERTURN overturn technologies GmbH

Registry name: OVERTURN overturn technologies GmbH, DE · not in PeeringDB

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

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

0RPKI invalid 0 origin · 0 maxLength

6No ROA 0 with no route object for this origin

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

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

Announced routes

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


80.89.64.0/23	No ROA	RIR databaseRIPE	673 100%	66
80.89.66.0/23	No ROA	RIR databaseRIPE	673 100%	66
80.89.68.0/23	No ROA	RIR databaseRIPE	673 100%	66
185.121.192.0/22	No ROA	RIR databaseRIPE	673 100%	67
2a02:1a8::/32	No ROA	RIR databaseRIPE	636 100%	67
2a0a:3a00::/32	No ROA	RIR databaseRIPE	636 100%	67
93.94.0.0/23	Valid	RIR databaseRIPE	673 100%	66
93.94.2.0/24	Valid	RIR databaseRIPE	673 100%	66
2a03:1e02::/32	Valid	RIR databaseRIPE	636 100%	67

AS-SET

AS203865 isn't in PeeringDB, where networks name their 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 7 are in fix.csv.

ROA: none6
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	80.89.64.0/23	No ROA covers it. Add a ROA for AS203865, maxLength 23.	673 of 673
ROA: none	80.89.66.0/23	No ROA covers it. Add a ROA for AS203865, maxLength 23.	673 of 673
ROA: none	80.89.68.0/23	No ROA covers it. Add a ROA for AS203865, maxLength 23.	673 of 673
ROA: none	185.121.192.0/22	No ROA covers it. Add a ROA for AS203865, maxLength 22.	673 of 673
ROA: none	2a02:1a8::/32	No ROA covers it. Add a ROA for AS203865, maxLength 32.	636 of 636
ROA: none	2a0a:3a00::/32	No ROA covers it. Add a ROA for AS203865, maxLength 32.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

80.89.64.0/23

No ROA covers it. Add a ROA for AS203865, maxLength 23.

673 of 673

ROA: none

80.89.66.0/23

No ROA covers it. Add a ROA for AS203865, maxLength 23.

673 of 673

ROA: none

80.89.68.0/23

No ROA covers it. Add a ROA for AS203865, maxLength 23.

673 of 673

ROA: none

185.121.192.0/22

No ROA covers it. Add a ROA for AS203865, maxLength 22.

673 of 673

ROA: none

2a02:1a8::/32

No ROA covers it. Add a ROA for AS203865, maxLength 32.

636 of 636

ROA: none

2a0a:3a00::/32

No ROA covers it. Add a ROA for AS203865, maxLength 32.

636 of 636

Route objects not announced

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


2a0a:3a01::/32	RIPE	No ROA

2a0a:3a01::/32

RIPE

No ROA

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.