Data as of Nov 11, 2026

178.19.86.0/24

27 residential-proxy exits · 30 days

SeWiKom GmbH

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

Residential-proxy exits

Proxy exits
27
11% of its addresses · 30 days
Providers
49
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

452 observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonix
  • GloryCloud
  • HideProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.19.80.0/204,096DE-SEWIKOM-20100507SeWiKom GmbH (ORG-SG107-RIPE) · DEALLOCATED PAMay 7, 2010abuse@sewikom.de
└ 178.19.80.0 - 178.19.95.2394,080sewikom_GmbHunknownASSIGNED PAMar 21, 2018abuse@sewikom.de
via DE-SEWIKOM-20100507

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 178.19.80.0/20

178.19.80.0/20

Routing history

Pattern
Stable
First seen
May 2010
Current origin since
Jun 2021 · 5.4 yr
Origin networks
3
Last change of origin
Jun 2021
Recorded history

History

Handoffs
2