Data as of Nov 13, 2026

185.147.32.0/24

Anonymizer · Datacenter proxy

UAB code200 · space held by Zappie Host LLC

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

Path

1 · Holder
record created Feb 25, 2019
2 · Leased from
its owner, directly
3 · Announced by
AS203061 UAB code200
since Jun 2017 · 9.4 yr ago
4 · Use
Proxy providersnamed Oxylabs
Datacenter proxy

Operators, sellers and brokers

Proxy providers

NameParentIn 185.147.32.0/24/24s
OxylabsTesonet
256100%
1
Leased from

Owners leasing their own space

NameIn 185.147.32.0/24/24s
Zappie Host LLC
256100%
1

Lineage

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

185.147.32.0/24

From the registry to its use

  1. Apr 5, 2016– Jun 1, 2016
    Announced
    AS62240 Clouvider Limited
    Hosting
  2. Jun 15, 2016– Jun 27, 2016
    Announced
    AS19437 Secured Servers LLC
    Hosting
  3. Sep 8, 2016– Apr 23, 2017
    Announced
    AS36351 IBM Cloud
    Hosting
  4. Apr 24, 2017– Jun 22, 2017
    Announced
    AS40676 Psychz Networks
    Hosting
  5. Jun 23, 2017– today
    Announced
    AS203061 UAB code200
    Hosting
  6. Jun 26, 2017
    Route object
    AS203061 UAB code200
    RIPE route object for AS203061 UAB code200, maintainer LT-IT-PROXIMUS-1-MNT
  7. Feb 25, 2019
    Registry record
    Zappie Host LLC
    ALLOCATED PA
    185.147.32.0/22
  8. Jan 10, 2024
    Assigned
    Customer Prefix
    ASSIGNED PA
    185.147.32.0/24
  9. today
    Used
    Oxylabs
    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
185.147.32.0/221,024US-ZAPPIE-20160412Zappie Host LLC (ORG-ZHL2-RIPE) · USALLOCATED PAFeb 25, 2019abuse@zappiehost.com
└ 185.147.32.0/24256CUST-PREFIXCustomer PrefixASSIGNED PAJan 10, 2024abuse@zappiehost.com
via US-ZAPPIE-20160412

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
Apr 2016
Current origin since
Jun 2017 · 9.4 yr
Origin networks
5
Last change of origin
Jun 2017
Recorded history

History

Handoffs
4