Minimum Connection Time Filter
Note: Expert settings are only available for Core Residential Proxies.
Evomi Residential Proxies offer a connection stability filter that ensures you only receive IPs that have maintained persistent connections to our network. This feature is particularly valuable when using sticky sessions or conducting long-running transactions.
How It Works Permalink to How It Works
The _activesince-<minutes> parameter filters IPs based on their continuous connection duration to our system:
- Measures time since IP first became available in our pool
- Only selects IPs active for at least the specified minutes
- Higher minimum times = increased connection stability
- Particularly effective when combined with session parameters
Usage Permalink to Usage
Add _activesince-<minutes> to your proxy password:
http://testuser:testpassword_activesince-60@rp.evomi.com:1000Implementation Examples Permalink to Implementation Examples
curl -x http://rp.evomi.com:1000 -U testuser:testpassword_session-mysession_activesince-120 https://ip.evomi.com/sImportant Considerations
- This is an extra feature with increased bandwidth costs
- Higher minimum times reduce available IP pool size
- Due to a number of factors its possible for ips to reconnect in batches, slashing the number of available IPs for a certain minimum time to 0, make sure to handle errors on your side if no IP is available.
- Recommended maximum: 240 minutes (4 hours)
- Combines best with
sessionorhardsessionparameters
Stability vs Availability Tradeoff
While longer-active IPs provide better stability, setting extremely high values (>300 minutes) may significantly limit available IPs. We recommend starting with 60-120 minute thresholds.
While longer-active IPs provide better stability, setting extremely high values (>300 minutes) may significantly limit available IPs. We recommend starting with 60-120 minute thresholds.
Ideal For
- Financial data scraping
- Multi-step checkout processes
- Account management workflows
- API interactions requiring persistent IP behavior