Data as of Nov 12, 2026

85.136.220.0/22

Anonymizer · Datacenter proxy

NetActuate, Inc · space held by cleardocks LLC

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

Path

1 · Holder
record created Feb 4, 2026 · 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 85.136.220.0/22/24s
Bright Data
1,024100%
4

Lineage

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

85.136.220.0/22

From the registry to its use

  1. Feb 4, 2026
    Registry record
    cleardocks LLC
    ALLOCATED PA
    85.136.212.0 - 85.137.15.255
  2. Mar 19, 2026
    Route object
    AS63911 NetActuate, Inc
    RADB route object for AS63911 NetActuate, Inc, maintainer MAINT-AS36236
  3. Mar 20, 2026– Nov 11, 2026
    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
85.136.212.0 - 85.137.15.25515,360US-CLEARDOCKS-20041103cleardocks LLC (ORG-CL623-RIPE) · USALLOCATED PAFeb 4, 2026cleardocks.abuse@gmail.com
└ 85.136.220.0/221,024GB-CLEARDOCKS-20041103unknownSUB-ALLOCATED PAApr 30, 2026cleardocks.abuse@gmail.com
via US-CLEARDOCKS-20041103

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