When the target market is Bulgaria, choose rotating residential (per GB) or static residential (per IP/month) by task. bg-BG/EUR/пощенски код checks plus Bulgarian ecommerce and localization pointers link to on-site scenes; inventory follows the console; prices follow the console. CEE/Southeast Europe primary contrast vs Romania and Hungary (BG ≠ RO / BG ≠ HU / BG ≠ SK / BG ≠ CZ / BG ≠ PL clones; EUR ≠ RON ≠ HUF ≠ CZK ≠ PLN; bg-BG ≠ ro-RO ≠ hu-HU ≠ sk-SK ≠ cs-CZ ≠ pl-PL); secondary SK/CZ/PL; do not invent GR/RS/HR/UA pages. Bulgaria joined the eurozone on 2026-01-01; BGN is transition-only.
What this Bulgaria page solves
Once the target market is Bulgaria, the next step is usually not another product brochure—it is two decisions:
- Pick product class by task: public-side sampling / monitoring / localization, or authorized store long-lived identity
- Confirm in the console that Bulgarian exits are orderable (cities and stock always follow the backend)
This is the Bulgaria country landing under Locations: map “Bulgaria × rotating/static” to on-site products and scenes—not a city inventory table. Still need the class frame? Rotating vs static residential. First-time buyer overview: How to choose a residential proxy. Sister markets: United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain · Brazil · Mexico · India · Indonesia · Taiwan · UAE · Saudi Arabia · Thailand · Philippines · Vietnam · Malaysia · Turkey · Egypt · Poland · Hong Kong · New Zealand · Ireland · Austria · Belgium · Switzerland · Sweden · Denmark · Norway · Finland · Portugal · Czech Republic · Slovakia · Hungary · Romania. Hub: Locations. Localization / public-path self-check deep-read: Localization testing. Store map: Ecommerce.
When you also run CEE / Southeast Europe exits in parallel, open the Romania and Hungary sisters (primary contrast RO + HU), and optionally Slovakia, Czech Republic and Poland. Greece / Serbia / Croatia / Ukraine (GR/RS/HR/UA) are neighbor notes only—do not invent GR/RS/HR/UA location pages that are not live. Optional EU ecommerce-hub contrast via Germany and Austria. Mainland China is out of scope for use on this site—we do not promise CN nodes. This Bulgaria page is not a Romania, Hungary, Slovakia, Czechia, or Poland clone—do not paste those bodies here, even when BG is discussed alongside RO or HU (BG ≠ RO / BG ≠ HU / BG ≠ SK / BG ≠ CZ / BG ≠ PL). This page covers Bulgarian exits only—do not treat Romanian, Hungarian, Slovak, Czech, or Polish storefront/localization as this Bulgaria proxy page. Lev/forint-neighbor proximity is a qualitative note only: EUR ≠ RON ≠ HUF, and Bulgaria ≠ Romania clone (same Southeast Europe cluster ≠ same market; even when eMAG spans BG/RO/HU or neighbor lev/forint storefronts appear, Bulgarian storefront currency follows public pages—typically EUR, Romania uses RON, Hungary uses HUF).
Lawful, authorized commercial and technical use only. Bulgaria / CEE scenes mean authorized business and self-checks on publicly reachable paths—not unauthorized access or bypassing platform rules. Mentions of eMAG.bg, Ozone, OLX.bg, Speedy, Econt, or Bulgarian Posts (Български пощи) are limited to authorized store operations and public-path localization / assortment / tracking self-checks. Mentions of tax display are localization notes only (e.g. how ДДС / VAT-BG fees may appear; Bulgaria is in the EU VAT area and joined the eurozone on 2026-01-01)—not tax advice; do not invent product VAT claims. Storefront currency follows what public pages show—typically EUR (historical BGN is transition-only; ≠ RON, ≠ HUF, ≠ CZK, ≠ PLN). Not supported for use in mainland China.
How to split Bulgaria market: rotating by GB vs static by IP
Rotating residential (per GB)
Fit when you need rotatable, Bulgaria-selectable, usage-flexible exits: public data sampling, price monitoring, ad creative / landing self-checks, bg-BG Bulgarian copy / EUR pricing / пощенски код delivery options short-flow previews (optional en-BG English ecommerce UI note—bg-BG ≠ ro-RO ≠ hu-HU ≠ sk-SK ≠ cs-CZ ≠ pl-PL; if a public page still shows historical BGN dual-price context, treat it as a localization note only), public-path UI spot checks, and Bulgarian ecommerce-context public-side assortment and competitor-page checks within a CEE frame, etc. Entry: Rotating.
Billing per GB: about $0.40/GB; 100 TB full bundle about $0.20/GB (full bundle only; not split; 1 TB = 1,000 GB). Math: Billing GB vs IP. Console wins on price.
One short flow (finish checkout or a settings page once—e.g. verify a EUR price and a city/region пощенски код delivery option) can use a sticky session—same exit briefly; sticky ≠ monthly static. Params: console. Detail: Sticky vs static. Multi-page / multi-sample → rotate; do not leave sticky always on.
Static residential (per IP / month)
Fit for authorized Bulgarian store backends or long-lived environments that need a relatively fixed exit during the subscription (CEE / Southeast Europe teams often discuss BG beside RO/HU/SK/CZ/PL static configs—but this page covers Bulgarian exits only—do not mix RO / HU / SK / CZ / PL exits). Entry: Static. Shared about $1.50, dedicated about $5 /IP/month; boundary: Shared vs dedicated. Store map: Ecommerce. Console wins on price.
Localization self-checks and public-side Bulgarian / CEE market research usually do not need monthly static; if the same project has both store backends and public experience / assortment checks, split configs (static + rotating each on their own). When Bulgaria and Romania or Hungary or Slovakia or Czechia or Poland both matter, split exits by market—do not treat Bulgarian exits as Romanian/Hungarian/Slovak/Czech/Polish exits, and do not substitute ro-RO, hu-HU, sk-SK, cs-CZ, or pl-PL for bg-BG (even when eMAG.ro / eMAG.hu / Alza.sk / Allegro logistics appear; Bulgaria storefronts are typically EUR, Romania RON, Hungary HUF, Slovakia EUR, Czechia CZK, Poland PLN—even when SK also uses EUR, EUR alone ≠ BG clone, and ≠ RO clone).
One table: how to match Bulgaria-side tasks
Choose by task
| Task type | Prefer | Why | ZTProxy mapping |
|---|---|---|---|
| Public multi-URL / multi-page sampling, price monitoring, Bulgarian public research | Rotating + Bulgaria geo | Need traffic and rotatable exits, not monthly identity | Rotating; Price monitoring |
| bg-BG / EUR / пощенски код self-check | Rotating; short sticky OK | Public-path regional experience, not long store identity | Localization testing; Sticky vs static |
| Ad creative / landing self-check | Rotating; short sticky or rotate | Object under review is creative and landing | Ad verification |
| Authorized Bulgarian store backend; long-lived identity for the term | Static shared or dedicated | Relatively fixed exit for the subscription | Static; Ecommerce; Shared vs dedicated |
| Unsure of class / first purchase | Read class guide + buyer checklist | Align task and billing unit | Rotating vs static; How to choose |
Prices and capabilities follow the console; this table is not a platform-review or conversion promise and does not claim inventory or coverage.
Rotating vs static (Bulgaria context)
| Dimension | Rotating residential | Static residential |
|---|---|---|
| What you buy | Rotatable / Bulgaria-selectable residential exits + traffic | Relatively fixed Bulgarian exit for the term |
| Billing | Per GB (~$0.40/GB; large packs on pricing) | Per IP / month (shared ~$1.50; dedicated ~$5) |
| Typical use | Monitoring, ads, bg-BG/EUR/пощенски код localization spot checks, public assortment | Authorized stores, persistent business environments |
| Entry | Rotating | Static |
| Easy mistakes | Forcing rotating for long-lived logins; treating sticky as monthly fixed | Forcing static monthly rent for multi-page public sampling / multi-city delivery checks |
BG vs RO vs HU (localization axes, qualitative)
| Axis | Bulgaria (this page) | Romania (contrast) | Hungary (contrast) |
|---|---|---|---|
| UI language tag | bg-BG | ro-RO | hu-HU |
| Currency | EUR (eurozone since 2026-01-01; BGN transition-only) | RON | HUF |
| Postal form | пощенски код (typically 4 digits) | cod poștal (RO, typically 6 digits) | irányítószám (HU) |
| Authorized public-path examples | eMAG.bg / Ozone / OLX.bg / Speedy / Econt / Bulgarian Posts | See Romania | See Hungary |
| Takeaway | This page covers BG only | Not BG primary CTA; RON ≠ EUR | Not BG primary CTA; HUF ≠ EUR |
How to read Bulgaria / CEE scenes (no invented inventory)
Common business talk mentions Bulgarian ecommerce and localization, a CEE / Southeast Europe / Balkans-adjacent cluster (Bulgaria often discussed beside Romania, Hungary, Slovakia, Czechia and Poland; even when eMAG.ro / eMAG.hu / Alza.sk / Allegro logistics or neighbor lev/forint UI overlap, storefronts, localization, currency (EUR ≠ RON ≠ HUF ≠ CZK ≠ PLN), and sovereign markets differ), Bulgarian public-side research, and bg-BG UI display differences. This page’s target market remains Bulgarian exits:
- Bulgarian ecommerce / CEE parallel pointer: authorized Bulgarian store long-lived identity → static; public assortment, competitor pages, price sampling → rotating. When contrasting in parallel, open Romania and Hungary first (primary RO + HU), then optionally Slovakia, Czech Republic and Poland. GR/RS/HR/UA are qualitative only—do not invent those location pages. Map: Ecommerce. eMAG.bg / Ozone / OLX.bg / Speedy / Econt / Bulgarian Posts mentions are authorized-store and public-path localization / assortment / tracking self-checks only—no account farming or bypass language.
- bg-BG / EUR / пощенски код localization: prefer rotating + Bulgaria geo; one complete short flow (EUR pricing, пощенски код delivery options, bg-BG UI; optional en-BG; historical BGN dual-price context as a note only) can use sticky; multi-page sampling should rotate. Deep-read: Localization testing. Remember bg-BG ≠ ro-RO ≠ hu-HU ≠ sk-SK ≠ cs-CZ ≠ pl-PL—Bulgarian market UI is primarily bg-BG (do not treat Bulgaria as Romania or Hungary/Slovakia/Czechia/Poland); Romanian storefront differences → Romania; Hungarian → Hungary; Slovak → Slovakia; Czech → Czech Republic; Polish → Poland. Do not invent GR/RS/HR/UA location pages.
- пощенски код / city·region delivery self-checks: sample only publicly reachable checkout/shipping/tracking paths under authorized business use; do not promise carrier outcomes or coverage, and do not invent city or postal lists. Even when eMAG.ro / eMAG.hu / Poșta Română / Magyar Posta remain visible in neighbors, Bulgarian paths still follow Speedy / Econt / Bulgarian Posts and Bulgarian storefronts—do not mix Romanian or Hungarian/Slovak/Czech/Polish storefront/localization into this page; do not treat eMAG.ro / eMAG.hu as Bulgaria primary CTAs (eMAG.bg is the Bulgarian public-path example).
- Vs Romania, Hungary, Slovakia, Czechia, and Poland (BG ≠ RO / BG ≠ HU / BG ≠ SK / BG ≠ CZ / BG ≠ PL): markets often sit side by side in CEE / Visegrad+RO+BG / Southeast Europe / EU ecommerce talk, but language/region tags (bg-BG ≠ ro-RO ≠ hu-HU ≠ sk-SK ≠ cs-CZ ≠ pl-PL), storefront/localization paths, currency (EUR ≠ RON ≠ HUF ≠ CZK ≠ PLN; even when SK uses EUR, EUR alone ≠ BG clone), and sovereign markets differ; this page covers Bulgaria only—do not mix neighbor storefront/localization into this page. Need Romanian exits → Romania; Hungarian → Hungary; Slovak → Slovakia; Czech → Czech Republic; Polish → Poland—do not use the Bulgaria page as a neighbor page. Prefer country-name + link sister contrasts; do not spam foreign currency codes in the Bulgaria body (EUR stands alone; RON/HUF/CZK/PLN only vs neighbors; BGN transition-only).
- Mainland boundary: this site does not support use in mainland China; no CN node promise.
- Bulgarian ecommerce and localization context: qualitative note that public paths may show bg-BG copy, EUR pricing (and possible residual BGN transition context), пощенски код / city·region delivery differences, or checkout fee display differences (including ДДС / VAT-BG display—localization note only, not tax advice; Bulgaria is in the EU VAT area and eurozone since 2026-01-01); this site does not provide translation services and does not promise a given language pack “will appear.”
- Competitor SERP themes (qualitative): match rotating vs static by task; verify Bulgarian exits before language/currency/delivery checks; split mixed configs; do not treat BG as RO or HU/SK/CZ/PL clone. This site does not invent search volume or rankings.
Locations is a browse hub; whether Bulgaria is orderable, and city/resource detail, always follow the console / backend. This article does not invent city counts, coverage, or availability SLAs. Start small, then scale.
If the target market is elsewhere, read: United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain · Brazil · Mexico · India · Indonesia · Taiwan · UAE · Saudi Arabia · Thailand · Philippines · Vietnam · Malaysia · Turkey · Egypt · Poland · Hong Kong · New Zealand · Ireland · Austria · Belgium · Switzerland · Sweden · Denmark · Norway · Finland · Portugal · Czech Republic · Slovakia · Hungary · Romania.
How to read price
- Rotating: about $0.40/GB; 100 TB full bundle about $0.20/GB (not split)
- Static: shared about $1.50 /IP/month; dedicated about $5 /IP/month
- USD list; self-serve may follow reseller settings—console and Pricing win
- Cost frame: Billing GB vs IP
- Payments context: USDT/USDC available; Visa/Mastercard applying / pending
Pre-order checklist
- Is the task public-side experience / sampling / Bulgarian market research, or authorized store long-lived identity?
- Confirm the target market is Bulgaria? Visible in console? Do Bulgaria and Romania or Hungary or Slovakia or Czechia or Poland need split configs (BG ≠ RO / BG ≠ HU / BG ≠ SK / BG ≠ CZ / BG ≠ PL; bg-BG ≠ ro-RO ≠ hu-HU ≠ sk-SK ≠ cs-CZ ≠ pl-PL; EUR ≠ RON ≠ HUF ≠ CZK ≠ PLN; do not mix neighbor storefronts)?
- Short sticky or rotate? (params follow console)
- Bill per GB or IP×month? Open Pricing
- Access: Docs quickstart; protocol list: HTTP / SOCKS5 setup
- Lawful authorized use? Avoid mainland China use limits? First purchase: How to choose
FAQ
Should Bulgaria work buy rotating or static?
Public monitoring, ad self-checks, bg-BG/EUR/пощенски код localization spot checks, public research → prefer Rotating. Authorized store long-lived identity → prefer Static. Frame: Rotating vs static.
Who decides Bulgaria inventory and city coverage?
The backend / console. This page lists no city inventory numbers; the Locations hub is browse-only.
How is Bulgaria rotating residential billed? What payments work?
Per GB, about $0.40/GB (large packs on pricing). USD list; console and Pricing win. Payments context: USDT/USDC available; Visa/Mastercard applying / pending.
Can a sticky session replace a Bulgaria static IP?
No. Sticky only tries to keep the same exit for a short window; static is monthly fixed identity. See Sticky vs static.
How to configure bg-BG, EUR, or пощенски код localization?
Prefer rotating + Bulgaria geo; one complete short flow (EUR / пощенски код / bg-BG UI; optional en-BG; historical BGN dual-price context as a note only) can use sticky; multi-page sampling should rotate. Deep-read: Localization testing. Need Romanian exits → Romania; Hungarian → Hungary; Slovak → Slovakia; Czech → Czech Republic; Polish → Poland (BG ≠ RO / BG ≠ HU / BG ≠ SK / BG ≠ CZ / BG ≠ PL; bg-BG ≠ ro-RO ≠ hu-HU ≠ sk-SK ≠ cs-CZ ≠ pl-PL; EUR ≠ RON ≠ HUF ≠ CZK ≠ PLN; even when eMAG.ro / eMAG.hu logistics or neighbor lev/forint UI overlap, storefronts and localization differ).
How does this differ from US / JP / SG / UK / DE / AU / CA / FR / NL / KR / IT / ES / BR / MX / IN / ID / TW / AE / SA / TH / PH / VN / MY / TR / EG / PL / HK / NZ / IE / AT / BE / CH / SE / DK / NO / FI / PT / CZ / SK / HU / RO pages?
Same selection skeleton, different target market; this page stresses bg-BG / EUR / пощенски код, Bulgarian ecommerce and localization, CEE / Southeast Europe context, and parallels with Romania, Hungary (primary RO + HU) and Slovakia, Czech Republic, Poland—and calls out BG ≠ RO / BG ≠ HU / BG ≠ SK / BG ≠ CZ / BG ≠ PL clones (Bulgaria is not Romania, Hungary, Slovakia, Czechia, or Poland; bg-BG ≠ ro-RO ≠ hu-HU ≠ sk-SK ≠ cs-CZ ≠ pl-PL; EUR ≠ RON ≠ HUF ≠ CZK ≠ PLN). Contrast: United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain · Brazil · Mexico · India · Indonesia · Taiwan · UAE · Saudi Arabia · Thailand · Philippines · Vietnam · Malaysia · Turkey · Egypt · Poland · Hong Kong · New Zealand · Ireland · Austria · Belgium · Switzerland · Sweden · Denmark · Norway · Finland · Portugal · Czech Republic · Slovakia · Hungary · Romania.
What is the use boundary? Can this be used for account farming or multi-account evasion?
Lawful, authorized commercial and technical use only, plus self-checks on publicly reachable paths. No account farming, multi-account evasion, or bypassing platform rules; no platform-review or conversion promises.
Is mainland China supported? Who decides price?
All proxy products on this site are not supported for use in mainland China. List prices are USD; orders and billing always follow the console and Pricing.
Next steps
- Use the task table to pick rotating or static
- Open Rotating or Static and confirm Bulgaria exits in the console
- Check Pricing; access via Docs quickstart
- Scenes: Localization testing · Ecommerce · Price monitoring · Ad verification
- Other markets: Locations · United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain · Brazil · Mexico · India · Indonesia · Taiwan · UAE · Saudi Arabia · Thailand · Philippines · Vietnam · Malaysia · Turkey · Egypt · Poland · Hong Kong · New Zealand · Ireland · Austria · Belgium · Switzerland · Sweden · Denmark · Norway · Finland · Portugal · Czech Republic · Slovakia · Hungary · Romania
- First-purchase overview: How to choose
Need help: [email protected] or the on-site support center (no invented response SLA).