Data as of Nov 21, 2026

165.217.100.0/22

Anonymizer · Datacenter proxy

NetActuate, Inc · space held by truview LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Datacenter proxy
Risk
85 / 100 · Critical
IPv4 market

Path

1 · Holder
record created Dec 8, 2025 · reallocated to a party the registry does not name Apr 30, 2026
2 · Leased from
not leased
3 · Announced by
AS63911 NetActuate, Inc
since Mar 2026 · 8 mo ago
4 · Use
Proxy providersnamed Bright Data
Datacenter proxy

Operators, sellers and brokers

Proxy providers

NameParentIn 165.217.100.0/22/24s
Bright Data
1,024100%
4

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

165.217.100.0/22

From the registry to its use

  1. Dec 8, 2025
    Registry record
    truview LLC
    ALLOCATED PA
    165.217.96.0/20
  2. Mar 19, 2026
    Route object
    AS63911 NetActuate, Inc
    RADB route object for AS63911 NetActuate, Inc, maintainer MAINT-AS36236
  3. Mar 20, 2026– today
    Announced
    AS63911 NetActuate, Inc
    Hosting
  4. today
    Used
    Bright Data
    Proxy seller

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
165.217.96.0/204,096US-TRUVIEW-19930907truview LLC (ORG-TL694-RIPE) · USALLOCATED PADec 8, 2025truview.abuse@gmail.com
└ 165.217.100.0/221,024GB-TRUVIEW-19930907unknownSUB-ALLOCATED PAApr 30, 2026truview.abuse@gmail.com
via US-TRUVIEW-19930907

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2026
Current origin since
Mar 2026 · 8 mo
Origin networks
1