# Minimum Connection Time Filter

Source: https://docs.evomi.com/proxy-instructions/residential-proxies/expert-settings/minconnection/

**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
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
Add `_activesince-<minutes>` to your proxy password:

<!--email_off-->
```bash
http://testuser:testpassword_activesince-60@rp.evomi.com:1000
```
<!--email_on-->

## Implementation Examples

#### CURL

  ```bash
curl -x http://rp.evomi.com:1000 -U testuser:testpassword_session-mysession_activesince-120 https://ip.evomi.com/s
```

#### Python

  ```Python
import requests

proxy_pass = "testpassword_hardsession-xyz_activesince-90"
proxy_url = f"http://testuser:{proxy_pass}@rp.evomi.com:1000"

proxies = {
  "http": proxy_url,
}
response = requests.get("https://ip.evomi.com/s", proxies=proxies)
print(response.text)
```

#### JavaScript

```JavaScript
const fetch = require('node-fetch');

const proxyPass = 'testpassword_session-abc_activesince-180';
const proxyUrl = `http://testuser:${proxyPass}@rp.evomi.com:1000`;
const url = 'https://ip.evomi.com/s';

fetch(url, { proxy: proxyUrl })
  .then(res => res.text())
  .then(body => console.log(body));
```

**Important Considerations**  
1. This is an extra feature with increased bandwidth costs
2. Higher minimum times reduce available IP pool size
3. 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.
4. Recommended maximum: 240 minutes (4 hours)
5. Combines best with `session` or `hardsession` parameters

**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.

**Ideal For**  
- Financial data scraping  
- Multi-step checkout processes  
- Account management workflows  
- API interactions requiring persistent IP behavior