Management & FAQ
Instance management, automatic renewal rules, IP retention guarantee, and common troubleshooting tips for static residential proxies.
Management & Frequently Asked Questions (FAQ)
This guide covers everyday management, automatic renewal mechanics, IP preservation, and troubleshooting for BytesFlows static residential proxies.
1. Instance Management
Edit Instance Remarks
In the management dashboard, click Edit Remark on any instance to assign custom tags (e.g. Amazon-US-Store-01 or TikTok-Account-LA). This helps teams isolate multiple stores without confusion.
Term Tracking
Every static proxy displays its precise start and expiration timestamp. When an instance has fewer than 3 days remaining, an amber alert banner appears in the console.
2. Auto-Renew Rules
- Execution Timing: Instances with Auto-Renew enabled automatically initiate renewal 24 hours before expiration.
- Payment Source: Funds are deducted directly from your account wallet balance.
- IP Retention: As long as the instance renews, your assigned static residential IP never changes, ensuring seamless session continuity.
- Grace Period: If renewal fails due to insufficient balance, an emergency 24-hour grace period applies before the node is decommissioned.
3. Frequently Asked Questions
Q1: What is the primary difference between static and rotating residential proxies?
Static residential proxies provide a fixed, unchanging IP address with unlimited bandwidth across your rental period. Rotating residential proxies bill per GB and rotate IPs frequently. For e-commerce stores and social media management, static proxies are mandatory to avoid security challenges.
Q2: Why is Dual-ISP critical?
Dual-ISP addresses are provisioned directly from tier-1 consumer carriers (e.g. AT&T, Verizon) and carry clean residential reputation, bypassing datacenter proxy detection engines.
Q3: When should I enable UDP?
UDP is beneficial for real-time applications:
- Live streaming (TikTok Live Studio, OBS streaming)
- VoIP & audio calls (WhatsApp Call, Telegram voice)
- Low-latency gaming For standard web browsing and store backends, standard TCP (HTTP/SOCKS5) is sufficient.