bgpreport

Network · data from 2026-11-12

AS205733 HOSTIFOX INTERNET VE BILISIM HIZMETLERI TICARET SANAYI LIMITED SIRKETI

Registry name: AS-HOSTIFOX HOSTIFOX INTERNET VE BILISIM HIZMETLERI TICARET SANAYI LIMITED SIRKETI, TR · PeeringDB

9IPv4 routes 88.9% RPKI valid · 88.9% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS205733, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS205733, 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.
82.152.11.0/24 Invalid: origin Other origin only 2 0%low visibility 2
31.56.213.0/24 Valid RIR databaseRIPE 673 100% 66
31.57.134.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
149.62.40.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
163.5.168.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
194.116.228.0/24 Valid RIR databaseRIPE 673 100% 66
45.8.172.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
45.94.171.0/24 Valid RIR databaseRIPE 672 100% 66
96.62.114.0/24 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

AS205733'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.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin82.152.11.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS205733. If AS205733 should announce it, add a ROA for AS205733.2 of 673
Route object: none82.152.11.0/24Route objects for it name AS834. Add a route object with origin AS205733 in the RIR database for the space.2 of 673

Route objects not announced

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