> 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.

# Changelog

## October 14, 2026

## Fraud API v3 adds risk type codes

Fraud API v3.0.0 returns a `riskTypes` field alongside `probability`: the four-digit codes that explain why an IP address, device ID or user agent is flagged. Codes follow the format class, category, type, so you can block at any level: all SIVT (`2xxx`), one category (`25xx`) or a single type (`2502`), alone or together with a probability threshold.

To move to v3, change the base URL from `https://fraud-api.pixalate.com/api/v2` to `https://fraud-api.pixalate.com/api/v3` and read `riskTypes` from the response. v2 remains available as a legacy API. See [Migrate from v2 to v3](/apis/fraud-api-v2-to-v3), [Risk types and codes](/apis/fraud-api-risk-types) and [IVT Taxonomy 2.0](/trust/ivt-taxonomy).

## September 23, 2026

## High Risk Mobile Apps 1.0 deprecated

High Risk Mobile Apps 1.0 was deprecated on September 23, 2026. Use [High Risk Mobile Apps 2.0](/data-feeds/high-risk-mobile-apps) instead, and contact your Pixalate account manager if you still need to move over.

## August 28, 2026

## New Data Center IPv6 feed and wider IPv4 coverage

A new, separate **Data Center IPv6 feed** covers IPv6 ranges across 66 hosting, cloud and data center providers. The existing Data Center Data Intelligence feed (IPv4) gained more than 15,000 IPv4 ranges from 13 more operators. Existing IPv4 integrations need no changes: naming, schema and delivery are the same.

See [Data center feeds](/data-feeds/data-center).

## CTV device ID feed now updates hourly

The Connected TV Device ID feed now refreshes every hour, up from twice a day, and detection prioritizes device IDs with demonstrated high-impact IVT. The file naming convention, schema and delivery method are unchanged. If you already poll hourly, no action is needed.

See [CTV device ID feed](/data-feeds/ctv-device-ids).

## August 20, 2026

## Two new risk types in High Risk Mobile Apps 2.0

High Risk Mobile Apps 2.0 Standard and Enterprise now include two more risk types:

| Risk type | Code     | Description                                                                                                                                             |
| --------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| New Apps  | `newApp` | Apps published within the past six months that haven't yet built the reputation needed to be fully evaluated. This flag isn't based on invalid traffic. |
| VPN Apps  | `vpnApp` | Apps used to hide the device's IP address and real location.                                                                                            |

Expect the lists to grow by about 37%. That reflects the wider coverage, not a change in your traffic quality. If you filter by risk type, make sure your ingestion and blocking rules handle the two new codes. In the Standard version, apps matching more than one risk type show as `various`; in Enterprise, every applicable type is listed.

See [High Risk Mobile Apps 2.0](/data-feeds/high-risk-mobile-apps).

## March 11, 2026

## High Risk CTV Apps 2.0 Standard and Enterprise (beta)

High Risk CTV Apps 2.0 Standard and Enterprise (beta) launched: Connected TV app block lists that identify known dangerous and fraudulent apps across nine CTV operating systems (Android, FireOS, Linux, Roku, Samsung, Sony, tvOS, LG webOS and Windows). Each app is included based on defined thresholds, with transparent risk reason codes.

See [High Risk CTV Apps 2.0](/data-feeds/high-risk-ctv-apps).

## February 5, 2026

## High Risk Mobile Apps 2.0 Standard and Enterprise (beta)

High Risk Mobile Apps 2.0 Standard and Enterprise (beta) launched.

In Analytics, impressions from apps on the 2.0 lists are no longer classified under the `highRiskApp` IVT type, so you may see lower reported IVT rates. Two new data points show how much of your traffic comes from listed apps: **Traffic from High Risk Apps (%)** and, in app-specific reports, **High Risk App (Yes/No)**.

See [High Risk Mobile Apps 2.0](/data-feeds/high-risk-mobile-apps).

## December 2, 2025

## Mobile device ID block list now updates hourly

The Mobile Device ID block list now refreshes every hour, up from twice a day. Detection now prioritizes device IDs with demonstrated high-impact IVT, and the file is smaller and faster to ingest.

The file naming convention and schema are unchanged. See [Mobile device ID feed](/data-feeds/mobile-device-ids).

## November 17, 2025

## IPv4 block list now updates hourly

The IPv4 block list now refreshes every hour, up from twice a day, so newly identified high-risk IP addresses can be blocked within hours rather than half a day. Detection now prioritizes IP addresses with demonstrated high-impact invalid traffic (IVT), and the file is smaller and faster to ingest.

The file naming convention and schema are unchanged. See [IP block lists](/data-feeds/ip-block-lists).