How to Set Up Automatic Removal of Banned Proxies from Your Pool: A Guide for Arbitrage and SMM

When you are working with 20-50 accounts on Facebook Ads, Instagram, or managing ads on Avito, the problem of banned proxies becomes critical. Each non-working proxy is lost time, a disrupted advertising campaign, or a blocked client account. Manually checking hundreds of proxies every day is impossible.

In this guide, we will discuss how to set up automatic proxy verification and removal of non-working ones from the pool — for anti-detect browsers (Dolphin Anty, AdsPower, Multilogin), for marketplace parsers, and for SMM automation. We will show ready solutions without programming and simple scripts for advanced users.

Why it is important to automatically remove banned proxies

Imagine a situation: you are an arbitrage specialist managing 30 Facebook Ads accounts through Dolphin Anty. Each account is assigned its own proxy from the pool. One of the proxies gets banned by Facebook — but you don't know about it. You open the profile, launch the ad, and Facebook immediately sees a suspicious IP. The result — account ban, loss of money invested in the campaign, an unhappy client.

Or another scenario for an SMM specialist: you manage 50 Instagram accounts for clients through AdsPower. Three proxies from your pool have stopped working — the provider has blocked them or the rental period has expired. You only find out when a client writes, "Why aren't my posts going out?" The agency's reputation is at risk.

The problems that automatic removal of banned proxies solves:

• Preventing account bans — you won't launch a profile through a non-working proxy
• Time savings — no need to manually check each proxy from a list of 100-500
• Relevance of the pool — only live proxies that have passed verification are in use
• Quick response to problems — the system will remove a non-working proxy in minutes, not days
• Cost reduction — you don't pay for proxies that no longer work (if you manage to cancel the renewal)

This is especially critical for residential proxies, which are often used by arbitrage specialists and SMM professionals — they can change status several times a day, as they operate through the IPs of real users.

How to determine if a proxy is banned or not working

Before setting up automatic removal, you need to understand the criteria: when to consider a proxy "banned" or non-working? This is not always obvious, as there are different types of problems.

Types of proxy issues

Proxy verification methods

Several verification methods are used to determine the status of a proxy:

Built-in verification features in anti-detect browsers

Most popular anti-detect browsers for arbitrage and SMM already have built-in proxy verification tools. This is the easiest way for those who do not want to deal with scripts.

Dolphin Anty — proxy checking and auto-removal

Dolphin Anty is one of the most popular anti-detect browsers among Facebook and TikTok arbitrage specialists. It has a mass proxy checking feature and automatic removal of non-working ones.

Step-by-step setup in Dolphin Anty:

1. Open the "Proxies" section in the main menu of Dolphin Anty
2. Click the "Check all proxies" button (checkmark icon in the top panel)
3. Dolphin will send test requests through each proxy from your list
4. In the "Status" column, results will appear: green (working), red (not working), yellow (slow)
5. Select all proxies with red status → right-click → "Remove selected"
6. For automation: enable the "Automatically remove non-working proxies" setting in the "Settings → Proxies" section

After enabling automatic mode, Dolphin Anty will check proxies before each profile launch. If a proxy is not responding — the browser will show a warning and suggest replacing it. This protects against accidentally launching an account through a dead IP.

AdsPower — mass checking and filtering

AdsPower offers a more advanced proxy management system with the ability to create pools and automatic rotation.

Setup in AdsPower:

1. Go to the "Proxy Management" section
2. Import your proxy list using the "Import" button (supports TXT, CSV formats)
3. Click "Batch Check" → AdsPower will check all proxies in parallel
4. In the results, you will see: status (Online/Offline), response speed, IP geolocation
5. Set up a filter: display only Offline proxies → select all → Delete
6. Enable "Auto-check before profile launch" — AdsPower will check proxies before each profile launch

An additional feature of AdsPower is the creation of "Proxy Pools". You can create a pool of 50 proxies, set automatic checks every 6 hours, and AdsPower will automatically remove non-working ones, leaving only live proxies. This is convenient for SMM agencies managing a large number of client accounts.

Multilogin and GoLogin

Multilogin and GoLogin also have built-in proxy verification features, but they are less automated than in Dolphin Anty and AdsPower.

In Multilogin: when creating a profile, click "Check proxy" next to the proxy input field — the system will show the status and IP. There is no mass checking, only manual for each profile.

In GoLogin: the "Test proxy" function is available when editing a profile. For automation, you need to use the GoLogin API and external scripts (more on this below).

External services for automatic proxy pool verification

If you are working not only through anti-detect browsers but also using proxies for parsing, auto-posting, or other tasks — it is more convenient to use specialized services for checking proxy pools.

ProxyChecker.co — online list checking

A free online service for mass proxy checking. Supports HTTP, HTTPS, SOCKS4, SOCKS5.

How to use:

1. Go to the website proxychecker.co
2. Paste your proxy list in the format IP:PORT:USER:PASS (each on a new line)
3. Select the type of check: basic (speed) or extended (geolocation + anonymity)
4. Click "Check proxies" — the service will check all proxies in 1-2 minutes
5. Download the result: the list will be divided into "Working" and "Dead"
6. Import only working proxies back into your tool

Limitation: the free version checks up to 100 proxies at a time. For larger pools, a paid subscription or use of other methods is required.

Proxy Checker Tool (desktop application)

For those who work with large pools (500+ proxies) and want to check them locally without sending data to third-party services, there are desktop applications.

Popular applications:

• ProxyChecker by Proxy-Store (Windows, free) — checks up to 1000 proxies simultaneously, shows speed and geolocation
• Elite Proxy Switcher (Windows, paid) — checking + automatic proxy replacement in the system
• Proxy Checker Pro (Windows/Mac, paid) — advanced checking with testing on specific sites

These applications allow you to set up automatic checks on a schedule (for example, every 6 hours) and export only working proxies to a file, which you then import into Dolphin Anty or AdsPower.

Simple scripts for automatic verification and pool cleaning

For advanced users who want full control over the verification process, simple scripts can be used. Don't be intimidated — even if you are not a programmer, these scripts are easy to run and configure for your tasks.

Python script for checking a list of proxies

This script checks a list of proxies from a file, sending requests through each, and saves only the working ones to a new file.

import requests
import time

# Read the list of proxies from a file
with open('proxies.txt', 'r') as f:
    proxy_list = f.read().splitlines()

working_proxies = []
dead_proxies = []

# Check each proxy
for proxy_line in proxy_list:
    # Format: IP:PORT:USER:PASS
    parts = proxy_line.split(':')
    proxy_url = f"http://{parts[2]}:{parts[3]}@{parts[0]}:{parts[1]}"
    
    proxies = {
        'http': proxy_url,
        'https': proxy_url
    }
    
    try:
        # Send a test request
        response = requests.get('http://ip-api.com/json', 
                              proxies=proxies, 
                              timeout=10)
        
        if response.status_code == 200:
            print(f"✓ Working: {parts[0]}:{parts[1]}")
            working_proxies.append(proxy_line)
        else:
            print(f"✗ Not working: {parts[0]}:{parts[1]}")
            dead_proxies.append(proxy_line)
            
    except Exception as e:
        print(f"✗ Error: {parts[0]}:{parts[1]} - {str(e)}")
        dead_proxies.append(proxy_line)
    
    time.sleep(0.5)  # Delay between checks

# Save results
with open('working_proxies.txt', 'w') as f:
    f.write('\n'.join(working_proxies))

with open('dead_proxies.txt', 'w') as f:
    f.write('\n'.join(dead_proxies))

print(f"\nDone! Working: {len(working_proxies)}, Dead: {len(dead_proxies)}")

How to run:

1. Install Python (python.org) and the requests library: pip install requests
2. Create a file proxies.txt with the list of proxies (format: IP:PORT:USER:PASS, each on a new line)
3. Save the script as check_proxies.py
4. Run: python check_proxies.py
5. Get two files: working_proxies.txt (working) and dead_proxies.txt (for removal)

Script with verification through the target platform

A more advanced version — checking proxies not on a test site, but on a real platform (Instagram, Facebook, Wildberries). This will show if the IP is banned specifically for your task.

import requests
import time

# Target site for checking (for example, Instagram)
TARGET_URL = 'https://www.instagram.com/'

with open('proxies.txt', 'r') as f:
    proxy_list = f.read().splitlines()

working_proxies = []

for proxy_line in proxy_list:
    parts = proxy_line.split(':')
    proxy_url = f"http://{parts[2]}:{parts[3]}@{parts[0]}:{parts[1]}"
    
    proxies = {
        'http': proxy_url,
        'https': proxy_url
    }
    
    try:
        start_time = time.time()
        response = requests.get(TARGET_URL, 
                              proxies=proxies, 
                              timeout=15,
                              headers={'User-Agent': 'Mozilla/5.0'})
        response_time = time.time() - start_time
        
        # Check: is the site accessible and is there no block
        if response.status_code == 200 and 'login' in response.text.lower():
            if response_time < 5:  # Speed less than 5 seconds
                print(f"✓ OK: {parts[0]} | Speed: {response_time:.2f}s")
                working_proxies.append(proxy_line)
            else:
                print(f"⚠ Slow: {parts[0]} | {response_time:.2f}s")
        else:
            print(f"✗ Blocked: {parts[0]}")
            
    except Exception as e:
        print(f"✗ Not working: {parts[0]}")
    
    time.sleep(1)

with open('instagram_working_proxies.txt', 'w') as f:
    f.write('\n'.join(working_proxies))

print(f"\nProxies for Instagram: {len(working_proxies)}")

This script checks access to Instagram through each proxy and saves only those that: (1) gain access to the site, (2) do not see a block, (3) respond faster than 5 seconds. Similarly, it can be set up for Facebook, TikTok, Wildberries — just change the TARGET_URL.

Automation through cron (Linux/Mac) or Task Scheduler (Windows)

To perform checks automatically every few hours, set up the script to run on a schedule.

Linux/Mac (via cron):

1. Open the terminal and enter: crontab -e
2. Add a line to run every 6 hours:
   0 */6 * * * /usr/bin/python3 /path/to/check_proxies.py
3. Save — now the script will run automatically

Windows (via Task Scheduler):

1. Open "Task Scheduler"
2. Create a new task → select "Run program"
3. Specify the path to python.exe and the argument — the path to the script
4. Set the trigger: repeat every 6 hours
5. Save the task

Auto-removal of non-working proxies for marketplace parsing

If you are parsing prices on Wildberries, Ozon, or Avito, the problem of banned proxies is especially relevant — marketplaces actively fight against automated requests.

Why marketplaces ban proxies

Wildberries, Ozon, and other marketplaces use anti-parsing protection:

• Request limits from a single IP (rate limiting) — usually 100-200 requests per hour
• IP blocking for suspicious activity (too fast requests, lack of cookies)
• Verification of IP reality — datacenter proxies are blocked more often than residential ones
• Captcha when exceeding limits — if an IP receives captcha several times, it is blocked

For marketplace parsing, we recommend using residential proxies — they look like regular users and are less likely to get blocked.

Integrating proxy checks into the parser

Most ready-made parsers (e.g., Datacol, ParseHub, Octoparse) do not have a built-in function for automatic removal of banned proxies. But you can set up external checks and update the proxy list in the parser.

Algorithm for parsing Wildberries:

1. Create a proxy checking script through Wildberries (similarly to the example above with Instagram, but TARGET_URL = 'https://www.wildberries.ru/')
2. Set up the script to run every 4 hours via cron/Task Scheduler
3. The script saves working proxies in the file working_proxies.txt
4. In the parser settings, specify the path to this file as the proxy source
5. The parser automatically loads the updated list at each launch

This way, the parser always works only with relevant proxies, and banned ones are automatically excluded from rotation.

Setting up proxy rotation in the parser

Besides removing dead proxies, it is important to properly set up the rotation of live ones — to avoid overloading a single IP.

How often to check proxies and when to remove them from the pool

The frequency of proxy checks depends on the type of task and the type of proxy. Here are recommendations for different scenarios:

For Facebook Ads / TikTok Ads arbitrage

• Frequency of checks: every 6-12 hours
• When to remove: if the proxy does not respond 2 times in a row or a ban is received from Facebook
• Ban criterion: when trying to access Facebook Ads through the proxy, an account block appears or verification is required
• Type of proxy: mobile proxies (for farming) or residential (for launching campaigns)

For SMM (Instagram, TikTok, VK)

• Frequency of checks: every 12-24 hours
• When to remove: if the proxy does not work or Instagram requires identity verification at each login
• Ban criterion: constant captchas, action blocking (likes, comments), shadowban
• Feature: for Instagram, IP stability is important — do not change proxies for one account unnecessarily

For marketplace parsing

• Frequency of checks: every 2-4 hours (marketplaces ban quickly)
• When to remove: if the proxy receives captcha 3+ times or response speed exceeds 10 seconds
• Ban criterion: Wildberries/Ozon returns error 403, requires captcha, or shows a placeholder
• Strategy: use a large pool (50+ proxies) with fast rotation

Checklist: when to definitely remove proxies from the pool

Automation solution: when to remove, when to keep

To avoid removing proxies during random failures, set up a system with "three attempts":

1. First failed check — mark the proxy as "suspicious," but keep it in the pool
2. Second failed check (after 1-2 hours) — move to the "problematic" category, do not use for new tasks
3. Third failed check — remove from the pool completely

This can be implemented by modifying the verification script — add a "failed_checks" column to the proxy list file and increase the counter on each failure.

Conclusion

Automatic removal of banned proxies from the pool is not just a convenience, but a necessity for professional work with multi-accounting, traffic arbitrage, and data parsing. You have learned several implementation methods: from built-in features in anti-detect browsers (Dolphin Anty, AdsPower) to external verification services and custom scripts in Python.

Choose a method depending on the scale of the task: for 10-20 accounts, manual checking in Dolphin Anty once a day is sufficient; for 100+ accounts or active marketplace parsing, full automation through scripts with checks every 2-4 hours is needed.

Remember the main rule: it is better to check a proxy an extra time than to lose a client account or advertising budget due to a banned IP. Set up automatic checks once — and forget about the problem forever.

If you are looking for reliable proxies for arbitrage, SMM, or marketplace parsing, we recommend trying residential proxies — they provide a high level of trust from platforms and minimal risk of blocks. For farming Facebook and Instagram accounts, mobile proxies with automatic IP rotation will be suitable.