Data as of Nov 13, 2026

147.142.0.0/16

455 residential-proxy exits · 30 days

Universitaet Stuttgart · space held by Universitaet Heidelberg

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

Residential-proxy exits

Proxy exits
455
0.69% of its addresses · 30 days
Spread
93 of 256
/24s with at least one exit
Providers
55
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

3.8K observations

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FROXY
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • GhostConnect
  • HPROXY
  • HideProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYFALL
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • 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
147.142.0.0/1665,536UNI-HEIDELBERGUniversitaet Heidelberg (ORG-UH5-RIPE) · DELEGACY—abuse@uni-heidelberg.de
└ 147.142.50.0/24256BELWUE-SCHULENUniversitaet HeidelbergLEGACYSep 26, 2003abuse@uni-heidelberg.de
via UNI-HEIDELBERG
└ 147.142.150.0 - 147.142.155.2551,536BELWUE-SCHULENUniversitaet HeidelbergLEGACYDec 6, 2002abuse@uni-heidelberg.de
via UNI-HEIDELBERG
└ 147.142.209.0/24256DZFA-HEIDELBERGDeutsches Zentrum fuer Alternsforschung (DZFA)LEGACYJun 12, 2003abuse@uni-heidelberg.de
via UNI-HEIDELBERG

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