Data as of Nov 16, 2026

185.160.40.0/22

Anonymizer · Datacenter proxy

GTT Communications Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Datacenter proxy
IPv4 market

Path

1 · Holder
record created Jul 20, 2016
2 · Leased from
its owner, directly
3 · Announced by
AS3257 GTT Communications Inc.
since Aug 2016 · 10.3 yr ago
4 · Use
Proxy providersnamed Oxylabs
Datacenter proxy

Operators, sellers and brokers

Proxy providers

NameParentIn 185.160.40.0/22/24s
OxylabsTesonet
1,024100%
4
Leased from

Owners leasing their own space

NameIn 185.160.40.0/22/24s
GTT Communications Inc.
1,024100%
4

Lineage

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

185.160.40.0/22

From the registry to its use

  1. Jul 20, 2016
    Registry record
    GTT Communications Inc.
    ALLOCATED PA
    185.160.40.0/22
  2. Aug 15, 2016– today
    Announced
    AS3257 GTT Communications Inc.
    Internet provider
  3. today
    Used
    Oxylabs
    Proxy seller

Announcements

More specific

Announcements inside

PrefixOriginTypeOperatorHolderRPKI
185.160.40.0/23
since Nov 7, 2026
AS212238Datacenter proxyProxy providersoperated by OxylabsGTT Communications Inc.
via Code200 UAB
185.160.42.0/23
since Nov 14, 2026
AS212238Datacenter proxyProxy providersoperated by OxylabsGTT Communications Inc.
via Code200 UAB

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.160.40.0/221,024US-GTTCOMMUNICATIONS-20160720GTT Communications Inc. (ORG-GCI2-RIPE) · USALLOCATED PAJul 20, 2016abuse@gtt.net
└ 185.160.40.0/23512CODE200-20261029-GTTCode200 UABSUB-ALLOCATED PAOct 30, 2026abuse@gtt.net
via US-GTTCOMMUNICATIONS-20160720
└ 185.160.42.0/23512CODE200-20261029-GTTCode200 UABSUB-ALLOCATED PAOct 30, 2026abuse@gtt.net
via US-GTTCOMMUNICATIONS-20160720

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
Aug 2016
Current origin since
Aug 2016 · 10 yr
Origin networks
1