LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

217.26.232.0/21

232 residential-proxy exits · 30 days

TNG Stadtnetz GmbH · space held by Stadtwerke Elmshorn

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

Residential-proxy exits

Proxy exits
232
11% of its addresses · 30 days
Spread
8 of 8
/24s with at least one exit
Providers
62
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

7.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.26.238.0/24037
217.26.236.0/24032
217.26.237.0/24032
217.26.239.0/24029
217.26.232.0/24028
217.26.233.0/24026
217.26.234.0/24024
217.26.235.0/24023

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • 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
217.26.232.0/212,048DE-STADTWERKE-ELMSHORN-20110817Stadtwerke Elmshorn (ORG-SE132-RIPE) · DEALLOCATED PANov 13, 2023sicherheitsbeauftragter@swe-net.de
└ 217.26.232.0/24256stadtwerke-elmshorn-217-26-232-0unknownASSIGNED PAJan 15, 2024sicherheitsbeauftragter@swe-net.de
via DE-STADTWERKE-ELMSHORN-20110817
└ 217.26.233.0/24256stadtwerke-elmshorn-217-26-233-0unknownASSIGNED PAJan 15, 2024sicherheitsbeauftragter@swe-net.de
via DE-STADTWERKE-ELMSHORN-20110817
└ 217.26.234.0/24256stadtwerke-elmshorn-217-26-234-0unknownASSIGNED PAJan 15, 2024sicherheitsbeauftragter@swe-net.de
via DE-STADTWERKE-ELMSHORN-20110817
└ 217.26.235.0/24256stadtwerke-elmshorn-217-26-235-0unknownASSIGNED PAJan 15, 2024sicherheitsbeauftragter@swe-net.de
via DE-STADTWERKE-ELMSHORN-20110817
└ 217.26.236.0/24256stadtwerke-elmshorn-217-26-236-0unknownASSIGNED PAJan 15, 2024sicherheitsbeauftragter@swe-net.de
via DE-STADTWERKE-ELMSHORN-20110817
└ 217.26.237.0/24256stadtwerke-elmshorn-217-26-237-0unknownASSIGNED PAJan 15, 2024sicherheitsbeauftragter@swe-net.de
via DE-STADTWERKE-ELMSHORN-20110817
└ 217.26.238.0/24256stadtwerke-elmshorn-217-26-238-0unknownASSIGNED PAJan 15, 2024sicherheitsbeauftragter@swe-net.de
via DE-STADTWERKE-ELMSHORN-20110817
└ 217.26.239.0/24256stadtwerke-elmshorn-217-26-239-0unknownASSIGNED PAJan 15, 2024sicherheitsbeauftragter@swe-net.de
via DE-STADTWERKE-ELMSHORN-20110817

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2024
Current origin since
Jan 2024 · 2.8 yr
Origin networks
1