Data as of Nov 22, 2026

212.37.171.0/24

5 residential-proxy exits · 30 days

RFT Kabel Brandenburg GmbH

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
2
40% of its exits
Providers
32
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

5.6K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • AnyIP
  • BirdProxies
  • Byteful
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.37.160.0/19
since Dec 2008
AS35205Residential338
9 always on
RFT Kabel Brandenburg GmbH

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.37.160.0/198,192DE-BRANDENBURG-RFT-20080623RFT Kabel Brandenburg GmbH (ORG-RRBG1-RIPE) · DEALLOCATED PAJun 23, 2008abuse_ripe@rftkabel.de
└ 212.37.168.0/212,048RFTONLINE-NET2RFT Docsis Customer Network 2ASSIGNED PAJun 15, 2020abuse_ripe@rftkabel.de
via DE-BRANDENBURG-RFT-20080623

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

Covering aggregate above, the prefix's own history below

212.37.160.0/20

Routing history

Pattern
Stable
First seen
Aug 2008
Current origin since
Oct 2018 · 8.1 yr
Origin networks
1