k6 · PROXY SETUP

k6 proxy setup

Load-testing tool from Grafana. Point it at the Eveses residential pool with the configuration below — the geo lives in the username, so nothing else in your setup has to change to move country.

proxy.eveses.com:12321 · SOCKS5 on 32325 · 199 countries · from $7.35/GB

Get proxies →All integrations
Watch out

k6 has no proxy option in the script — it reads HTTP_PROXY and HTTPS_PROXY from the environment only, and it ignores lower-case variants on some platforms. Be aware that a load test through a metered residential pool bills every virtual user's traffic; datacenter IPs are the right pool for load work.

Configuration

# k6 reads the environment; there is no proxy option in the script.
export HTTPS_PROXY="http://eveses_user_country-us:[email protected]:12321"
export HTTP_PROXY="$HTTPS_PROXY"

k6 run script.js

Notes for k6

Use datacenter or ISP IPs for load testing. Residential is metered by the gigabyte and a load test is, by design, a lot of gigabytes.

Only load-test infrastructure you own or have written permission to test.

Change country without touching k6

Germanyeveses_user_country-de
Sticky 30 mineveses_user_country-de_session-ab12cd34_lifetime-30m

The geo and the session live in the username, not in the host or the port. Every configuration on this page stays exactly as it is when you move country — you edit one string. 199 countries are addressable, with city and state tokens inside most of them.

FAQ

How do I set a proxy in k6?›
Point it at proxy.eveses.com on port 12321 for HTTP, or 32325 for SOCKS5, and authenticate with your Eveses proxy username and password. The exact syntax is in the snippet above. k6 has no proxy option in the script — it reads HTTP_PROXY and HTTPS_PROXY from the environment only, and it ignores lower-case variants on some platforms. Be aware that a load test through a metered residential pool bills every virtual user's traffic; datacenter IPs are the right pool for load work.
How do I choose the country k6 exits from?›
Append a geo token to the USERNAME rather than changing the host: eveses_user_country-de reaches Germany, eveses_user_country-us the United States. 199 countries are addressable this way, and city or state tokens narrow it further. Nothing else in your k6 configuration changes.
How do I keep the same IP across requests in k6?›
Add a session token — eveses_user_country-us_session-ab12cd34_lifetime-30m — and every request carrying that username exits from the same address until the lifetime runs out. Drop the token and each request rotates to a fresh IP.
What does this cost?›
Residential traffic is billed by the gigabyte from your Eveses wallet: $7.35/GB at 1 GB, falling to $2.57/GB in volume. There is no per-tool charge, and the same credentials work in every tool at once.
Paste your own curl → get it in javascript →

Other integrations

ScrapySeleniumPuppeteerPlaywrightPython requestsHTTPXaiohttpAxiosnode-fetch / undiciGuzzle

Run k6 through residential IPs

$7.35/GB at 1 GB, $2.57/GB in volume — same credentials in every tool.

Get proxies →