UK proxies: networks, regions and location checks

Choose the UK behaviour you need to verify

A UK proxy provides an intermediary exit that a supplier represents as being in the United Kingdom. That can help you evaluate your own service from a different network perspective, but the country label leaves important questions unanswered. A UK storefront check, a London location rule and an issue reported by an O2 mobile user need different evidence.

Begin with a sentence describing the expected application behaviour. For example: our country selector should offer the UK experience when the request arrives from an address our location database classifies as UK. That criterion can be tested. Requiring an authentic British user experience is too broad: account settings, delivery details and browser state may change the result independently of the proxy.

Name the destination, the location source your application uses, the required access type and any city or network restriction. Decide which findings would stop the trial. This guide helps you specify that evaluation; it does not describe available ipvolt endpoints or confirmed relationships with the networks mentioned below.

Resolve UK, GB and the geographical scope

The UK includes England, Scotland, Wales and Northern Ireland. Great Britain means England, Scotland and Wales, excluding Northern Ireland. Government geographical guidance also identifies Jersey, Guernsey and the Isle of Man as Crown Dependencies outside the UK. A broad British label therefore deserves a precise scope before it enters a test specification.

There is a separate naming trap in country codes. The same government guidance gives GB and GBR as the ISO codes for the United Kingdom. A documented GB country selector can consequently include Northern Ireland: it does not necessarily mean the geographical island of Great Britain. Use the supplier's documented parameter and meaning instead of guessing between uk and gb.

A country selection still does not promise an exit in each UK nation. If reproducing an issue requires Belfast or Glasgow specifically, request that capability separately and agree how it will be evidenced. Include a Crown Dependency only when your application has an explicit case for it; do not silently count it as a UK sample.

Account for the Vodafone and Three merger

VodafoneThree's completion announcement states that Vodafone UK and Three UK merged on 31 May 2025. Its current company description includes Vodafone UK, Three UK, VOXI, SMARTY and Talkmobile. Seeing Vodafone and Three listed separately in a proxy menu is therefore insufficient evidence of two independent operator businesses.

Ofcom's August 2025 coverage methodology names EE, Virgin Media O2 and VodafoneThree as the mobile-network operators providing predictions. Its consumer checker still displays EE, O2, Three and Vodafone labels. These sources describe different layers of a changing market; preserve the label and date of each observation instead of making a four-brand menu your ownership model.

For a provider offering both Vodafone and Three selections, request the definition of each filter and its current verification method. Do they describe subscription brands, different address groups, or something else? A merger announcement alone does not tell you whether two requested selections produce the same exit route, nor does it prove that either selection is available from that provider.

Keep the brand, host network and access type separate

Ofcom's checker FAQ illustrates the distinction between a retail service and its underlying network. It maps BT Mobile and 1p Mobile to EE; Tesco Mobile, giffgaff and Sky Mobile to O2; VOXI to Vodafone; and SMARTY to Three. Treat these as dated reference mappings, then ask for the current mapping of the specific service under evaluation.

That distinction matters when building a comparison. Two different retail names may share a host network, so counting their names can overstate the diversity of your sample. Conversely, a different routing organization is a finding to investigate, not automatic proof that the retail description is false. Ask how the actual connection and exit address relate to the label.

Keep mobile access, fixed broadband and hosting access in separate fields. VodafoneThree itself serves fixed and mobile markets, so a group-name match cannot classify an exit on its own. For a claimed mobile sample, request evidence of the access arrangement as well as the network selection. For a country-only application check, decide whether a documented hosting exit already satisfies the narrower requirement.

Also establish how the underlying connections are authorized for the offered service. A familiar carrier name does not supply that explanation. Record the supplier's answer alongside its definition of the product, especially if your requirement depends on household or mobile participation rather than simply a UK location result.

Use coverage maps for the question they answer

Ofcom's Map Your Mobile offers local signal information and a separate performance view. Its methodology uses operator predictions for coverage and crowdsourced measurements aggregated into postal districts or areas for performance. The regulator explicitly describes uncertainty in predicting service at a particular location.

This information is relevant when evaluating where a handset might obtain mobile service. It does not identify the public IP a proxy request will use, establish the location assigned to that address, or measure the proxy gateway between your client and the destination. A favourable local map result cannot substitute for a successful application trial.

Suppose a provider uses a Manchester coverage screenshot to support a Manchester mobile-proxy claim. Ask for the missing link: what connects this supplied exit to the claimed access arrangement and selectable location? Keep the screenshot as background context, then evaluate the destination-observed address and the provider's documented selection. Do not infer a proxy speed or a city guarantee from the radio-coverage display.

Test London and postcode rules independently

IP geolocation is an estimate. MaxMind says its data cannot locate a particular household or street address, and accuracy depends on the network and address type. City results may include an accuracy radius; mobile addresses may lack a city or postal-code result. A London label should therefore be read with its available precision, not converted into an exact postcode.

For an application you control, distinguish the inferred city from a postcode someone enters. A delivery checker may use the supplied address; a country banner may use IP location; a language preference may come from the browser or an account. Determine which input the feature is intended to use before calling a result incorrect.

If your test requires a London-classified exit, retain the named location service, lookup timestamp, returned city and any radius or confidence field. An absent city is unresolved evidence for that requirement, even if the country passes. If the test instead checks postcode rules, use approved synthetic address fixtures and vary that input while holding the network configuration constant.

Build an evidence record for each selection

Use the related curl setup guide to establish connectivity with deadlines and private credentials. For exit identification, use a documented diagnostic service or an endpoint you control that records the connecting source address. The proxy gateway's resolved address is a different observation. If your destination is behind a CDN, verify its trusted forwarding configuration before relying on a reported client address.

Capture the observed exit IP, address family, time, requested country and optional network filter. RIPEstat's Network Info endpoint supplies a containing prefix and announcing ASN information from RIPE RIS. Save that routing observation alongside the geographic lookup and the supplier's explanation of its brand mapping.

RIPE's resource documentation warns that its country attribute cannot reliably locate an IP address: the value can refer to different aspects of the resource or organization. A GB registration field therefore does not complete a UK exit-location test. An ASN match similarly provides routing context rather than proof of a SIM, postcode or supplier contract.

Preserve requested and observed labels separately. For example, keep a requested Three filter and the returned organization exactly as recorded, plus the explanation you obtained. Do not rewrite historical rows when a brand or mapping changes. Dated evidence makes a later support conversation much more useful than a screenshot labelled working UK proxy.

Run a bounded UK application trial

The following matrix is a suggested experiment for your own service, not a report of tests performed by ipvolt. Select only the rows your application needs and obtain the necessary trial access. An unavailable carrier or city selection should remain unavailable in the record; a generic UK substitute cannot complete that row.

For an initial pass, choose two documented proxy selections and make three sequential diagnostic requests for each, with a short pause between requests and a fixed deadline. That is six diagnostic requests, with no automatic retries. Keep session settings unchanged within a selection and retain unsuccessful attempts. This small sample is intended to uncover configuration and classification problems, not to estimate long-term reliability.

• UK country rule: hold the account and browser settings constant; compare the observed exit country with the location service used by your application. Pass only the country criterion, leaving city and carrier outside that result.
• London location rule: use a documented city selection if offered; capture its city evidence and the application's response. If selection is country-only, label a London result incidental rather than repeatable city targeting.
• Northern Ireland application case: use an approved Belfast address fixture for address-driven behaviour. If the issue requires a local network exit as well, require separate location evidence; a GB country code alone does not establish Belfast.
• EE or O2 network issue: keep the same small application fixture and request a documented network selection. Record the retail label, host explanation and routing evidence. Do not count two O2-hosted brands as two independent host-network samples.
• Vodafone versus Three comparison: retain both requested filters and all observed prefixes, including identical results. Ask the supplier to explain overlap before treating the pair as independent network coverage.

Decide what passed and what still needs explanation

Separate transport success, country classification, optional city classification and application behaviour. A UK exit with no city can satisfy the first location requirement while leaving the London row open. A correctly classified exit followed by the wrong storefront language calls for an application-input check before switching networks.

When the returned country is unexpected, first confirm the exact exit address and the documented selector. Keep any disagreement between dated location services visible and send the provider a sanitized example. For a timeout, follow the related troubleshooting guide and record a transport failure rather than inventing a location result for a response that never arrived.

Before committing, clarify what happens when a requested network is unavailable, whether fallback changes the country or carrier, and how session expiry affects the selections you tested. Ask how location disputes are handled and which promises are contractual. The useful outcome is an agreed acceptance record with limitations, not a claim that a handful of requests represents every UK user.

ipvolt has not secured UK supply agreements or confirmed UK country, city or carrier inventory. This educational guide is independent of future availability. Joining the waitlist records interest; it does not reserve a British IP address, a specific network or an access date.