bgpreport

Network · data from 2026-11-12

AS42846 guzelhosting GNET Internet Telekomunikasyon A.S.

Registry name: guzelhosting GNET Internet Telekomunikasyon A.S., TR · not in PeeringDB

46IPv4 routes 100.0% RPKI valid · 95.7% with a route object
2IPv6 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
0Route objects not announced registered with origin AS42846, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42846, 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.
70.40.138.0/24 Valid None 673 100% 67
70.40.139.0/24 Valid None 673 100% 67
89.252.151.0/24 Valid RIR databaseRIPE 673 100% 67
89.252.152.0/24 Valid RIR databaseRIPE 673 100% 67
89.252.179.0/24 Valid RIR databaseRIPE 673 100% 67
89.252.180.0/24 Valid RIR databaseRIPE 673 100% 67
89.252.181.0/24 Valid RIR databaseRIPE 673 100% 67
89.252.182.0/24 Valid RIR databaseRIPE 673 100% 67
89.252.183.0/24 Valid RIR databaseRIPE 673 100% 67
89.252.184.0/24 Valid RIR databaseRIPE 673 100% 67
89.252.185.0/24 Valid RIR databaseRIPE 673 100% 67
89.252.187.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.160.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.161.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.162.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.163.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.164.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.165.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.166.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.167.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.168.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.169.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.173.0/24 Valid RIR databaseRIPE 673 100% 67
104.247.179.0/24 Valid RIR databaseRIPE 673 100% 67
45.84.189.0/24 Valid RIR databaseRIPE 672 100% 67
45.84.191.0/24 Valid RIR databaseRIPE 672 100% 67
46.45.136.0/24 Valid RIR databaseRIPE 672 100% 67
46.45.137.0/24 Valid RIR databaseRIPE 672 100% 67
46.45.138.0/24 Valid RIR databaseRIPE 672 100% 67
46.45.139.0/24 Valid RIR databaseRIPE 672 100% 67
89.252.186.0/24 Valid RIR databaseRIPE 672 100% 67
31.192.212.0/24 Valid RIR databaseRIPE 671 100% 67
31.192.214.0/24 Valid RIR databaseRIPE 671 100% 67
46.45.133.0/24 Valid RIR databaseRIPE 671 100% 67
89.252.134.0/24 Valid RIR databaseRIPE 671 100% 67
89.252.137.0/24 Valid RIR databaseRIPE 671 100% 67
89.252.138.0/24 Valid RIR databaseRIPE 671 100% 67
89.252.159.0/24 Valid RIR databaseRIPE 671 100% 67
89.252.178.0/24 Valid RIR databaseRIPE 671 100% 67
159.253.37.0/24 Valid RIR databaseRIPE 671 100% 67
185.106.208.0/24 Valid RIR databaseRIPE 671 100% 67
185.106.209.0/24 Valid RIR databaseRIPE 671 100% 67
185.106.210.0/24 Valid RIR databaseRIPE 671 100% 67
185.106.211.0/24 Valid RIR databaseRIPE 671 100% 67
45.84.188.0/24 Valid RIR databaseRIPE 670 100% 67
45.84.190.0/24 Valid RIR databaseRIPE 670 100% 67
2a06:41c0:1::/48 Valid RIR databaseRIPE 636 100% 67
2a06:41c0::/48 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none70.40.138.0/24No route object for it. Add a route object with origin AS42846 in the RIR database for the space.673 of 673
Route object: none70.40.139.0/24No route object for it. Add a route object with origin AS42846 in the RIR database for the space.673 of 673

Route objects not announced

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