---
name: proxy-provider-switch
description: "Switched Ultron's residential proxy from DataImpulse to Evomi on 2026-07-05"
metadata: 
  node_type: memory
  type: project
  originSessionId: e76b8acc-b39e-441c-ad82-68c4ed982296
---

Ultron's Saudi residential proxy moved from DataImpulse to Evomi on 2026-07-05.

**Why:** DataImpulse's initial topup was only $5, but the NEXT topup after that demanded a $50
minimum — Ahmed didn't want to commit that much. Evomi is pay-as-you-go with no big minimum
(bought 15GB to start), and has confirmed Saudi Arabia city-level targeting.

**Mechanics (see CLAUDE.md credentials table + src/browser.js for the current, authoritative
version):** Evomi's country targeting goes on the PASSWORD (`_country-SA` suffix), not the
username — the opposite of DataImpulse's `__cr.sa`-on-username scheme. This was a real gotcha
when swapping the code over; if a future proxy switch happens, check the new provider's docs for
which field carries geo-targeting before assuming the old pattern carries over.

**How to apply:** If proxy errors show up again (ERR_PROXY_AUTH_UNSUPPORTED etc.), check Evomi
account balance first, not DataImpulse — that account is retired for this project now. Don't
assume env var names changed; PROXY_HOST/PORT/USER/PASS/COUNTRY were kept the same, only their
values and how COUNTRY gets used changed.