> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.pixalate.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.pixalate.com/_mcp/server.

# Proxy gateway reference list

> Pixalate's proxy gateway list (Gateways file) of proxy, Tor and gateway IPs with the average number of users behind each, used as a reference list to refine IP blocking.

The proxy gateway list surfaces gateway IP addresses, such as proxies, Tor nodes and network gateways, and estimates the average number of users behind each one. Malicious users hide their real IP behind these nodes, and most suspicious activity, including botnet distribution and control, takes place behind them. But a gateway such as a home router also puts many legitimate devices behind a single IP.

> **Warning**
>
> This is a **reference list, not a block list**. Don't block every IP on it. Use it as extra information to refine your IP or device blocking, for example to decide whether blocking an IP would also block many legitimate users.

## When to use it

Use the gateway list to build extra logic on top of your blocking feeds. For example, block a flagged IP only when the gateway list shows a small number of users behind it, so you don't block a large group of users.

If you're looking for proxy and Tor IPs to block, use the [IP block lists](/data-feeds/ip-block-lists) instead. They include Tor and proxy IPs (for example under the `proxy` fraud type) when they meet Pixalate's high-IVT criteria.

## At a glance

|             |                     |
| ----------- | ------------------- |
| File format | CSV                 |
| File name   | `Gateways_YYYYMMDD` |
| Columns     | `IP`, `user_bucket` |
| File size   | Up to 1 GB          |

For the update schedule, access and file locations, see [Delivery and integration](/data-feeds/delivery) or contact [support@pixalate.com](mailto:support@pixalate.com).

## Schema

| Column        | Type   | Description                                                                                                                 |
| ------------- | ------ | --------------------------------------------------------------------------------------------------------------------------- |
| `IP`          | string | A gateway IP address.                                                                                                       |
| `user_bucket` | string | The range that the average number of users behind the IP falls in, written as `lower-upper` (for example `2-5`), or `500+`. |

Every gateway has more than one user, so the buckets start at 2.

| `user_bucket` | Average number of users behind the IP |
| ------------- | ------------------------------------- |
| `2-5`         | 2 to 5                                |
| `6-10`        | More than 5, up to 10                 |
| `10-20`       | More than 10, up to 20                |
| `20-50`       | More than 20, up to 50                |
| `50-100`      | More than 50, up to 100               |
| `100-500`     | More than 100, up to 500              |
| `500+`        | More than 500                         |

Example rows (made-up values):

```csv
203.0.113.14,2-5
198.51.100.77,20-50
192.0.2.201,500+
```

## Apply it pre-bid

1. Load the latest gateway file next to your IP block lists.
2. When a request's IP is flagged by one of your blocking feeds, look up the IP in the gateway list.
3. Use the `user_bucket` value in your blocking rule. For example, block the IP when few users sit behind it, and treat IPs with many users with more care.

## Related

#### [IP block lists (IPv4 and IPv6)](/data-feeds/ip-block-lists)

IPs to block, including proxy and Tor IPs, with fraud types and probabilities.

#### [Data center feeds](/data-feeds/data-center)

Weekly IPv4 and IPv6 CIDR ranges of hosting and cloud providers.

#### [Delivery and integration](/data-feeds/delivery)

Access, file locations and polling for every feed.