Threads Proxy: One Static Residential IP per Threads Account

Why Threads needs a proxy

Threads is blocked in mainland China — GreatFire's recent tests of threads.com from there failed — and it comes from Meta, whose Facebook and Instagram have been blocked in Russia since 2022. In our hourly checks on 18 October 2026, the Russian residential exit did not reach threads.com while the other test countries did.

Brand teams that schedule Threads posts use the Threads API: each post is created as a media container and then published, Meta recommends waiting about 30 seconds between those two calls, and a profile can publish up to 250 posts in 24 hours. The limit belongs to the profile, so a proxy never changes it.

Agencies run many brand profiles from one office line, so every login and every API call arrives from the same address. A static ISP IP per account — a home-broadband address in the country you choose, fixed for the term and assigned only to you — keeps each profile on its own steady connection.

• Sources:
• GreatFire Analyzer: www.threads.com from mainland China
• Freedom House: Freedom on the Net 2025 — Russia
• Proxy302 hourly connectivity checks: Threads
• Threads API: Posts
• Proxy302 static ISP configuration

Recommended Threads setup

Scroll horizontally with the arrow keys to read all content.

The “Configure Threads proxies” button at the top of this page opens the Threads proxy setup: static ISP, billed per IP and term, with SOCKS5 selected. Choose the region and Quantity (one IP per account, up to 100) before you pay.

• Sources:
• Proxy302 static ISP configuration

Which Proxy302 proxy to buy

Scroll horizontally with the arrow keys to read all content.

Top up your wallet, then buy the line you need. Auto-renew is not available yet, so renew each IP in My assets before its term ends.

• Sources:
• Proxy302 static ISP configuration
• Proxy302 pricing

Set up Threads proxies in 4 steps

1. Open the Threads setup

   The “Configure Threads proxies” button at the top of this page opens the static ISP page with Billing set to Per IP and term, the Social operations use case and Threads proxy selected. Under Connection settings pick the Region, keep Term at 1 month and Protocol at SOCKS5, set Quantity to the number of IPs you need (one for each account, up to 100 at a time), then click Review cost and generate.

   Expected result The “Your configuration” panel shows Per IP and term, your region, SOCKS5 and the quantity.

2. Copy each IP's details

   Open My assets, choose View credentials on each IP and copy the endpoint (host:port), username and password. Note which Threads account each IP belongs to.

3. One browser profile per account

   In AdsPower, Dolphin Anty, GoLogin or Multilogin create a profile per account, choose SOCKS5, paste the details and set WebRTC to follow the proxy. Check the exit on an IP-check page, then log in at threads.com. If the account is linked to a brand's Instagram account, run both in this same profile.

   Expected result The IP-check page shows the country you bought.

   Before continuing Never log two Threads accounts in through the same IP or profile.

4. Schedule through the API on the same IP

   For scheduled posts, send each account's Threads API calls through that account's IP, as in the example below. Check the account's remaining quota with GET {threads-user-id}/threads_publishing_limit before large batches.

Publish a Threads post through the account's IP

Scroll horizontally with the arrow keys to read all content.

# pip install requests
import time

import requests

TOKEN = "THREADS_ACCESS_TOKEN"
USER_ID = "THREADS_USER_ID"
BASE = f"https://graph.threads.net/v1.0/{USER_ID}"
# This account's API calls leave through its own static ISP IP
PROXIES = {"https": "http://USERNAME:PASSWORD@HOST:PORT"}

container = requests.post(
    f"{BASE}/threads",
    params={"media_type": "TEXT", "text": "Hello from our brand account", "access_token": TOKEN},
    proxies=PROXIES,
    timeout=30,
)
container.raise_for_status()
creation_id = container.json()["id"]

time.sleep(30)  # Meta recommends waiting about 30 seconds before publishing

published = requests.post(
    f"{BASE}/threads_publish",
    params={"creation_id": creation_id, "access_token": TOKEN},
    proxies=PROXIES,
    timeout=30,
)
published.raise_for_status()
print("Published post:", published.json()["id"])

Two calls: create a text container, wait, then publish it. For an IP bought with SOCKS5, install requests[socks] and use socks5h://USERNAME:PASSWORD@HOST:PORT.

• Sources:
• Threads API: Posts

Quick fixes

Threads proxy FAQ

Related setups

Instagram proxies

Instagram proxies for brands and agencies: one static ISP IP per account, in the US, UK or the country you pick. Works in antidetect browsers and on iPhone.

View options and pricing

X (Twitter) proxies

Twitter (X) proxy for brand, client and regional accounts: one static ISP IP per account in the country you choose, SOCKS5 or HTTP — also where X is blocked.

View options and pricing

Keep one exit for a longer workflow

Dedicated static ISP proxies: a residential-grade IP that is yours alone and stays the same for the whole term. For social accounts, stores and AI tools. HTTP and SOCKS5.

View options and pricing

Related guides

Platform access by country

Which countries block Discord, YouTube, Instagram, Telegram and more — and hourly checks showing all 38 platforms reachable through residential IPs in 7 countries.

Proxies in antidetect browsers

Set up a proxy in AdsPower, BitBrowser, GoLogin, Kameleo, Hidemium or GenLogin: one IP per profile, where each field goes, and what a failed proxy check really means.

Check a proxy's IP, country and ISP

Check the exit IP, country and ISP your proxy really gives you in 30 seconds — and why IP databases disagree on the city. With our own test of three lookup services.

Residential vs ISP vs datacenter proxies

What separates rotating residential, static ISP and datacenter proxies — who owns the IP, whether it changes, how you pay — and which one Proxy302's own presets pick for each job.