Data as of Nov 11, 2026

185.63.124.0/22

4 residential-proxy exits · 30 days

Epcan GmbH

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
24
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.63.125.0/2412
185.63.124.0/2401
185.63.126.0/2401

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • Infatica
  • Kookey
  • LemonBright
  • MangoProxy
  • NovaProxy
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • ThunderProxy
  • VantageProxies

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.63.124.0/221,024DE-EPCAN-20140710Epcan GmbH (ORG-EG43-RIPE) · DEALLOCATED PAJul 10, 2014abuse@epcan.de
└ 185.63.124.0/24256EPCRZNET2124RZ Network 2124ASSIGNED PAAug 23, 2014abuse@epcan.de
via DE-EPCAN-20140710
└ 185.63.125.0/24256EPCDSLNET125unknownASSIGNED PAJan 5, 2017abuse@epcan.de
via DE-EPCAN-20140710
└ 185.63.126.0/24256EPCDSLNET126DSL NetworkASSIGNED PAFeb 11, 2015abuse@epcan.de
via DE-EPCAN-20140710
└ 185.63.127.0/24256EPCDSLNET127unknownASSIGNED PAJan 5, 2017abuse@epcan.de
via DE-EPCAN-20140710

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
Sep 2014
Current origin since
Sep 2014 · 12 yr
Origin networks
1