Data as of Nov 17, 2026

212.82.48.0/20

17 residential-proxy exits · 30 days

VSE NET GmbH

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

Residential-proxy exits

Proxy exits
17
0.42% of its addresses · 30 days
Spread
6 of 16
/24s with at least one exit
Providers
27
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2.1K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 9HTTP
  • AETHYN_ELITE
  • AnyIP
  • BottingTools
  • Byteful
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • IPFly
  • KocerRoxy
  • LemonBright
  • NodeMaven
  • NovaProxy
  • Novada
  • Proxies.fo
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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
212.82.48.0/204,096DE-SAARGATE-990607VSE NET GmbH (ORG-SGFM1-RIPE) · DEALLOCATED PAMay 9, 2016abuse@vsenet.de
└ 212.82.56.0/24256FTTX-BUSINESS-NETunknownASSIGNED PAMar 28, 2018abuse@vsenet.de
via DE-SAARGATE-990607
└ 212.82.57.0/24256DSL-DU-NETVSE NET GmbHASSIGNED PAMar 28, 2018abuse@vsenet.de
via DE-SAARGATE-990607
└ 212.82.58.0/24256FTTX-BUSINESS-NETVSE NET GmbHASSIGNED PAMar 28, 2018abuse@vsenet.de
via DE-SAARGATE-990607
└ 212.82.59.0/24256DSL-DU-NETunknownASSIGNED PAMar 28, 2018abuse@vsenet.de
via DE-SAARGATE-990607
└ 212.82.60.0/24256FTTX-BUSINESS-NETunknownASSIGNED PAMar 8, 2022abuse@vsenet.de
via DE-SAARGATE-990607
└ 212.82.61.0/24256FTTX-BUSINESS-NETVSE NET GmbHASSIGNED PADec 9, 2020abuse@vsenet.de
via DE-SAARGATE-990607
└ 212.82.62.0/24256FTTX-BUSINESS-NETVSE NET GmbHASSIGNED PAApr 14, 2020abuse@vsenet.de
via DE-SAARGATE-990607
└ 212.82.63.0/24256FTTX-BUSINESS-NETVSE NET GmbHASSIGNED PAApr 11, 2018abuse@vsenet.de
via DE-SAARGATE-990607

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