Data as of Nov 13, 2026

80.208.211.0/24

35 residential-proxy exits · 30 days

Stadtnetz Bamberg Gesellschaft fuer Telekommunikation mbH

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

Residential-proxy exits

Proxy exits
35
14% of its addresses · 30 days
Providers
55
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.9K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.208.208.0/212,048DE-STADTNETZ-BAMBERG-20011212Stadtnetz Bamberg Gesellschaft fuer Telekommunikation mbH (ORG-SBGF1-RIPE) · DEALLOCATED PAMay 9, 2017abuse@stadtnetz-bamberg.de
└ 80.208.208.0/221,024STNB-NETFTTx Customer PPPoE Dynamic Pool 7ASSIGNED PASep 17, 2019abuse@stadtnetz-bamberg.de
via DE-STADTNETZ-BAMBERG-20011212

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 80.208.208.0/21

80.208.208.0/21

Routing history

Pattern
Stable
First seen
Sep 2017
Current origin since
Sep 2017 · 9.2 yr
Origin networks
1