Automated Proxy Rotation for Reliable Web Scraping

Proxy Rotation for Web Scraping

During industrial web scraping, a single IP address quickly gets blocked: sites detect high request frequency and return 403 or 429. Data loss reaches 40%. Manual proxy switching is inefficient; an automatic solution is needed. We build a system that distributes requests across a pool of addresses, quarantines blocked ones, and weighted-selects the most reliable proxies. Our experience with over 15 projects shows: proper rotation increases data collection to 99.5%.

How Weighted Proxy Selection Works

Each proxy in the pool stores statistics of successful and failed requests. The rotator calculates success_rate as the ratio of successful to total requests. When selecting an address, weighted randomness is used: a proxy with a coefficient of 0.92 is chosen 7 times more often than one with 0.5. If a proxy returns an error (403, 429, timeout), it is placed in quarantine for 15 minutes (configurable). This prevents retrying through a known-blocked IP.

Request → Proxy Selector
              ↓
         [Proxy Pool]
         192.168.1.1:8080  ← status: OK, 245 requests, score 0.92
         10.0.0.5:3128     ← status: OK, 198 requests, score 0.88
         172.16.0.2:8080   ← status: BLOCKED, in quarantine
              ↓
         Target Site
              ↓
         Response Checker
         (status 200 → success / 403/429 → fail)

How to Integrate the Rotator with aiohttp

Integration relies on asyncio and aiohttp. The fetch function gets a proxy from the rotator, executes the request, and reports success. On error, the proxy goes into quarantine, and the next request uses a different address. This enables processing up to 1000 requests per minute without blocking. Use our Python scraping code for quick setup.

import asyncio
import aiohttp
from dataclasses import dataclass, field
from datetime import datetime, timedelta
import random

@dataclass
class ProxyEntry:
    url: str
    success: int = 0
    fail: int = 0
    blocked_until: datetime = field(default_factory=lambda: datetime.min)

    @property
    def is_available(self):
        return datetime.now() > self.blocked_until

    @property
    def success_rate(self):
        total = self.success + self.fail
        return self.success / total if total > 0 else 0.5

class ProxyRotator:
    def __init__(self, proxies: list[str], quarantine_minutes=15):
        self.pool = [ProxyEntry(url=p) for p in proxies]
        self.quarantine = timedelta(minutes=quarantine_minutes)
        self._lock = asyncio.Lock()

    async def get(self) -> ProxyEntry:
        async with self._lock:
            available = [p for p in self.pool if p.is_available]
            if not available:
                raise RuntimeError("All proxies are blocked")
            weights = [p.success_rate for p in available]
            return random.choices(available, weights=weights)[0]

    async def report(self, proxy: ProxyEntry, success: bool):
        async with self._lock:
            if success:
                proxy.success += 1
            else:
                proxy.fail += 1
                proxy.blocked_until = datetime.now() + self.quarantine

async def fetch(session, url, rotator):
    proxy = await rotator.get()
    try:
        async with session.get(url, proxy=proxy.url, timeout=10) as resp:
            if resp.status in (403, 429, 503):
                await rotator.report(proxy, success=False)
                return None
            await rotator.report(proxy, success=True)
            return await resp.text()
    except Exception:
        await rotator.report(proxy, success=False)
        return None

Why Weighted Selection is Better Than Random

Random selection overloads the system with errors: bad addresses receive as many requests as good ones. A weighted approach based on success_rate is similar to exponential smoothing—the longer a proxy works stably, the more often it is used. This reduces retries by 30% and speeds up data collection. Additionally, we implement proxy monitoring: every 5 minutes we check pool availability and automatically exclude long-blocked addresses.

Comparison of Proxy Types: Residential vs ISP vs Datacenter

Residential proxies (e.g., Bright Data) provide the best bypass but are more expensive—budget savings come from fewer retries. ISP proxies (Oxylabs) are a sweet spot for scraping online stores. Datacenter proxies only suit quick prototypes where temporary blocks are acceptable.

What If All Proxies Are in Quarantine?

The algorithm checks blocked_until for each address. If all are unavailable, an exception is raised—a signal for the operator. We recommend a reserve pool of 5–10 proxies with increased delay between requests. With a pool of 20 residential proxies and default settings, the parser runs without downtime in 99% of cases. In complex scenarios, we automatically increase quarantine_minutes to 30 to reduce pool load.

Stages of Proxy Rotation Implementation

1. Analysis of target sites: determine targeting, request limits, block types.
2. Selection of proxy provider: choose optimal pool (residential/ISP/mix) for budget and tasks.
3. Development of rotator: implement weighted selection, quarantine, and monitoring.
4. Integration with parser: connect aiohttp, error handling, logging.
5. Load testing: run 10,000 requests, check stability under peak loads.

Proxy Provider Comparison by Target Task

For most tasks, 10–15 residential proxies from Smartproxy with adequate delays suffice. If global coverage is needed, choose Bright Data—their pool includes 72 million IPs.

What's Included in the Result

• Architecture of the rotation system with documentation
• Source code in Python with asyncio and aiohttp integration
• Deployment instructions (Docker, monitoring setup)
• Two weeks of support guarantee after deployment

We have 5+ years of experience developing scraping systems and have implemented 15+ projects with proxy rotation. All solutions undergo load testing. Over 15 clients trust our guaranteed result: data loss below 1% and average savings of $200/month on proxy costs. Get a consultation—we'll send an estimate in 1 day. Order implementation—we'll deploy the system in 2–3 days.

Timeline

Basic system: 2–3 working days. Turnkey with adaptation to your stack: up to 5 days.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.