bgpreport

Network · data from 2026-11-12

AS6205 HizliNet-as6205

Registry name: HizliNet-Teknoloji - HizliNet Teknoloji A.S., TR · PeeringDB

37IPv4 routes 100.0% RPKI valid · 29.7% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 26 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
21Route objects not announced registered with origin AS6205, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS6205, 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.136.0/24 Valid None 673 100% 67
70.40.137.0/24 Valid None 673 100% 67
104.247.170.0/24 Valid Other origin only 673 100% 67
104.247.171.0/24 Valid Other origin only 673 100% 67
104.247.174.0/24 Valid Other origin only 673 100% 67
104.247.176.0/24 Valid Other origin only 673 100% 67
104.247.178.0/24 Valid Other origin only 673 100% 67
104.247.181.0/24 Valid Other origin only 673 100% 67
104.247.183.0/24 Valid Other origin only 673 100% 67
104.247.184.0/24 Valid Other origin only 673 100% 67
104.247.186.0/24 Valid Other origin only 673 100% 67
104.247.187.0/24 Valid Other origin only 673 100% 67
104.247.188.0/24 Valid Other origin only 673 100% 67
104.247.189.0/24 Valid Other origin only 673 100% 67
104.247.190.0/24 Valid Other origin only 673 100% 67
185.70.85.0/24 Valid Other origin only 673 100% 67
185.70.86.0/24 Valid Other origin only 673 100% 67
185.70.87.0/24 Valid Other origin only 673 100% 67
185.73.130.0/24 Valid Other origin only 673 100% 67
185.137.215.0/24 Valid Other origin only 673 100% 67
91.102.164.0/24 Valid Other origin only 672 100% 67
104.247.172.0/24 Valid Other origin only 670 100% 67
104.247.175.0/24 Valid Other origin only 667 99% 67
104.247.177.0/24 Valid Other origin only 667 99% 67
104.247.182.0/24 Valid Other origin only 667 99% 67
104.247.185.0/24 Valid Other origin only 667 99% 67
104.247.191.0/24 Valid RIR databaseRIPE 673 100% 67
185.70.97.0/24 Valid RIR databaseRIPE 673 100% 67
185.73.84.0/24 Valid RIR databaseRIPE 673 100% 67
185.73.131.0/24 Valid RIR databaseRIPE 673 100% 67
185.122.14.0/24 Valid RIR databaseRIPE 673 100% 67
85.189.14.0/24 Valid RIR databaseRIPE 670 100% 67
185.157.40.0/24 Valid RIR databaseRIPE 667 99% 67
46.45.180.0/24 Valid RIR databaseRIPE 666 99% 67
46.45.181.0/24 Valid RIR databaseRIPE 666 99% 67
46.45.182.0/24 Valid RIR databaseRIPE 666 99% 67
46.45.183.0/24 Valid RIR databaseRIPE 666 99% 67
2a03:35e0:9700::/48 Valid RIR databaseRIPE 636 100% 67
2a03:a5a0:1::/48 Valid RIR databaseRIPE 636 100% 67
2a03:a5a0:2::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS6205: RIPE::AS6205:AS-HIZLINET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS6205 isn't in the set, or no route object for AS6205 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS6205 in itNot covered
RIPE::AS6205:AS-HIZLINET RIPElists itself further down2 member sets in no database: AS-ZENLAYER, AS138915:AS-CUSTOMER 162323,835 Yes 26

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

  • Route object: none26
  • AS-SET: missing member2
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
Route object: none70.40.136.0/24No route object for it. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none70.40.137.0/24No route object for it. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.170.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.171.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.174.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.176.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.178.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.181.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.183.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.184.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.186.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.187.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.188.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.189.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none104.247.190.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none185.70.85.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none185.70.86.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none185.70.87.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none185.73.130.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none185.137.215.0/24Route objects for it name AS57152, AS208002. Add a route object with origin AS6205 in the RIR database for the space.673 of 673
Route object: none91.102.164.0/24Route objects for it name AS199724. Add a route object with origin AS6205 in the RIR database for the space.672 of 673
Route object: none104.247.172.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.670 of 673
Route object: none104.247.175.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.667 of 673
Route object: none104.247.177.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.667 of 673
Route object: none104.247.182.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.667 of 673
Route object: none104.247.185.0/24Route objects for it name AS57152. Add a route object with origin AS6205 in the RIR database for the space.667 of 673
AS-SET: missing memberRIPE::AS6205:AS-HIZLINETAS6205:AS-HIZLINET (RIPE) lists AS-ZENLAYER; no IRR database read has it.
AS-SET: missing memberRIPE::AS6205:AS-HIZLINETAS6205:AS-HIZLINET (RIPE) lists AS138915:AS-CUSTOMER; no IRR database read has it.

Route objects not announced

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

45.131.2.0/24RIPEValid
45.194.83.0/24AFRINICInvalid: origin
84.17.86.0/24RIPEInvalid: origin
84.54.14.0/24RIPEValid
85.189.19.0/24RIPEValid
85.189.25.0/24RIPEValid
85.189.31.0/24RIPEValid
86.104.14.0/24RIPEValid
89.43.78.0/24RIPEValid
176.98.42.0/24RIPEValid
176.98.43.0/24RIPEValid
185.81.152.0/24RIPEValid
185.81.155.0/24RIPEValid
185.118.176.0/24RIPEInvalid: origin
185.118.178.0/24RIPEInvalid: origin
212.87.197.0/24RIPEValid
2a03:a5a0::/32RIPENo ROA
2a03:a5a0:3::/48RIPENo ROA
2a03:a5a0:4::/48RIPEValid
2a03:a5a0:5::/48RIPENo ROA
2a03:a5a0:1000::/48RIPENo 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.