When the target market is Colombia, choose rotating residential (per GB) or static residential (per IP/month) by task. es-CO/COP/código postal checks plus Colombian ecommerce and localization pointers link to on-site scenes; inventory follows the console; prices follow the console. LatAm/Andean primary contrast vs Mexico and Brazil (CO ≠ MX / CO ≠ BR / CO ≠ ES clones; COP ≠ MXN ≠ BRL ≠ EUR; es-CO ≠ es-MX ≠ es-ES); secondary ES; do not invent AR/CL/PE pages. Colombia uses COP as storefront currency; MXN/BRL/EUR are neighbor contrast-only.
What this Colombia page solves
Once the target market is Colombia, 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 Colombian exits are orderable (cities and stock always follow the backend)
This is the Colombia country landing under Locations: map “Colombia × 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 · Bulgaria. Hub: Locations. Localization / public-path self-check deep-read: Localization testing. Store map: Ecommerce.
When you also run LatAm / Andean exits in parallel, open the Mexico and Brazil sisters (primary contrast MX + BR), and optionally Spain (language-family secondary; es-CO ≠ es-ES). Argentina / Chile / Peru (AR/CL/PE) are neighbor notes only—do not invent AR/CL/PE location pages that are not live. Optional Americas contrast via United States. Mainland China is out of scope for use on this site—we do not promise CN nodes. This Colombia page is not a Mexico, Brazil, or Spain clone—do not paste those bodies here, even when CO is discussed alongside MX or BR (CO ≠ MX / CO ≠ BR / CO ≠ ES). This page covers Colombian exits only—do not treat Mexican, Brazilian, or Spanish storefront/localization as this Colombia proxy page. MXN/BRL/EUR-neighbor proximity is a qualitative note only: COP ≠ MXN ≠ BRL ≠ EUR, and Colombia ≠ Mexico clone (same LatAm cluster ≠ same market; even when Mercado Libre / Falabella spans CO/MX/BR or neighbor MXN/BRL storefronts appear, Colombian storefront currency follows public pages—typically COP, Mexico uses MXN, Brazil uses BRL, Spain uses EUR).
Lawful, authorized commercial and technical use only. Colombia / LatAm scenes mean authorized business and self-checks on publicly reachable paths—not unauthorized access or bypassing platform rules. Mentions of Mercado Libre CO, Falabella CO, Éxito, Servientrega, or 4-72 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 IVA-CO fees may appear; Colombia is not in the EU VAT area; uses COP as storefront currency)—not tax advice; do not invent product VAT claims. Storefront currency follows what public pages show—typically COP (≠ MXN, ≠ BRL, ≠ EUR). Not supported for use in mainland China.
How to split Colombia market: rotating by GB vs static by IP
Rotating residential (per GB)
Fit when you need rotatable, Colombia-selectable, usage-flexible exits: public data sampling, price monitoring, ad creative / landing self-checks, es-CO Colombian copy / COP pricing / código postal delivery options short-flow previews (optional en-CO English ecommerce UI note—es-CO ≠ es-MX ≠ es-ES; if a public page still shows neighbor MXN/BRL/EUR contrast context, treat it as a localization note only), public-path UI spot checks, and Colombian ecommerce-context public-side assortment and competitor-page checks within a LatAm 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 COP price and a city/region código postal 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 Colombian store backends or long-lived environments that need a relatively fixed exit during the subscription (LatAm / Andean teams often discuss CO beside MX/BR/ES static configs—but this page covers Colombian exits only—do not mix MX / BR / ES 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 Colombian / LatAm 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 Colombia and Mexico or Brazil or Spain both matter, split exits by market—do not treat Colombian exits as Mexican/Brazilian/Spanish exits, and do not substitute es-MX, pt-BR, or es-ES for es-CO (even when Mercado Libre MX / Mercado Libre BR / Amazon.es logistics appear; Colombia storefronts are typically COP, Mexico MXN, Brazil BRL, Spain EUR—even within the Spanish-language family, es alone ≠ CO clone, and ≠ MX clone).
One table: how to match Colombia-side tasks
Choose by task
| Task type | Prefer | Why | ZTProxy mapping |
|---|---|---|---|
| Public multi-URL / multi-page sampling, price monitoring, Colombian public research | Rotating + Colombia geo | Need traffic and rotatable exits, not monthly identity | Rotating; Price monitoring |
| es-CO / COP / código postal 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 Colombian 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 (Colombia context)
| Dimension | Rotating residential | Static residential |
|---|---|---|
| What you buy | Rotatable / Colombia-selectable residential exits + traffic | Relatively fixed Colombian 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, es-CO/COP/código postal 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 |
CO vs MX vs BR (localization axes, qualitative)
| Axis | Colombia (this page) | Mexico (contrast) | Brazil (contrast) |
|---|---|---|---|
| UI language tag | es-CO | es-MX | pt-BR |
| Currency | COP (storefront since always; neighbor MXN/BRL/EUR contrast-only) | MXN | BRL |
| Postal form | código postal (typically 4 digits) | código postal (MX) | CEP (BR) |
| Authorized public-path examples | Mercado Libre CO / Falabella CO / Éxito / Servientrega / 4-72 | See Mexico | See Brazil |
| Takeaway | This page covers CO only | Not CO primary CTA; MXN ≠ COP | Not CO primary CTA; BRL ≠ COP |
How to read Colombia / LatAm scenes (no invented inventory)
Common business talk mentions Colombian ecommerce and localization, a LatAm / Andean / South America cluster (Colombia often discussed beside Mexico, Brazil, and Spain; even when Mercado Libre MX / Mercado Libre BR / Amazon.es logistics or neighbor MXN/BRL UI overlap, storefronts, localization, currency (COP ≠ MXN ≠ BRL ≠ EUR), and sovereign markets differ), Colombian public-side research, and es-CO UI display differences. This page’s target market remains Colombian exits:
- Colombian ecommerce / LatAm parallel pointer: authorized Colombian store long-lived identity → static; public assortment, competitor pages, price sampling → rotating. When contrasting in parallel, open Mexico and Brazil first (primary MX + BR), then optionally Spain. AR/CL/PE are qualitative only—do not invent those location pages. Map: Ecommerce. Mercado Libre CO / Falabella CO / Éxito / Servientrega / 4-72 mentions are authorized-store and public-path localization / assortment / tracking self-checks only—no account farming or bypass language.
- es-CO / COP / código postal localization: prefer rotating + Colombia geo; one complete short flow (COP pricing, código postal delivery options, es-CO UI; optional en-CO; neighbor MXN/BRL/EUR contrast context as a note only) can use sticky; multi-page sampling should rotate. Deep-read: Localization testing. Remember es-CO ≠ es-MX ≠ es-ES—Colombian market UI is primarily es-CO (do not treat Colombia as Mexico or Brazil or Spain); Mexican storefront differences → Mexico; Brazilian → Brazil; Spanish → Spain. Do not invent AR/CL/PE location pages.
- código postal / 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 Mercado Libre MX / Mercado Libre BR / Correos de México / Correios remain visible in neighbors, Colombian paths still follow Servientrega / 4-72 and Colombian storefronts—do not mix Mexican or Brazilian/Spanish storefront/localization into this page; do not treat Mercado Libre MX / Mercado Libre BR as Colombia primary CTAs (Mercado Libre CO is the Colombian public-path example).
- Vs Mexico, Brazil, and Spain (CO ≠ MX / CO ≠ BR / CO ≠ ES): markets often sit side by side in LatAm / Andean / Spanish-language-family commercial talk, but language/region tags (es-CO ≠ es-MX ≠ es-ES), storefront/localization paths, currency (COP ≠ MXN ≠ BRL ≠ EUR; even within the Spanish-language family, es alone ≠ CO clone), and sovereign markets differ; this page covers Colombia only—do not mix neighbor storefront/localization into this page. Need Mexican exits → Mexico; Brazilian → Brazil; Spanish → Spain—do not use the Colombia page as a neighbor page. Prefer country-name + link sister contrasts; do not spam foreign currency codes in the Colombia body (COP stands alone; MXN/BRL/EUR only vs neighbors; neighbor MXN/BRL/EUR contrast-only).
- Mainland boundary: this site does not support use in mainland China; no CN node promise.
- Colombian ecommerce and localization context: qualitative note that public paths may show es-CO copy, COP pricing (and possible residual MXN/BRL transition context), código postal / city·region delivery differences, or checkout fee display differences (including IVA-CO display—localization note only, not tax advice; Colombia is not in the EU VAT area and COP storefront since always); 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 Colombian exits before language/currency/delivery checks; split mixed configs; do not treat CO as MX or BR/ES clone. This site does not invent search volume or rankings.
Locations is a browse hub; whether Colombia 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 · Bulgaria.
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 / Colombian market research, or authorized store long-lived identity?
- Confirm the target market is Colombia? Visible in console? Do Colombia and Mexico or Brazil or Spain need split configs (CO ≠ MX / CO ≠ BR / CO ≠ ES; es-CO ≠ es-MX ≠ es-ES; COP ≠ MXN ≠ BRL ≠ EUR; 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 Colombia work buy rotating or static?
Public monitoring, ad self-checks, es-CO/COP/código postal localization spot checks, public research → prefer Rotating. Authorized store long-lived identity → prefer Static. Frame: Rotating vs static.
Who decides Colombia inventory and city coverage?
The backend / console. This page lists no city inventory numbers; the Locations hub is browse-only.
How is Colombia 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 Colombia 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 es-CO, COP, or código postal localization?
Prefer rotating + Colombia geo; one complete short flow (COP / código postal / es-CO UI; optional en-CO; neighbor MXN/BRL/EUR contrast context as a note only) can use sticky; multi-page sampling should rotate. Deep-read: Localization testing. Need Mexican exits → Mexico; Brazilian → Brazil; Spanish → Spain (CO ≠ MX / CO ≠ BR / CO ≠ ES; es-CO ≠ es-MX ≠ es-ES; COP ≠ MXN ≠ BRL ≠ EUR; even when Mercado Libre MX / Mercado Libre BR logistics or neighbor MXN/BRL 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 / BG pages?
Same selection skeleton, different target market; this page stresses es-CO / COP / código postal, Colombian ecommerce and localization, LatAm / Andean context, and parallels with Mexico, Brazil (primary MX + BR) and Spain—and calls out CO ≠ MX / CO ≠ BR / CO ≠ ES clones (Colombia is not Mexico, Brazil, or Spain; es-CO ≠ es-MX ≠ es-ES; COP ≠ MXN ≠ BRL ≠ EUR). 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 · Bulgaria.
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 Colombia 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 · Bulgaria
- First-purchase overview: How to choose
Need help: [email protected] or the on-site support center (no invented response SLA).