Network · data from 2026-11-12

AS49879 HOSTHANE

Registry name: HOSTHANE Dincer Isik trading as ISIK Bilgisayar Internet ve Yayincilik Hizmetleri, TR · PeeringDB

24IPv4 routes 100.0% RPKI valid · 95.8% with a route object

0IPv6 routes

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 AS49879, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49879, 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.141.109.0/24	Valid	None	672 100%	66
185.21.204.0/22	Valid	RIR databaseRIPE	672 100%	66
185.21.204.0/24	Valid	RIR databaseRIPE	672 100%	66
185.21.205.0/24	Valid	RIR databaseRIPE	672 100%	66
185.21.206.0/24	Valid	RIR databaseRIPE	672 100%	66
185.21.207.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.192.0/21	Valid	RIR databaseRIPE	672 100%	66
217.116.192.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.193.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.194.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.195.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.196.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.197.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.198.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.199.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.200.0/21	Valid	RIR databaseRIPE	672 100%	66
217.116.200.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.201.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.202.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.203.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.204.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.205.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.206.0/24	Valid	RIR databaseRIPE	672 100%	66
217.116.207.0/24	Valid	RIR databaseRIPE	672 100%	66

AS-SET

AS49879'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 2 are in fix.csv.

Route object: none1
Route object: not announced1

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

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.141.109.0/24

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

672 of 673

Route objects not announced

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


2a00:5fe0::/48	RIPE	No ROA

2a00:5fe0::/48

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.