Lithuania Proxies
62,679+ residential and mobile proxy IPs in Lithuania. City-level geo-targeting, rotating and sticky sessions, HTTP, HTTPS & SOCKS5. Plans from $0.90/GB.
Pay as you go from 1 GB. Dataset updated June 2026; live availability varies by network type.
European exchange ledger
Pool rank 11 of 46
38 ASNs
- 01Italy1,299,820
- 02Spain1,238,826
- 03United Kingdom1,205,913
- 04Germany1,162,084
- 05France916,416
Lithuania network coverage
The proxy networks reported for Lithuania, with global catalogue size, network origin, and volume-plan entry price.
ISP-origin IPs for authorized regional sampling and workflows that require a consumer-network route.
- Global pool
- 34M+ IPs
- Network origin
- ISP-classified
- From
- $0.90/GB (1 TB plan)
Mobile Proxies
Live4G and 5G carrier-network IPs for authorized app testing and mobile-network checks.
- Global pool
- 800K+ IPs
- Network origin
- Mobile carrier
- From
- $2.50/GB (512 GB plan)
A network shows as Live only when it is currently serving traffic in Lithuania. Global pool sizes are catalog-wide; browse the live community proxy list for Lithuania to sample real endpoints.
Target Lithuania down to the city and ASN
Set countryCode-lt in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-lt, requests an exit geolocated to Lithuania, subject to live availability.City, ZIP & GPS requests
Request a narrower residential location, then verify the observed exit because live supply and geolocation can vary.
ASN targeting request
Request an autonomous system by AS number, subject to network support and current eligible exits.
Rotating or sticky
Request gateway-selected exits or a sticky target up to 120 minutes; connections and availability affect reuse.
- Country, city, ZIP, GPS, and ASN targeting included on every plan
- Gateway-selected exits or sticky session targets, subject to availability
- HTTP, HTTPS, and SOCKS5 on one gateway, no allowlisting
- Every flag set in the proxy username, no code changes
Sample of 38 autonomous systems covered in Lithuania
- AS8764 TELIA-LIETUVA
- AS24645 CSC-TELECOM-
- AS33922 NTT-LT-AS
- AS34857 T-VARTAI-AS Telekomunikaciju vartai ISP, Klaipeda, Lithuania
- AS202044 GETECHBROTHERS-INTERNET
- AS212531 INTERNETO-VIZIJA
- AS215294 LUMINABROADBAND
- AS2847 LITNET
- AS6769 SICN
- AS8849 MELBICOM-EU-AS Melbikomas UAB
- AS13194 BITE Bite IP Network
- AS16125 CHERRYSERVERS1-AS
Select any country, city, or AS number directly in the proxy username. ASN availability varies by network type and real-time device counts.
# Rotating residential proxy in Lithuania
curl -x http://USER-zone-residential-countryCode-lt:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in Lithuania
curl -x http://USER-zone-residential-countryCode-lt-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in Lithuania
curl -x http://USER-zone-datacenter-countryCode-lt:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for Lithuania: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include Lithuania country targeting at no extra cost. See documentation.
Network-wide operating targets for Lithuania routes
These catalogue-wide figures describe the service target, not a country-specific guarantee. Measure the exact route and workload before relying on it.
- Uptime target
- 99.9%+
- Network-wide availability
- Residential latency
- ~1.1s
- Median response time
- Datacenter latency
- ~780ms
- Median response time
- Max sticky target
- 120 min
- Subject to live exit availability
Latency and uptime are network-wide medians and targets. See how Databay benchmarks its network.
What Lithuania proxies are used for
Authorized workflows where a documented Lithuania network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved Lithuania sources with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a Lithuania network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a Lithuania network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted Lithuania search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted Lithuania price and availability observations against feeds, APIs, or another authorized source.
ExploreSocial media
Operate authorized client accounts using platform-approved tools and stable sessions where the platform permits proxy access.
Explore
Other proxy locations
Compare published catalogue counts and then check live network and targeting availability for the exact location you need.
Largest pools worldwide
Need rotating IPs with city and ASN targeting? Get residential proxies in Lithuania (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Lithuania (refreshed every 5 minutes).
How Lithuania compares in the proxy catalogue
Databay's June 9, 2026 paid-network catalogue assigns 62,679 addresses to Lithuania. That places Lithuania number 46 of 195 locations worldwide and number 11 of 46 in Europe. The Lithuania allocation represents 0.18% of the global catalogue and 0.76% of the Europe total. For Lithuania, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The Lithuania count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live Lithuania coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. Lithuania pricing is determined by network and plan rather than by inflating the country count into a performance promise.
What countryCode-lt changes
The gateway flag countryCode-lt requests an exit geolocated to Lithuania, subject to current supply and the selected network. For Lithuania, it changes one input: the apparent network origin seen by the destination. A Lithuania exit does not set a browser language, currency, time zone, delivery address, tax jurisdiction, account country, cookie history, device profile, or legal eligibility. For a useful Lithuania comparison, write down the hypothesis first and hold those other inputs constant. Check the Lithuania exit with a diagnostic endpoint you trust, save the timestamp and effective settings, and compare the observation with a direct or controlled reference. If a Lithuania city, ZIP, coordinate, or ASN matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan Lithuania sessions from the actual pool scale
Lithuania has a mid-sized catalogue allocation. Treat Lithuania country-level coverage as the broadest useful pool and narrow only when the research question genuinely requires it. Prefer steady Lithuania schedules over bursts, cap retries, and measure exit reuse. A smaller Lithuania eligible set after city or ASN filtering can change the practical behavior substantially. Lithuania pool depth also cannot authorize collection: the destination's terms, robots guidance, contracts, authentication boundaries, rate controls, and applicable law remain the controlling constraints. Treat a block, CAPTCHA, quota, or explicit denial as a stop or review signal across the whole Lithuania pool rather than rotating around it. Record Lithuania failures as data; do not hide them with unlimited retries.
Lithuania in its Europe comparison set
The immediately larger undefined catalogue entry than Lithuania is Portugal at 101,316 addresses, and the next smaller is Norway at 54,406. In the Lithuania comparison set, the regional leader is Italy with 1,299,820. These Lithuania capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Lithuania when the research question specifically needs a Lithuania network-origin observation. Choose a different country from Lithuania only when it is a valid control or a separate market in the study. Combining Lithuania observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Lithuania route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible Lithuania validation checklist
Before using a Lithuania result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-lt setting; the observed exit IP, ASN, and geolocation source; the browser, account, language, currency, address, cookie, and device state; and the UTC timestamp plus response evidence. Repeat the Lithuania check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Lithuania price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Lithuania workflow makes the 62,679-address catalogue figure useful as coverage context without pretending it proves a resident's experience.
Frequently asked questions
How many proxy IPs does Databay have in Lithuania?
What types of proxies are available in Lithuania?
Which networks and ASNs are covered in Lithuania?
How do I authenticate with Databay proxies?
Which protocols are supported?
Is there an API?
How do I get started?
Do you offer reseller or volume plans?
Start using Lithuania proxies
Review live Lithuania coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.