Bulgaria proxies
Bulgaria hands you two problems, and both are about data rather than access. The first: the country moved to the euro at the start of 2026, so any series begun earlier crosses a currency boundary and needs care. The second: Bulgarians routinely type Bulgarian words in Latin letters, so the same query exists in two spellings with no single standard.
What we have in Bulgaria
Prices are the same as in every other country we cover.
What Bulgarian addresses get used for
Retail price monitoring
eMAG.bg, Technopolis, Technomarket, Ozone: Bulgarian storefronts are separate from the Romanian ones even where the platform is shared.
Classifieds and second-hand
OLX.bg and Bazar.bg for goods, Mobile.bg for cars, which covers almost the whole vehicle market.
Property
Imot.bg: the main rental and sales platform, serving something else from outside the country.
Local search and SEO
google.bg: queries arrive in both Cyrillic and Latin script, and you need both lists.
What looks different from outside Bulgaria
These serve a Bulgarian 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 Bulgarian 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 Bulgarian datacenters, traffic unmetered.
Volume collection where the target ignores address class
Cities people ask for here
Cities are set with the _city_ suffix. Sofia outweighs everything, Plovdiv and Varna resolve reliably, and beyond them the pool is thin.
The setups people take here most often
- 01Residential, country levelThe default: retail and classifieds expect a home address.
- 02Two alphabets in the listsCyrillic and Latin query variants are collected together rather than in turn.
- 03Datacenter, SofiaVolume collection where the target is neutral.
- 04A fifty minute sticky sessionWhen a job has to run start to finish on one address.
Connection strings for Bulgaria
The country code is BG, upper case. The city goes after it with _city_, hyphens instead of spaces, in the order country, city, session, lifetime.
Bulgarian static addresses take no suffixes: the host is the IP from your dashboard, port 50100, SOCKS5 on 50101.
Bulgarian exits, four ways
curl -x login_c_BG: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_BG_s_42_ttl_50m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# Plovdiv explicitly, when regions are being compared
curl -x login_c_BG_city_Plovdiv_s_43_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# a Bulgarian static address: no suffixes
curl -x login:password@YOUR-BG-IP:50100 https://api.ipify.orgYour price series crosses a currency changeover
The first thing to check if you have been watching this market for longer than a year.
The country moved to the euro at the start of 2026. In practice that means observations taken before and after the change are expressed in different units, and any comparison across that boundary without conversion shows a difference that never happened.
The second half of the problem is subtler: around the changeover platforms displayed both prices side by side. A parser that grabs the first number it meets next to a currency mark captured one or the other depending on the markup, and what landed in the database was a series with mixed units. From the outside it looks continuous.
The rule is simple and applies well beyond this country. Currency is its own field on the record rather than part of the price string. No conversion on the fly: store what you were shown and normalise in the report layer, where it is visible and can be redone.
If the series already exists, check it for a step around the changeover. An abrupt change in the scale of the numbers is your export rather than the market.
Bulgarian words get typed in Latin letters too
The second feature, and it concerns queries and matching.
The official script is Cyrillic, but in messages, listings and search queries Bulgarians regularly write Bulgarian words in Latin letters. There is no single standard for that: the same letter is rendered several ways, so one query exists in several spellings at once.
For search that means a Cyrillic-only keyword list understates demand. Collect both variants from search suggestions rather than deriving the Latin forms with a rule: live spellings do not obey the rule.
For matching it means listing titles arrive mixed. Use the listing identifier as your key, and normalise the title first: fold case, reconcile the letter renderings, and only then compare.
A note on links: page addresses are often transliterated rather than percent-encoded, so the same listing can appear under different URLs. Reconcile on the identifier inside the page rather than on the URL.
What actually blocks you on Bulgarian targets
The familiar Eastern European split.
Retail chains and classifieds platforms filter hosting ranges: expect a 403 from datacenter and plan for residential.
Publishers and government sites serve datacenter addresses normally.
Search results are reachable but rate limited per address: more addresses rather than a different type.
Mobile.bg and Imot.bg set no elaborate checks but cut rate noticeably: there the question is pace rather than address class.
Which exits you get here, and how stable they are
The Bulgarian pool in practical terms.
The pool is mid-sized by European standards: a country of seven million people, but home internet penetration is high and there are enough addresses for regular work.
Line quality is good and even: fibre is widespread and response times from Europe are predictable.
Sofia outweighs the rest, Plovdiv and Varna resolve reliably, and beyond them the pool is thin. City targeting outside the three largest often falls back to country level.
Sticky sessions hold an address for up to fifty minutes, and default rotation changes it on every request.
Choosing the type for a Bulgarian target
The usual order.
- Start with a Bulgarian 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 the classifieds platforms lower the pace before you hit the wall: what they cut is frequency, not address class.
- 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: more addresses, not a different type.
What Bulgarian sites check beyond the address
A Bulgarian address opens the first gate; language, currency and number parsing decide the rest.
Send bg-BG. English versions exist here and are handed over readily, especially on property platforms aimed at foreign buyers.
The number format is continental: 1 299,90, a space between thousands and a comma for decimals. That separator is often non-breaking.
Record the currency as its own field: as described above, that is not a formality here.
The time zone is EET, UTC+2 in winter and UTC+3 in summer, the same as Latvia, Estonia and Finland and an hour ahead of Central Europe.
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 Bulgarian work costs
Three scenarios at our prices, so you have something to check a quote against.
- Price monitoring across Bulgarian retail, 15,000 listings a day with images blocked, roughly 100 KB per page. That is about 1.5 GB a day, around 45 GB a month: $45 on residential.
- The classifieds platforms with their rate limits need a longer schedule rather than more traffic: the effect on the invoice is minimal.
- If the targets are neutral, the same collection on ten datacenter addresses costs $13.50 a month.
The legal part, stated plainly
Bulgaria is in the European Union, so GDPR applies here with everything that follows for collecting personal data. A Bulgarian 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 Bulgarian exit
Under a minute. The second command is useful here because it shows immediately which currency marks are present on the page you collected.
Three checks
# 1. is the exit Bulgarian, and where
curl -s -x login_c_BG:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json
# 2. which currency marks does the page carry
curl -s -H "Accept-Language: bg-BG" -x login_c_BG:password@proxy.sotaproxy.com:10000 https://your-target.bg/product \
| grep -oE "лв\.|€|EUR|BGN" | sort | uniq -c
# 3. does the fifty minute session hold
for i in 1 2 3; do
curl -s -x login_c_BG_s_42_ttl_50m:password@proxy.sotaproxy.com:10000 https://api.ipify.org; echo
doneQuestions people ask before buying Bulgarian addresses
Why do my old and new prices disagree?
The country moved to the euro at the start of 2026. A series crossing that boundary is expressed in different units, and currency belongs in its own field on the record.
Should I convert prices during collection?
No. Store what you were shown and normalise in the report layer, where it is visible and can be redone.
Why is my keyword list underperforming?
It is most likely Cyrillic only. Bulgarians regularly type Bulgarian words in Latin letters, and there is no single standard for how.
Why does one listing appear under several URLs?
Links are often transliterated rather than percent-encoded. Reconcile on the identifier inside the page rather than the URL.
Do I need city targeting?
Only for the three largest. Beyond them the pool is thin and the request falls back to country level.
Do Bulgarian addresses cost more?
No. Prices are the same everywhere: residential from $1.00 per GB, datacenter from $1.15 per address per month.