Proxy expert needed -help country/City Level Accuracy at Scale for meta ad's & browser automations

**About us** UK software company. Our product runs isolated browser sessions for business customers via GoLogin desktop app (open to suggest change), each on its own dedicated static IP (purchased from IProyal), geo-matched to the city that customer trades in. Handful of sessions now, scaling to 50–100 over the next year. **The problem** We buy static ISP IPs advertised as UK, specific city. They pass every geolocation checker we test. Then the service we're connecting to resolves the session to a different country entirely — most recently Azerbaijan, on an IP sold to us as Manchester. A trial IP from a different provider resolved correctly to London first time. So the question iw why one provider's UK IP resolves accurately and another's doesn't, how to know before we pay, and where to buy consistent and realisbale proxys (think we need ISP proxys for this particular automation) how to build a sourcing process that holds up at volume. **What you should know** - practical differences between static ISP, datacentre and residential IPs, and where each breaks - why an IP's registered location, the commercial GeoIP databases (MaxMind, IP2Location, IPinfo) and a given service's own internal geolocation can all disagree - how to get an inaccurate record corrected, and how long it realistically takes - ASN and subnet reputation, and how to check it before buying - current provider landscape for UK and US static ISP at low volume - anti-detect browser platforms (GoLogin, Multilogin, AdsPower, Dolphin) and how proxy config interacts with them - what makes a long-lived session persist versus get invalidated Most likely background is performance marketing or paid social agency operations, where you've run many separate browser profiles on dedicated IPs in production. Not a proxy reseller. **Engagement** Paid consultation to start, one to five hours, call/messages and screenshare/send screen recording - whatever is most effifect and effective. If it works, ongoing advisory as we scale — reviewing providers, sanity-checking IPs before we commit, and writing an internal sourcing SOP. **Deliverables** 1. Written recommendation on two or three providers for UK and US static ISP, with rough pricing. 2. A verification checklist — what we test before committing to an IP, in what order. 3. Your view on our current setup and what you'd change. **To apply — answer these four** 1. You're sold an IP as "Manchester, UK" and the service resolves it somewhere else. Likely causes, in order, and how do you work out which one it is? 2. Which providers do you currently use for static UK ISP IPs? 3. What do you check on an IP before committing? Be specific. 4. How many separate profiles and IPs have you run at once, for how long, and what broke? Tell us your hourly rate for the initial consultation. Title: Proxy Infrastructure Consultant — Static ISP Proxies with Accurate UK & US Geolocation About us We're a UK software company building a listing and enquiry tool for car dealerships. Each customer runs in an isolated browser profile with its own dedicated static proxy, city-matched to where that dealership actually trades. We're at a handful of accounts now and scaling toward 50–100 over the next year. The problem We buy static ISP IPs advertised as UK, specific city. They test clean on every geolocation checker we run. Then the platform resolves the session to a different country entirely — most recently Azerbaijan, on an IP sold to us as Manchester. A trial IP from a different provider resolved correctly to London on the first attempt. So the question isn't where to buy proxies. It's why one provider's UK IP resolves correctly and another's doesn't, how to know before we pay, and how to build a sourcing process that gives consistent city-level accuracy at volume. Who we're looking for Someone who has run large numbers of separate browser sessions and dedicated IPs in production. Most likely background is performance marketing or paid social agency operations, where you've managed many separate profiles and ad accounts across dedicated IPs. Not a proxy reseller. You should know: the practical difference between static ISP, datacentre and residential IPs, and where each one breaks why an IP's registered location, the commercial GeoIP databases (MaxMind, IP2Location, IPinfo) and a platform's own internal geolocation can all disagree how to get an incorrect record corrected and how long that actually takes ASN and subnet reputation, and how to check it before buying the current provider landscape — who is genuinely good for UK and US static ISP at low volumes anti-detect browser platforms (GoLogin, Multilogin, AdsPower, Dolphin) and how proxy config interacts with them what makes a session persist versus get invalidated The engagement Starts as a paid consultation, one to two hours, call and screen share. If it works, ongoing advisory as we scale: reviewing new providers, sanity-checking IPs before we commit, and writing us an internal sourcing SOP so this doesn't live in one person's head. Deliverables for the first engagement Written recommendation on two or three providers for UK and US static ISP IPs, with rough pricing. A verification checklist — what we test on an IP before committing, and in what order. Your view on our current setup and what you'd change. To apply Skip the generic proposal. Answer these four: You're sold an IP as "Manchester, UK" and the platform resolves it somewhere else entirely. What are the likely causes, in order, and how do you work out which one it is? Which providers do you currently use for static UK ISP IPs, and roughly what do you pay per IP per month? What do you check on an IP before you commit to it? Be specific. How many separate profiles and IPs have you run at once, for how long, and what broke? Budget is open for the right person. Tell us your hourly rate for the initial consultation.