# ASN Targeting

You can select a specific ASN (Autonomous System Number) when connecting through Plain Proxies’ residential proxies. This gives you control over the origin of your connection, which is useful for applications that require IPs from specific ISPs. PlainProxies' Residential Proxy Pool consists exclusively of verified residential IP addresses. 

All **non-residential** endpoints including **corporate, institutional, and data center IPs are systematically identified** and **excluded** from the pool, ensuring a purely residential network.

#### Connection format with ASN <a href="#id-3-connection-format-with-asn" id="id-3-connection-format-with-asn"></a>

To use a specific ASN, include the desired ASN number in the username, like this:

```
res-v2.pr.plainproxies.com:8080:user-asn-7018:password
```

In this example, 7018 is the ASN of AT\&T, one of the largest residential ISPs in the United States.

You can replace the ASN with any other of your choice. If we have IPs available for it, your connection will succeed.

#### What happens if the ASN is not available <a href="#id-3-what-happens-if-the-asn-is-not-available" id="id-3-what-happens-if-the-asn-is-not-available"></a>

You can request any ASN. However, if there are no IPs available with the requested ASN at the moment, the system will return an error. We recommend testing different options based on your needs.

#### Common ASN examples from major ISPs <a href="#id-3-common-asn-examples-from-major-isps" id="id-3-common-asn-examples-from-major-isps"></a>

Below are examples of public ASNs in US:

* AT\&T: 7018
* Comcast: 7922
* CenturyLink / Lumen: 209


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.plainproxies.com/proxies/residential-proxies/asn-targeting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.