> For the complete documentation index, see [llms.txt](https://docs.ipdunar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipdunar.com/products/overview-1/locations.md).

# Locations & carriers

Mobile coverage spans **80+ countries** with at least one major carrier per country. Unlike residential, mobile is **carrier-first, geography-second** — `asn` (the carrier) is usually a bigger lever than `state` or `city`.

## Country (region)

Required. Lowercase ISO-3166 alpha-2.

```
ipdunar_s1a2b3c4d5e-type-mob-region-us
```

Top markets by pool size: US, GB, DE, FR, JP, KR, BR, IN, ID, MX, CA, AU.

For the live list:

```bash
curl -H "Authorization: Bearer API_KEY" \
     https://api.ipdunar.com/v1/mobile/locations
```

## Carrier (ASN)

The mobile carrier you want to look like. Highly recommended on every mobile workload — see [ASN targeting](https://docs.ipdunar.com/products/overview-1/asn-targeting.md) for the full table and rationale.

```
ipdunar_s1a2b3c4d5e-type-mob-region-us-asn-6167   # Verizon Wireless
ipdunar_s1a2b3c4d5e-type-mob-region-jp-asn-2516   # KDDI
ipdunar_s1a2b3c4d5e-type-mob-region-de-asn-3209   # Vodafone DE
```

## State / city (limited)

`state` and `city` are accepted but the live pool is usually small. Use only in tier-1 markets and only when geo precision is critical:

```
ipdunar_s1a2b3c4d5e-type-mob-region-us-state-ca-city-la-asn-6167
```

If the combined filter has fewer than 10 live IPs, the gateway returns `522` + `X-IPdunar-Insufficient-Pool: true`. Drop `city` first, then `state`.

## Major carriers per top market

| Country | Carrier                       | ASN   |
| ------- | ----------------------------- | ----- |
| US      | Verizon Wireless              | 6167  |
| US      | T-Mobile                      | 21928 |
| US      | AT\&T Mobility                | 20057 |
| GB      | EE / BT                       | 12576 |
| GB      | Vodafone UK                   | 12969 |
| DE      | Deutsche Telekom / Telekom DE | 3320  |
| DE      | Vodafone DE                   | 3209  |
| DE      | Telefónica O2 DE              | 6805  |
| FR      | Orange                        | 3215  |
| FR      | SFR                           | 15557 |
| JP      | KDDI                          | 2516  |
| JP      | NTT Docomo                    | 9605  |
| JP      | SoftBank                      | 17676 |
| KR      | SK Telecom                    | 9318  |
| BR      | Vivo / Telefónica BR          | 26599 |
| IN      | Reliance Jio                  | 55836 |
| IN      | Airtel                        | 24560 |

The ASNs listed are the public BGP ASNs; some carriers route mobile traffic through multiple ASNs. The API endpoint above lists every routable ASN per country.

## Why `state`/`city` is often empty on mobile

Mobile devices move. The geo data we have for a SIM is at best metro-area accuracy and at worst country-only (when the carrier doesn't expose finer info). When city granularity is needed, residential is the better tool.

## Coverage at a glance

| Coverage                         | Count |
| -------------------------------- | ----- |
| Countries with live IPs          | 80+   |
| Countries with multiple carriers | 30+   |
| Tier-1 markets (deep pools)      | 12    |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ipdunar.com/products/overview-1/locations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
