Estonia proxies
Estonia stands out in two ways at once. The state publishes a great deal of data officially, so part of the work people usually buy addresses for gets done without them. What remains runs into a quirk of the local address space: the country is small, but it hosts disproportionately much infrastructure, and that changes how sites react to a datacenter address.
What we have in Estonia
Prices are the same as in every other country we cover.
What Estonian addresses get used for
Retail price monitoring
Kaup24, Euronics, Hansapost, Selver, Rimi: Estonian storefronts are separate from the Latvian and Lithuanian ones even where the chain is shared.
Classifieds and second-hand
Okidoki and Soov for goods, Auto24 for cars: a small market that turns over quickly.
Property
kv.ee and City24: rentals in Tallinn and Tartu move noticeably and need frequent passes.
Local search and ad verification
google.ee, Delfi, Postimees, ERR: campaigns are often split by the language of the audience rather than by country alone.
What looks different from outside Estonia
These serve an Estonian 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 an Estonian job
Home connection addresses, billed per gigabyte, rotating by default. A sticky session holds one address for up to fifty minutes.
Retail, classifieds, search results, ad checks
Addresses in Estonian datacenters, traffic unmetered.
Volume collection where the target ignores address class
Cities people ask for here
Cities are set with the _city_ suffix, but in a country of just over a million Tallinn outweighs everything, and a city request cuts the pool to dozens of addresses.
The setups people take here most often
- 01Residential, country levelThe default: the pool is small and city targeting usually gets in the way.
- 02A fifty minute sticky sessionWhen a job has to run start to finish on one address.
- 03Datacenter for neutral targetsPublishers, reference sites and open data are served normally.
- 04Two language passesThe Estonian and Russian versions of sites are collected separately.
Connection strings for Estonia
The country code is EE, upper case. The city goes after it with _city_, hyphens instead of spaces, in the order country, city, session, lifetime.
Estonian static addresses take no suffixes: the host is the IP from your dashboard, port 50100, SOCKS5 on 50101.
Estonian exits, four ways
curl -x login_c_EE:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# held for fifty minutes, for a job that must not change address
curl -x login_c_EE_s_42_ttl_50m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# Tartu explicitly, though the pool there is thin
curl -x login_c_EE_city_Tartu_s_43_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# an Estonian static address: no suffixes
curl -x login:password@YOUR-EE-IP:50100 https://api.ipify.orgPart of the work here needs no proxy at all
Better to start here, or you will buy addresses for work that does not need them.
Estonia keeps a lot of government data open and machine readable. Company information, register extracts, statistics and part of the geodata are available through official interfaces, with no site to work around and no address in the country. If your task is phrased as "collect company data" or "export the statistics", start there: it is faster, steadier and does not break on a redesign.
Proxies are for what has no official interface by definition. Shop prices, listings, search positions, ad impressions, what a broadcaster will play: all of that exists only on pages, and those pages show different things depending on where you arrived from.
The line runs roughly here: facts about legal entities the state hands over itself, and market behaviour nobody hands over.
We lose some sales to that honesty, and you avoid paying for addresses you will not use.
A small country hosting a lot of infrastructure
The second feature, and it explains why a datacenter address behaves differently here than in a country of comparable size.
Estonia has spent years attracting technology companies, and the share of hosting in its address space is out of proportion to its population. Sites worldwide see a noticeable stream of automated traffic from Estonian server networks and treat those ranges accordingly.
First practical consequence: where a datacenter address would pass in another small country, here it is refused more often. Plan the move to residential earlier and do not be surprised by a 403 on your first request to a retailer.
Second practical consequence: the residential pool itself is modest, because there are few people. It cannot carry many workers, and that belongs in your schedule rather than in your error log.
A sensible configuration looks like this: datacenter on publishers, open data and reference sites, residential on everything commercial, low concurrency and a pass spread out over time.
What actually blocks you on Estonian targets
The familiar split, with the amendment from the section above.
Retail chains and classifieds platforms expect a home address: expect a 403 from datacenter, and sooner than the regional average.
ERR, publishers and government sites serve datacenter addresses normally.
Search results are reachable but rate limited per address: more addresses, and with a pool this size that is exactly the constraint.
As with the neighbours, an even machine rhythm stands out more than volume: jitter in your intervals helps more than extra addresses.
Which exits you get here, and how stable they are
The Estonian pool in practical terms.
The pool is small: a country of just over a million people, with almost all of it in Tallinn. Tartu adds a noticeable amount, and beyond that it is a handful.
Line quality is excellent: fibre is widespread and response times from Europe are among the best in our coverage.
A city request cuts the pool to dozens of addresses and produces repeats. Country level is nearly always the right call here, and the fallback is worth logging.
Sticky sessions hold an address for up to fifty minutes: when a job has to run on one address from start to finish, that is the tool here.
Choosing the type for an Estonian target
A short order, because there are two types.
- First check whether the task has an official source. If the state publishes the data, you need no addresses at all.
- For publishers, reference sites and open data take a datacenter address: $1.15 per address per month.
- For retail, classifieds and search results plan for country-level residential from the start: datacenter is refused here more often than usual.
- If the job has to run on one address, add a sticky session with a lifetime.
- A 429 after many requests is a per-address rate limit: lower the pace, because growing the address count in a pool this size is not an option.
What Estonian sites check beyond the address
An Estonian address opens the first gate; language, time and number parsing decide the rest.
Send et-EE. The larger platforms keep Russian and English versions, and without an explicit header you will happily collect the wrong catalogue. The Russian version here is a separate audience rather than a translation, particularly in the east of the country.
The time zone is EET, UTC+2 in winter and UTC+3 in summer, the same as Latvia and Finland and an hour ahead of Sweden.
The currency is the euro with a Nordic number format: 1 299,00 €, a space between thousands, a comma for decimals, and that separator is usually non-breaking.
Estonian uses õ, ä, ö and ü as separate letters. Folding them during normalisation damages name matching.
What a month of Estonian work costs
Three scenarios at our prices, so you have something to check a quote against.
- Price monitoring across Estonian retail, 10,000 listings a day with images blocked, roughly 100 KB per page. That is about 1 GB a day, around 30 GB a month: $30 on residential.
- A second language pass adds the same again only for the sections where the versions genuinely differ, not for the whole volume.
- Open government data costs nothing beyond your own bandwidth: it can be taken without addresses in the country.
The legal part, stated plainly
Estonia is in the European Union, so GDPR applies here with everything that follows for collecting personal data. An Estonian address neither puts you under it nor takes you out: what matters is whose data you collect, not where the traffic exits.
A separate word on open registers: data being available does not mean anything may be done with it. Exports come with their own terms of use, and those are worth reading before you build a product on them.
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 an Estonian exit
Under a minute. The third command is the most useful one here: it shows how many distinct addresses the pool actually gives you under rotation.
Three checks
# 1. is the exit Estonian, and where
curl -s -x login_c_EE:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json
# 2. does the fifty minute session hold
for i in 1 2 3; do
curl -s -x login_c_EE_s_42_ttl_50m:password@proxy.sotaproxy.com:10000 https://api.ipify.org; echo
done
# 3. how many distinct addresses do twenty rotating requests give
for i in $(seq 1 20); do
curl -s -x login_c_EE:password@proxy.sotaproxy.com:10000 https://api.ipify.org; echo
done | sort -u | wc -lQuestions people ask before buying Estonian addresses
Is it true some data can be taken without proxies?
Yes. Company information, register extracts and statistics are published machine readable. Proxies are for prices, listings, search results, advertising and broadcasters, where no official interface exists.
Why does datacenter fail more often than in neighbouring countries?
Estonia’s address space carries disproportionately much hosting, and sites judge those ranges more strictly. On commercial targets plan for residential from the start.
How many workers can I run here?
Not many. A country of just over a million people has a pool to match, and at high concurrency you start drawing repeated addresses.
Do I need city targeting?
Usually not. Tallinn outweighs everything, and a city request cuts the pool to dozens of addresses.
Why collect the Russian versions of sites?
Because that is a separate audience rather than a translation, particularly in the east. Advertising and framing there can differ.
Do Estonian addresses cost more?
No. Prices are the same everywhere: residential from $1.00 per GB, datacenter from $1.15 per address per month.