Kazakhstan proxies
Kazakhstan needs two caveats before you configure a collector. The first: a large share of local commerce lives inside apps, so a web sample describes the market only partly and must not be labelled as complete. The second: cities here have been renamed, names exist in Kazakh and Russian forms, and geo databases disagree with each other.
What we have in Kazakhstan
Prices are the same as in every other country we cover.
What Kazakh addresses get used for
Marketplace price monitoring
Kaspi, Wildberries KZ, Technodom, Sulpak, Mechta: Kazakh storefronts and prices are separate from the Russian ones.
Cars and property
Kolesa.kz and Krisha.kz cover those two markets almost entirely, and both are only visible from inside the country.
Classifieds
OLX.kz: private listings with local prices and local geography.
Local search and ad verification
google.kz, Tengrinews, NUR.KZ, Zakon.kz: campaigns are bought for the local audience.
What looks different from outside Kazakhstan
These serve a Kazakh visitor something other than what a foreign one sees, because of broadcast rights and local catalogues. We sell addresses rather than a way past detection.
Which type to take for a Kazakh job
Home connection addresses, billed per gigabyte, rotating by default. A sticky session holds one address for up to fifty minutes.
Marketplaces, classifieds, search results, ad checks
Addresses in Kazakh datacenters, traffic unmetered.
Volume collection where the target ignores address class
Cities people ask for here
Cities are set with the _city_ suffix, but names here are unstable: write them the way the geo database knows them, and verify what you got.
The setups people take here most often
- 01Residential, country levelThe default: marketplaces and classifieds expect a home address.
- 02Datacenter, AlmatyVolume collection where the target is neutral.
- 03A fifty minute sticky sessionWhen a job has to run start to finish on one address.
- 04Cities stored as identifiersIn the data a city is a code or coordinates rather than a string lifted from text.
Connection strings for Kazakhstan
The country code is KZ, upper case. The city goes after it with _city_, hyphens instead of spaces, in the order country, city, session, lifetime.
Kazakh static addresses take no suffixes: the host is the IP from your dashboard, port 50100, SOCKS5 on 50101.
Kazakh exits, four ways
curl -x login_c_KZ:[email protected]:10000 https://api.ipify.org
# held for fifty minutes, for a job that must not change address
curl -x login_c_KZ_s_42_ttl_50m:[email protected]:10000 https://api.ipify.org
# Almaty explicitly, then verify what you actually got
curl -x login_c_KZ_city_Almaty_s_43_ttl_15m:[email protected]:10000 https://ipinfo.io/json
# a Kazakh static address: no suffixes
curl -x login:password@YOUR-KZ-IP:50100 https://api.ipify.orgThe web describes only part of this market
Better to start here, because it determines what you are entitled to claim from the data you collect.
A large share of local retail runs inside apps: the catalogue is there, so is the order and the payment. Web versions exist, but on some platforms they are thinner, and certain offers never appear in them at all.
What that means in practice. Data collected from the web stays useful: prices are comparable, movement is visible, competitors can be measured against each other. But the sample is partial, and it cannot be labelled as exhaustive.
So in reports on Kazakhstan it pays to state explicitly that the web storefront is what was covered. Six months later nobody then has to explain a gap against a client’s internal numbers as a collection error, because there was no error: the two things measured are not the same thing.
We would rather say this before the sale than after. Addresses here are useful and needed; the market is simply built so that the web reflects part of it.
One city can go by several names
The second feature, and it breaks both targeting and data joins.
Cities here have been renamed, some more than once. On top of that most names have Kazakh and Russian forms, and older variants still turn up in listing text and in archived exports. The capital has changed its name twice in recent years.
For targeting that means a city request can fail simply because the geo database knows it under a different spelling. Verify what you received rather than assuming the name is universal.
For joining data it means a city cannot be stored as a string lifted from page text. Otherwise one place splits into several records and the regional breakdown comes out wrong. Keep a region code or coordinates, and use the name as a human-readable label.
On historical series specifically: if you are comparing today’s data against an export from two years ago, reconcile the name reference first. A break in a city’s series usually means a renaming rather than a market that disappeared.
What actually blocks you on Kazakh targets
The familiar split.
Marketplaces and the large chains filter hosting ranges: expect a 403 from datacenter and plan for residential.
Publishers and government sites serve datacenter addresses normally.
Kolesa and Krisha set no elaborate checks but cut rate noticeably: there the question is pace rather than address class.
Search results are reachable but rate limited per address: more addresses rather than a different type.
Which exits you get here, and how stable they are
The Kazakh pool in practical terms.
The pool is mid-sized: a country of twenty million people, with almost all of it in Almaty, Astana and Shymkent.
The country is enormous and thinly populated, so outside the large cities there are noticeably fewer addresses and line quality varies more. Do not shorten the thirty second timeout.
Response times from Europe are longer than the map suggests: traffic transits other countries, and an extra few tens of milliseconds is normal here.
Sticky sessions hold an address for up to fifty minutes, and default rotation changes it on every request.
Choosing the type for a Kazakh target
The usual order.
- Start with a Kazakh datacenter address: $1.15 per address per month. On publishers and reference sites that is enough.
- A 403 on the first request means hosting ranges are filtered. Move to country-level residential.
- On Kolesa and Krisha lower the pace before you hit the wall: what they cut is frequency.
- If the job has to run on one address, add a sticky session with a lifetime.
- Ask for a city only among the three largest, and always verify that it is what you received.
What Kazakh sites check beyond the address
A Kazakh address opens the first gate; language, time and number parsing decide the rest.
Send kk-KZ or ru-KZ depending on the pass. On most commercial platforms the Russian version is fuller while the Kazakh one is growing, and ad verification needs both passes separately.
There is one time zone for the whole country, UTC+5, and that changed in 2024: the eastern half previously ran an hour ahead. Older timezone references and unverified geo databases still return the former value, which puts a profile an hour out.
The currency is the tenge, written ₸, with a space between thousands and a comma for decimals.
Consent banners are less common than in the EU, but a city picker on first visit is frequent and stops collection at the first step.
What a month of Kazakh work costs
Three scenarios at our prices, so you have something to check a quote against.
- Price monitoring across Kazakh marketplaces, 20,000 listings a day with images blocked, roughly 110 KB per page. That is about 2.2 GB a day, around 66 GB a month: $66 on residential.
- Kolesa and Krisha with their rate limits need a longer schedule rather than more traffic.
- If the targets are neutral, the same collection on ten datacenter addresses costs $13.50 a month.
The legal part, stated plainly
Kazakhstan is not in the European Union, and GDPR does not apply here directly. Its own personal data legislation does, and collecting data that identifies people in Kazakhstan is governed by it regardless of where your company sits.
This is general information rather than legal advice. Our terms require lawful use and we act on abuse reports. Where the answer carries commercial risk, ask a lawyer.
Verifying a Kazakh exit
Under a minute. The second command is mandatory here: it shows which city and region you actually received rather than which one you asked for.
Three checks
# 1. is the exit Kazakh, and where
curl -s -x login_c_KZ:[email protected]:10000 https://ipinfo.io/json
# 2. did the city request land where you meant
curl -s -x login_c_KZ_city_Almaty:[email protected]:10000 https://ipinfo.io/json | grep -iE "city|region"
curl -s -x login_c_KZ_city_Astana:[email protected]:10000 https://ipinfo.io/json | grep -iE "city|region"
# 3. does the fifty minute session hold
for i in 1 2 3; do
curl -s -x login_c_KZ_s_42_ttl_50m:[email protected]:10000 https://api.ipify.org; echo
doneQuestions people ask before buying Kazakh addresses
Why does web data disagree with the market?
Because a large share of commerce runs inside apps and the web storefront does not cover everything. The data is useful, but label the sample as a web storefront.
Why does a city request fail?
Names here are unstable: renamings plus Kazakh and Russian forms. The geo database may know the city under a different spelling, so verify the result.
How should a city be stored in the data?
As a region code or coordinates rather than a string from page text. Otherwise one place splits into several records.
Which timezone should the profile use?
UTC+5 for the whole country. That changed in 2024, and older references still return the former value for the east.
Which language should I collect in?
The Russian version is fuller on most commercial platforms while the Kazakh one is growing. Ad verification needs both passes.
Do Kazakh addresses cost more?
No. Prices are the same everywhere: residential from $1.00 per GB, datacenter from $1.15 per address per month.