Network · data from 2026-11-12
AS34619 CIZGI CIZGI TELEKOMUNIKASYON ANONIM SIRKETI
Registry name: CIZGI CIZGI TELEKOMUNIKASYON ANONIM SIRKETI, TR · not in PeeringDB
114IPv4 routes
100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS34619, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS34619, 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.
| 37.148.208.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.148.209.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.148.210.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.148.211.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.148.212.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.148.213.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.148.214.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.148.215.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.159.64.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.159.65.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.159.66.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.159.67.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.159.68.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.159.69.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.159.70.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.159.71.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.0.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.1.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.2.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.3.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.4.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.5.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.6.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.7.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.8.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.9.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.10.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.11.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.12.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.13.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.14.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.15.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.16.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.17.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.18.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.19.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.20.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.21.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.22.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.23.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.24.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.25.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.26.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.27.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.28.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.29.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.30.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.19.31.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.129.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.130.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.131.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.132.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.133.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.134.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.135.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.136.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.137.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.138.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.139.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.140.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.142.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.144.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.147.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.148.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.149.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.150.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.151.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.152.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.153.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.154.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.155.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.156.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.157.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.158.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.159.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.160.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.161.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.162.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.163.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.164.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.165.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.166.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.167.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.168.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.169.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.170.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.171.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.172.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.173.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.174.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.177.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.178.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.179.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.180.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.181.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.182.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.183.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.184.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.185.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.186.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.187.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.188.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.189.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.190.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.73.191.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.22.184.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.22.185.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.22.186.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.22.187.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.253.242.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.73.146.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS34619 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 9 are in fix.csv.
- Route object: not announced9
Route objects not announced
Route objects with origin AS34619 whose prefix no peer sees AS34619 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.148.208.0/21 | RIPE | Valid |
| 85.159.64.0/21 | RIPE | Valid |
| 89.19.0.0/19 | RIPE | Valid |
| 94.73.128.0/18 | RIPE | Valid |
| 94.73.128.0/24 | RIPE | Valid |
| 94.73.143.0/24 | RIPE | Valid |
| 94.73.175.0/24 | RIPE | Valid |
| 185.22.184.0/22 | RIPE | Valid |
| 185.22.184.0/23 | 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.