Latvia proxies
Latvia puts two questions to anyone collecting data. First, the market is bilingual, and the same platform shows different things depending on which language asked. Second, the country is small and the address pool matches, so concurrency cannot be planned the way it is in Germany.
What we have in Latvia
Prices are the same as in every other country we cover.
What Latvian addresses get used for
Retail price monitoring
1a.lv, Rimi, Maxima, Elkor, RD Electronics: Latvian storefronts are separate from the Lithuanian and Estonian ones even where the chain is shared.
Classifieds and second-hand
ss.com covers goods, cars and property here: an old platform that is still the main one.
Search results in two languages
google.lv returns different results for a Latvian and a Russian query, and you need both sets for the full picture.
Ad verification
Delfi, TVNET, LSM: campaigns are often split by the language of the audience rather than by country alone.
What looks different from outside Latvia
These serve a Latvian 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 Latvian job
Home connection addresses, billed per gigabyte, rotating by default.
Retail, search results, classifieds, ad checks
Consumer registration on datacenter hardware. Static and dedicated for the term.
Accounts, long sessions, anything that must not change address
Addresses in Latvian 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 two million Riga outweighs everything else so heavily that city targeting rarely makes sense.
The setups people take here most often
- 01Residential, country levelThe default: city targeting in a pool this size hinders more than it helps.
- 02An ISP address for the termWhen you need the same address for weeks and would rather not count traffic.
- 03Datacenter, RigaVolume collection where the target is neutral.
- 04Two passes by languageLatvian and Russian are collected separately, because they are different results.
Connection strings for Latvia
The country code is LV, upper case. The city goes after it with _city_, hyphens instead of spaces, in the order country, city, session, lifetime.
Latvian static addresses, both ISP and datacenter, take no suffixes: the host is the IP from your dashboard, port 50100, SOCKS5 on 50101.
Latvian exits, four ways
curl -x login_c_LV:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# held for fifteen minutes on session 42
curl -x login_c_LV_s_42_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# Riga explicitly, though country level lands there anyway
curl -x login_c_LV_city_Riga_s_43_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# a Latvian static address, ISP or datacenter: no suffixes
curl -x login:password@YOUR-LV-IP:50100 https://api.ipify.orgOne country, two languages of search
The defining feature of collecting Latvia, and it doubles the work.
A substantial part of the population searches and shops in Russian and the rest in Latvian. The larger platforms keep both versions, and publishers often run two editions with different content. The same campaign may target only the Russian-speaking audience or only the Latvian one, and in a country-level report that arrives as a single line.
For search this means the keyword list has to be doubled. Checking Latvian queries and calling that a market measurement does not hold here: half the demand is typed in different words and lands on different pages.
There is a separate technical trap. Many Latvian sites switch language on a button and a cookie rather than on the Accept-Language header. A scraper diligently sending lv-LV gets whatever version was chosen on first contact, and then collects the wrong one consistently. Verify which version you were served from the page content rather than from the header you sent.
The practical conclusion: two passes, two exports, and language as its own column in the data rather than a setting on the collector.
A small pool, and what it changes
Latvia is genuinely small: two million people, and the address pool matches. Worth knowing before you plan a hundred concurrent workers.
At high concurrency you start drawing the same address into several workers at once. Formally everything runs; in practice the target sees a burst from one address and applies limits sooner than your arithmetic predicted.
Hence a simple rule: here you lower concurrency and spread collection over time rather than adding workers. Twenty workers against a country the size of Latvia collect more than a hundred, because a hundred produce refusals.
City targeting makes it worse. Asking for Daugavpils cuts an already modest pool down to dozens of addresses, and repeats begin immediately. Country level is nearly always the right call.
If the work needs stability rather than spread, ISP answers it differently: one static address for the term, with no competition for the pool and no surprises from repeats.
What actually blocks you on Latvian targets
The familiar split, with a local amendment.
Retail chains filter hosting ranges: expect a 403 from datacenter, then choose between residential and ISP.
ss.com sets no elaborate checks but cuts rate hard: the question there is pace rather than address class. Slow down instead of switching type.
Publishers and government sites serve datacenter addresses normally.
Search results are reachable but rate limited per address: more addresses rather than a different type, and with a pool this size that is exactly the constraint.
Which exits you get here, and how stable they are
The Latvian pool in practical terms.
The pool is small and heavily Riga-weighted. Enough for price monitoring, ad verification and position tracking; not enough for jobs needing hundreds of concurrent addresses.
Line quality is good: home connectivity in Latvia is fast and response times from Europe are predictable.
Outside Riga there are noticeably fewer addresses, and individual city requests do not always resolve. Keep a country-level fallback and log when it fires.
Sticky sessions behave normally. ISP addresses do not rotate at all, which is the reason to buy them in a country this size.
Choosing the type for a Latvian target
The usual order, but the fork arrives earlier than in large countries.
- Start with a Latvian datacenter address: $1.15 per address per month.
- A 403 on the first request means hosting ranges are filtered.
- What decides next is concurrency as much as session length. With many workers against a small pool, ISP removes the competition for addresses at $1.90 each per month.
- One-off wide-coverage passes stay on residential, but with fewer workers than you would run in Germany.
- A 429 after many requests is a per-address rate limit: more addresses, or a slower pace.
What Latvian sites check beyond the address
Language is covered above; here is the rest.
The time zone is EET, UTC+2 in winter and UTC+3 in summer. That is an hour ahead of most of the EU, and a profile set to Central European time is out here.
The currency is the euro with its own number format: 1 299,90 €, a space between thousands and a comma for decimals. That separator is often non-breaking, so a parser splitting on an ordinary space will not find the price.
Latvian text carries diacritics: ā, č, ē, ģ, ī, ķ, ļ, ņ, š, ū, ž. Matching names without normalising them produces false mismatches.
Consent banners are mandatory and cover the content: a scraper that does not handle them captures an empty page under a successful status code.
What a month of Latvian work costs
Three scenarios at our prices, so you have something to check a quote against.
- Price monitoring across Latvian retail, 12,000 listings a day with images blocked, roughly 100 KB per page. That is about 1.2 GB a day, around 36 GB a month: $36 on residential.
- Two passes by language double the volume: about $72 a month. That is the price of not passing half a market off as the whole one.
- Five ISP addresses for long sessions cost $9.50 a month with traffic unmetered. In a country with a small pool that is also a way of not competing with your own workers.
The legal part, stated plainly
Latvia is in the European Union, so GDPR applies here with everything that follows for collecting personal data. A Latvian address neither puts you under it nor takes you out: what matters is whose data you collect, not where the traffic exits.
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 Latvian exit
Under a minute. The third command matters most here: it shows whether high concurrency is giving you distinct addresses or the same one repeatedly.
Three checks
# 1. is the exit Latvian, and where
curl -s -x login_c_LV:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json
# 2. does the sticky session hold
for i in 1 2 3; do
curl -s -x login_c_LV_s_42_ttl_15m: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_LV:password@proxy.sotaproxy.com:10000 https://api.ipify.org; echo
done | sort -u | wc -lQuestions people ask before buying Latvian addresses
Why collect two languages?
Because a substantial part of the market searches and shops in Russian while the rest uses Latvian. Different queries, different pages and often different ad campaigns.
Why is the site serving the wrong language?
Many Latvian platforms switch on a cookie rather than the Accept-Language header. Verify the version from the page content rather than from what you sent.
How many workers can I run here?
Fewer than in a large country. The pool is small, so at high concurrency the same address lands in several workers and the target applies limits sooner than your arithmetic predicted.
Do I need city targeting?
Usually not. Riga outweighs everything, and asking for a smaller city cuts the pool to dozens of addresses and produces repeats.
When should I take ISP?
When you need stability rather than spread: one static address for the term at $1.90 a month removes both the competition for the pool and the traffic bill.
Do Latvian addresses cost more?
No. Prices are the same everywhere: residential from $1.00 per GB, ISP from $1.90 per address per month, datacenter from $1.15.