Data as of Nov 10, 2026

83.136.80.0/21

9 anonymizer addresses · 0.44% · VPN10 residential-proxy exits · 30 days

Wiit AG

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
>99% of it

Residential-proxy exits

Proxy exits
10
0.49% of its addresses · 30 days
Spread
2 of 8
/24s with at least one exit
Providers
36
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

437 observations
  • VPN · anonymizer
  • Hosting

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.136.82.0/2409
83.136.84.0/2401

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Byteful
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
IPv4 market

Path

1 · Holder
record created Nov 4, 2020
2 · Leased from
not leased
3 · Announced by
AS24961 Wiit AG
since Oct 2010 · 16.1 yr ago
4 · Use
VPN servicesnamed CyberGhost
Hosting

Operators, sellers and brokers

VPN services

NameParentIn 83.136.80.0/21/24s
CyberGhostKape Technologies
90.44%
1

Lineage

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

83.136.80.0/21

From the registry to its use

  1. May 9, 2005– Sep 22, 2010
    Announced
    AS31010 Dennis Thomas
    Business
  2. Jan 18, 2008
    Route object
    AS24961 Wiit AG
    RIPE route object for AS24961 Wiit AG, maintainer MYLOC-MNT
  3. Oct 1, 2010– today
    Announced
    AS24961 Wiit AG
    Hosting
  4. Nov 4, 2020
    Registry record
    Wiit AG
    ALLOCATED PA
    83.136.80.0/21
  5. today
    Used
    CyberGhost
    VPN

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
83.136.80.0/212,048DE-MYLOC-DUS-20040203Wiit AG (ORG-MMIA3-RIPE) · DEALLOCATED PANov 4, 2020abuse@myloc.de
└ 83.136.80.44/304DE-MYLOC-BECHTLEunknownASSIGNED PAOct 28, 2019abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.80.224/2732DE-MYLOC-INFRA1myLoc Infrastructure NetworksASSIGNED PAApr 8, 2005abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.82.0/2664DE-MYLOC-RICHPORTALrichportal GmbHASSIGNED PAFeb 27, 2004abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.82.128/2732DE-MYLOC-MEHRWERTmehrwert.NETASSIGNED PAMay 14, 2004abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.82.160/2732DE-MYLOC-RSNrising systems networks GmbHASSIGNED PAMay 14, 2004abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.82.192/2732DE-MYLOC-TRIONTriOn IT GmbHASSIGNED PAOct 13, 2004abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.84.0/2664DE-MYLOC-BMAGBMAG ServicesASSIGNED PAMay 28, 2004abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.84.128/2732DE-MYLOC-IMAGEARTSImage Arts GmbHASSIGNED PAOct 13, 2004abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.84.160/2732DE-MYLOC-NETDATANetdata Limited NetworkASSIGNED PAApr 7, 2005abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.84.240/2816DE-MYLOC-MANAGED-1myLoc Managed Server #1ASSIGNED PANov 17, 2004abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.86.0/24256MYLOC-DE-DUS2-DEDICATEDdedicated Server by http://www.webtropia.comASSIGNED PAJun 9, 2012abuse@myloc.de
via DE-MYLOC-DUS-20040203
└ 83.136.87.0/24256DE-MYLOC-FCNETFutureComm, Daniel LaffienASSIGNED PANov 8, 2004abuse@myloc.de
via DE-MYLOC-DUS-20040203

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

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

2,048 addresses
TypeAddressesShareRanges
Hosting2,039>99%6
VPNanonymizer90.44%9

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Oct 2010 · 16 yr
Origin networks
2
Last change of origin
Oct 2010
Recorded history

History

Handoffs
1