# Residential Overview

#### Residential Proxy Business Model

The Residential product range is distinct and has several differences to other ranges which are sold per IP Address like Static Residential and Datacenter Proxies.

A Residential Service allows a customer to access our global residential proxy network on a bandwidth basis. They can purchase between 1GB and 5TB of bandwidth in a service and this allows them to use the respective traffic amount across our network.

The Residential Service type is not region specific and is not sold per IP address resulting in several differences in terms of proxy management.

#### One Residential Proxy Service Per Account

Unlike other product types, there can only be a single active Residential Proxy Service attached to a customer account at any given time.

If a customer wants more bandwith then they must reconfigure the service rather than purchasing another one.

{% hint style="info" %}
You can see if a customer has an active residential service by using the Customer Retrieve API Route.

If a active\_residential\_service\_id value is returned then the customer has a residential service and you can use the ID for Residential API Route calls.
{% endhint %}

#### Customer Traffic Limit vs ProxyUser Traffic Limit

There are two different traffic limit levels which can effect residential proxy service usage.

The main traffic limit is at the customer account level and is directly tied to the residential service package size on the account. All traffic from all ProxyUsers increments against this limit and if a customer were to have a 1TB limit then all ProxyUsers on their account could use up to 1TB between them.

The secondary traffic limit is per ProxyUser and is set with the ProxyUser Create / Edit  API Route. This limit allows you to restrict a ProxyUser to a limit below the overall customer account traffic limit.

```
// Example - Assume beginning of service with no usage

Active Residential Service Size: 1TB
Customer Traffic Limit: 1TB

ProxyUser ID (1): No ProxyUser Limit Appplied
ProxyUser ID (2): ProxyUser Limit Appplied @ 100GB

ProxyUser ID (2) uses 100GB and they hit their Customer Traffic Limit and new requests are rejected. The customer level traffic usage is incremented by 100GB as well.
ProxyUser ID (1) can not use up to 4.9TB as they are not ProxyUser limited and all traffic left at a customer level.
```


---

# 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://internal.developer.documentation.private.user.pingproxies.com/residential-package-management/residential-overview.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.