Thordata Review 2026

Thordata was founded in 2018 in Hong Kong and has grown into a full-stack data infrastructure provider that directly challenges the enterprise proxy duopoly of Bright Data and Oxylabs. The residential proxy pool exceeds 60 million IPs across 195+ countries, with city-level and ISP-level targeting available on all plans. What sets Thordata apart from pure proxy providers is the breadth of its product suite: alongside raw proxy access, the platform includes a SERP API for structured search result extraction, a Web Unlocker that handles JavaScript rendering and anti-bot bypass automatically, and a cloud-based Scraping Browser compatible with Puppeteer and Playwright. Pricing is structured to undercut the enterprise tier significantly — volume pricing drops to $0.77 per gigabyte at the 500 GB tier, compared to $8+ per gigabyte at Bright Data's comparable level. For teams scaling data collection operations without enterprise budgets, Thordata's combination of tooling depth and aggressive pricing represents one of the more compelling 2026 alternatives to the legacy market leaders.

Thordata is well-suited for the following primary use cases: Web Scraping, SEO Monitoring, Ad Verification, Price Monitoring, Brand Protection.

Thordata's Web Unlocker makes it particularly effective for e-commerce price monitoring on heavily protected retail sites — the layer handles Cloudflare, PerimeterX, and similar bot detection automatically without engineering overhead. The SERP API supports SEO agencies running large-scale keyword tracking across multiple geographies, delivering structured search results without managing proxy rotation or response parsing. Brand protection teams use the residential pool's ISP-level targeting to verify localized ad delivery and monitor counterfeit product listings on regional marketplaces. Financial data teams benefit from the 99.9% uptime guarantee and configurable sticky sessions for multi-step authenticated workflows. The Scraping Browser enables complex JavaScript-heavy scraping workflows — login sequences, cart operations, infinite scroll — using familiar Puppeteer or Playwright syntax on managed infrastructure, removing the need to maintain rotating browser fleets.

In our testing period, Thordata achieved a 98.0% request success rate — placing it in the top tier among providers we have evaluated. For enterprise workloads where every failed request represents lost data, this level of reliability reduces the need for retry logic and fallback proxies.

The average response time of 520 ms is well below the 2,000 ms threshold we consider fast for proxy traffic, making Thordata suitable for latency-sensitive applications including real-time price monitoring and SERP rank tracking.

Thordata maintained 99.9% uptime during our monitoring window. This near-flawless availability is suitable for 24/7 production systems and continuous data pipelines that cannot tolerate interruptions.

Thordata residential proxies start at approximately $2.00 per gigabyte for small volumes, dropping to $1.80/GB at 10 GB, $1.50/GB at 50 GB, $1.00/GB at 150 GB, and $0.77/GB at 500 GB and above. Mobile proxies and static ISP proxies are priced separately. New residential proxy customers receive a 100% credit-back offer on first purchases up to $900 — effectively making the first volume tier a free trial. Datacenter proxies are billed separately per IP per month. Enterprise accounts can negotiate custom pricing. The Web Unlocker and SERP API are billed per successful request rather than bandwidth, keeping costs predictable for structured data workflows.

Pricing structure varies by plan tier — contact the sales team or consult the pricing page to identify the plan that matches your expected monthly usage volume.

Thordata is a strong choice for growing data teams that need enterprise-grade tooling — SERP API, Web Unlocker, Scraping Browser — without paying enterprise prices. E-commerce and market intelligence teams that have outgrown budget providers but cannot justify Bright Data's minimum spend will find Thordata the most capable mid-market alternative. Teams already using Puppeteer or Playwright for scraping can migrate scraping browser workloads directly without rewriting their automation code.

Setting up Thordata for your project is straightforward. After creating an account and selecting a plan, you receive proxy credentials that work with any HTTP-compatible scraping framework. Below is a typical integration workflow.

Step 1 — Sign up and verify your account. Visit Thordata's website, create an account, and complete any required verification to activate proxy access. Most providers activate accounts within minutes. Start with the free trial to validate the service for your specific target sites before committing to a paid plan.

Step 2 — Generate credentials. In the dashboard, create a set of proxy credentials (username and password) and note the proxy endpoint hostname and port. Some providers also support IP-based authentication, which removes credential management from your code entirely.

Step 3 — Configure your tool or script. Pass the proxy endpoint and credentials to your scraping framework. In Python's requests library this is a one-line configuration. In Playwright or Puppeteer, set the proxy in the browser launch options. Most frameworks also support reading proxy settings from environment variables — the recommended approach for keeping credentials out of source code.

Step 4 — Test and scale. Run a small test batch against your target geography before scaling up. Check response codes, verify content returns correctly, and confirm success rates meet your threshold. Based on our testing, expect results in the range of 98.0% success rate under normal conditions. Once validated, scale up your concurrency and monitor usage in the provider dashboard.

Thordata operates a residential proxy pool of 60 million+ IPs across 195 countries, sourced through a consented SDK-based peer network. The mobile proxy network covers 80+ countries via real SIM card infrastructure including 3G, 4G, and 5G carriers. Static ISP proxies are available in the US and major EU markets. Datacenter nodes span 40+ global locations. Supports HTTP, HTTPS, and SOCKS5 with both rotating and sticky session modes up to 30 minutes.

Thordata's proxy infrastructure operates on a distributed network architecture where client requests are routed through an intermediary server before reaching the target website. The target site sees the proxy IP address instead of your real IP, allowing you to access geo-restricted content, avoid rate limiting, and scrape data at scale without triggering IP-based blocks.

The rotation mechanism assigns a fresh IP address based on your session configuration. In rotating mode, each HTTP request may use a different IP from the pool, distributing your request signature across thousands of addresses. In sticky session mode, the same IP is maintained for a set duration — typically 1 to 30 minutes — allowing multi-step workflows to maintain session continuity without re-authentication on each request.

Thordata offers residential proxies (IPs assigned by Internet Service Providers to real homes and businesses — the highest trust tier) alongside datacenter proxies (IPs from dedicated server infrastructure — faster, lower cost, but more easily detected by sophisticated bot-protection systems) and mobile proxies (IPs from genuine 4G/LTE carrier connections — the hardest to detect for platforms that track device fingerprints). Choosing the right type for your use case significantly impacts success rate and cost efficiency.

Authentication is handled either through username/password credentials passed in the proxy URL or via IP whitelisting, where your server's IP is registered and traffic is authorized automatically without credentials in the request. The latter approach is preferred for production environments where embedding credentials in code creates security exposure.

Thordata supports IP whitelist and credential-based authentication on all proxy types. The platform enforces a strict no-traffic-log policy, retaining only billing and connection metadata. TLS 1.3 is used on all API and proxy connections. GDPR-aligned data processing is available with a Data Processing Agreement for enterprise customers. The Web Unlocker and SERP API operate on isolated request infrastructure with no cross-customer data exposure.

When evaluating a proxy provider for sensitive data collection or business-critical automation, three privacy properties matter most. First, the no-logging policy — does the provider store request URLs and content, or only connection metadata for billing? Second, traffic isolation — are your requests routed through infrastructure shared with other customers, or through dedicated paths that prevent cross-contamination? Third, authentication security — are credentials transmitted over encrypted channels, and is IP whitelisting available as a zero-credential alternative?

Thordata supports standard proxy authentication via HTTPS-tunneled connections, ensuring request metadata is encrypted in transit between your client and the proxy endpoint. SOCKS5 protocol support provides an additional layer of flexibility, allowing non-HTTP traffic to be proxied without exposing application-layer metadata to the proxy infrastructure.

For compliance-sensitive use cases — financial data collection, healthcare research, or operations under GDPR jurisdiction — always request and review the provider's data processing agreement before deploying. A provider's public no-logs claim should be backed by a written DPA that specifies what data is processed, the retention period, and the legal basis for processing under your jurisdiction's privacy law.

Integrating Thordata into your workflow takes under 10 minutes for most frameworks. Below are the most common integration patterns used by developers in production environments. Always store credentials as environment variables — never hardcode them in source files that may be committed to version control.

Python (requests library): The requests library accepts a proxy dictionary where you specify the HTTP and HTTPS proxy URL including credentials. Set the proxy endpoint hostname and port from your Thordata dashboard, then pass your username and password in the URL. For rotating sessions, this is the simplest integration pattern. For sticky sessions, append the session parameter to the username string as documented in the provider API reference.

Python (Playwright / Puppeteer): Browser automation frameworks accept proxy configuration in the browser launch options. Pass the proxy server URL and, if not using IP whitelisting, provide the username and password in the proxy credentials object. Browser-based proxying is important when the target site fingerprints browser behavior in addition to IP addresses — a headless browser through a residential proxy provides the most realistic session simulation.

Scrapy (Python): In Scrapy, set the HTTPPROXY middleware and configure PROXY_URL in your settings.py or per-spider settings. The scrapy-rotating-proxies middleware can automate rotation across a pool of proxy endpoints for distributed scraping tasks.

Environment variable approach: Most proxy providers support an HTTP_PROXY and HTTPS_PROXY environment variable that many HTTP libraries honor automatically. Setting these at the OS or container level applies proxy routing to all outbound requests without code changes. This is the recommended pattern for containerized production deployments.

For Thordata specifically, check the dashboard API documentation for the correct endpoint URL format, session duration parameter syntax, and any rate limits that apply to your subscription tier. Most providers offer a proxy tester tool in the dashboard to verify connectivity before deploying to production.

The proxy provider market has consolidated around a small number of enterprise platforms — Bright Data, Oxylabs, and Smartproxy command the largest IP pools and the most comprehensive feature sets. Mid-tier providers like Thordata compete by offering more targeted pricing, specific geographic advantages, or simplified APIs that remove the complexity of enterprise platforms.

When comparing Thordata to the market leaders, the key trade-offs are typically pool size and feature breadth versus cost and simplicity. Enterprise providers offer real-time performance analytics, dedicated account management, and SLA-backed uptime guarantees that smaller providers cannot match. However, for projects that do not require 100 million+ IPs or enterprise support structures, a focused provider like Thordata often delivers better price-to-performance ratios for the specific use case it targets.

Thordata's 98.0% success rate and 520ms average response time position it among the top-performing providers in the market, competitive with the best enterprise platforms. Whether this performance tier meets your requirements depends on your target sites' bot protection sophistication and your acceptable failure rate budget.

Before selecting a provider, benchmark two to three candidates against your actual target URLs using trial access or small paid allocations. Benchmark metrics from third-party reviews — including those on this site — use standardized test targets that may not reflect performance on your specific websites. Real-world benchmarking against your targets is the only reliable evaluation method.