Data as of Nov 16, 2026

94.199.208.0/22

32 residential-proxy exits · 30 days

KurpfalzTEL GmbH

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

Residential-proxy exits

Proxy exits
32
3.1% of its addresses · 30 days
Always-on exits
1
3.1% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
58
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

7.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.199.209.0/24111
94.199.208.0/24013
94.199.210.0/2408

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GhostConnect
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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
94.199.208.0/221,024DE-KURPFALZTEL-20081119KurpfalzTEL GmbH (ORG-KGFT1-RIPE) · DEALLOCATED PAAug 23, 2017abuse@kurpfalztel.net
└ 94.199.208.0/23512KPFTEL-POOL-5KurpfalzTEL customer poolASSIGNED PAOct 7, 2026abuse@kurpfalztel.net
via DE-KURPFALZTEL-20081119
└ 94.199.210.0/23512KPFTEL-POOL-6unknownASSIGNED PAOct 7, 2026abuse@kurpfalztel.net
via DE-KURPFALZTEL-20081119

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
Aug 2017
Current origin since
Oct 2019 · 7.1 yr
Origin networks
2
Last change of origin
Oct 2019
Recorded history

History

Handoffs
1