Network · data from 2026-11-12

AS215365 Threatoff

Registry name: Threatoff Tom Gewiese, DE · PeeringDB

21IPv4 routes 100.0% RPKI valid · 90.5% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


77.90.61.0/24	Valid	None	671 100%	66
77.90.63.0/24	Valid	None	671 100%	66
5.231.117.0/24	Valid	RIR databaseRIPE	672 100%	66
5.231.118.0/24	Valid	RIR databaseRIPE	672 100%	66
5.231.119.0/24	Valid	RIR databaseRIPE	672 100%	66
5.231.123.0/24	Valid	RIR databaseRIPE	672 100%	66
85.93.2.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.177.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.178.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.179.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.184.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.186.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.187.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.188.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.189.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.195.0/24	Valid	RIR databaseRIPE	672 100%	66
94.249.198.0/24	Valid	RIR databaseRIPE	672 100%	66
217.69.167.0/24	Valid	RIR databaseRIPE	672 100%	66
77.90.15.0/24	Valid	RIR databaseRIPE	671 100%	66
77.90.52.0/24	Valid	RIR databaseRIPE	671 100%	66
77.90.60.0/24	Valid	RIR databaseRIPE	671 100%	66
2a09:3f00:1007::/48	Valid	RIR databaseRIPE	634 100%	69
2a09:3f00:1008::/48	Valid	RIR databaseRIPE	634 100%	69
2a09:3f00:1009::/48	Valid	RIR databaseRIPE	634 100%	69
2a09:3f00:3000::/40	Valid	RIR databaseRIPE	634 100%	69
2a14:7c0:1000::/38	Valid	RIR databaseRIPE	634 100%	69

AS-SET

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

Route object: none2
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	77.90.61.0/24	No route object for it. Add a route object with origin AS215365 in the RIR database for the space.	671 of 673
Route object: none	77.90.63.0/24	No route object for it. Add a route object with origin AS215365 in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

77.90.61.0/24

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

671 of 673

Route object: none

77.90.63.0/24

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

671 of 673

Route objects not announced

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


185.129.84.0/22	RIPE	Valid

185.129.84.0/22

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.