# Latency Filter

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

**Note:** Expert settings are only available for **Core Residential Proxies**.

Evomi Residential Proxies offer a latency-based IP filtering feature that helps you select faster connections for time-sensitive operations. This parameter lets you specify the maximum network latency for IPs in milliseconds (ms).

**Real-World Considerations**  
While our tests provide consistent benchmarks, actual user-experienced latency may vary due to:
- Geographic distance between you and the IP
- Network congestion
- Target server response times
- Local network conditions

## Using the Latency Filter
Append `_latency-<ms>` to your proxy password to set maximum latency:

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

## Implementation Examples

#### CURL

  ```bash
curl -x http://rp.evomi.com:1000 -U testuser:testpassword_latency-500 https://ip.evomi.com/s
```

#### Python

  ```Python
import requests

proxy_pass = "testpassword_country-US_latency-300"
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_latency-550_session-mysession';
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 Notes**  
1. Latency filtering is an extra feature with increased bandwidth costs
2. Lower latency values significantly reduce available IP pool size
3. Recommended minimum value: 300ms
4. Combines with most parameters except `extended` pool

**Optimization Tip**  
Start with higher latency values (1000-1500ms) and gradually decrease while monitoring success rates. Sudden drops in performance may indicate too strict latency filtering.

**Best For**  
- Real-time web interactions  
- High-frequency trading data collection  
- Low-latency API integrations  
- Live price monitoring  
- Time-sensitive account operations