Pixalate — IPv4 & IPv6 Data Center Pre-Bid Blocklists

Now Available

Data Center Pre-Bid Blocklists for IPv4 & IPv6

Programmatic's first pre-bid IPv6 Data Center Blocklist, alongside Pixalate's expanded IPv4 list — two separate weekly CIDR feeds that extend pre-bid protection against data center-originated Invalid Traffic (IVT) across both internet protocols, covering 3,000+ cloud and hosting providers worldwide, including Alibaba Cloud and Tencent Cloud.

Contact Pixalate

Providers Covered Include

AWS Google Cloud Microsoft Azure Alibaba Cloud Tencent Cloud Meta Oracle Cloud IBM Cloud DigitalOcean Hetzner OVHcloud Huawei Cloud & 3,000+ more

3,000+

Cloud & hosting providers covered

Separate weekly feeds — IPv4 & IPv6

Update Frequency: Weekly

Format: CIDR ranges (two separate lists: IPv4 and IPv6)

Access Methods: AWS RTB Fabric, API, FTP, S3

Coverage: North America, Europe & Asia

Data Center Traffic Is Invalid Traffic, Per MRC Standards

Pixalate's Data Center Blocklists identify IP ranges belonging to hosting and cloud infrastructure, where ad traffic originates from servers rather than people. The Media Rating Council (MRC) classifies known invalid data center traffic as General Invalid Traffic (GIVT) — the first category listed in its Invalid Traffic Detection and Filtration Standards.

Required Baseline Filtration

Per the MRC standards, filtration of invalid data center traffic "originating from IPs associated to the three largest known hosting entities: Amazon AWS, Google and Microsoft" is required as a starting point.

Beyond the Big-Three Baseline

Vendors "shall supplement these lists with other information, third-party sources or other techniques ... to account for smaller data centers that may be a source of IVT." Pixalate's lists go beyond the AWS/Google/Azure baseline to 3,000+ providers.

Continuous Evaluation & Update

The MRC further requires that data center lists "be maintained by vendors and subject to continuous evaluation and update." As data center IP space expands and fragments, static or infrequently updated blocklists fall out of date.

Why IPv6 Changes the Data Center Problem

IPv6 adoption is approaching half of all internet traffic, per Google's published adoption data — and data center infrastructure is following suit.

2⁶⁴

Addresses in a Single IPv6 Subnet

The entire IPv4 address space holds 2³² addresses — 4.3 billion. A single standard IPv6 subnet (a /64) holds 2⁶⁴ — 4.3 billion times more.

1.6×10³⁰

Addresses Across Big-Three IPv6 Ranges

Combined, the IPv6 ranges published by Google, AWS, and Microsoft Azure alone now span more than 1.6×10³⁰ addresses, per Pixalate's analysis.

+109%

IPv6 Data Center Growth

Between August 2025 and August 2026, the number of IPv6 CIDR ranges published by Google Cloud grew 109%, AWS grew 54%, and Microsoft Azure grew 22%, per Pixalate's analysis.

IPv6 makes address-level blocking impractical. Server-originated traffic from IPv6 infrastructure must be filtered at the range level, using a continuously updated list of data center CIDR ranges.

Coverage: 3,000+ Providers Across North America, Europe & Asia

The full lists span more than 3,000 hosting and cloud providers worldwide. The providers below are a small illustrative sample — not the complete list.

North America Sample

Amazon Web Services
Microsoft Azure
Google Cloud
Meta
Oracle Cloud
IBM Cloud
DigitalOcean
Linode (Akamai)
Vultr
CircleCI
+ many more

Europe Sample

Hetzner
OVHcloud
Scaleway
Leaseweb
Contabo
netcup
+ many more

Asia Sample

Alibaba Cloud
Tencent Cloud
Huawei Cloud
Sakura Internet
Zenlayer
+ many more

New coverage of Alibaba Cloud and Tencent Cloud includes their US-based infrastructure.

Use Cases

DSPs, Agencies & Advertising Platforms

Block data center IP ranges pre-bid across both protocols, protecting advertiser spend from server-originated impressions at scale.

SSPs & Exchanges

Filter data center-originated supply before it reaches demand partners, and document GIVT filtration aligned with MRC processes.

How the Blocklists Are Compiled

Pixalate's data science team curates, validates, and continuously re-evaluates every range in the blocklists.

Multi-Source Inputs

Provider-published IP ranges and externally maintained open-source lists serve as inputs, which Pixalate verifies, deduplicates, and monitors before inclusion.

Pixalate's Own Detection

External inputs sit alongside data center ranges identified and maintained by Pixalate's own detection.

False-Positive Engineering

The blocklists exclude mixed-use IP ranges that carry legitimate consumer traffic — such as Apple iCloud Private Relay egress ranges — consistent with MRC guidance to exclude routing artifacts of legitimate users.

API Access

Programmatic lookup of data center IPs across both protocols.

Request

curl -X 'GET' \
'https://api.pixalate.com/api/v2/blocklists/datacenter?riskType=datacenter&pretty=true' \
-H 'x-api-key: {API_KEY}' \
-H 'accept: application/json'

Response (trimmed)

{
"content": [
{ "rank": 1, "risk": "high", "identifier": "12.34.457.89", "fraudType": "datacenter", "isp": "Google Cloud" },
{ "rank": 2, "risk": "high", "identifier": "98.76.543.21", "fraudType": "datacenter", "isp": "Amazon Web Services" },
{ "rank": 3, "risk": "high", "identifier": "11.22.333.44", "fraudType": "datacenter", "isp": "Microsoft Azure" },
{ "rank": 4, "risk": "high", "identifier": "55.66.777.88", "fraudType": "datacenter", "isp": "Alibaba Cloud" },
{ "rank": 5, "risk": "high", "identifier": "10.20.300.40", "fraudType": "datacenter", "isp": "Tencent Cloud" }
]
}

Integrations:

REST API with JSON responses

Access Methods:

Direct API calls, batch processing, custom integrations

Rate Limits:

Contact sales for volume pricing

Documentation:

developer.pixalate.com

Availability

Both lists are delivered weekly via AWS RTB Fabric, APIs, FTP, and S3.

AWS RTB Fabric

Module for data center pre-bid filtering

API Access

Programmatic access via Pixalate APIs

FTP Data Feeds

Weekly CIDR blocklists delivered via FTP

S3 Bucket

Direct delivery to your AWS S3 bucket

Contact Pixalate to Learn More