Data as of Nov 12, 2026

37.60.1.0/24

8 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
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
34
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.9K observations

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • AnyIP
  • BirdProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FloppyData
  • GSocks
  • GeekProxy
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PSBProxy
  • PrivateByte
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VProxy
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.60.0.0/21
since Mar 2012
AS198570Residential90
1 always on
Stadtnetz Bamberg Gesellschaft fuer Telekommunikation mbH

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.60.0.0/212,048DE-STADTNETZ-BAMBERG-20120117Stadtnetz Bamberg Gesellschaft fuer Telekommunikation mbH (ORG-SBGF1-RIPE) · DEALLOCATED PAJan 17, 2012abuse@stadtnetz-bamberg.de
└ 37.60.0.0/23512STNB-NETFTTx Customer PPPoE Dynamic Pool 1ASSIGNED PAMar 5, 2012abuse@stadtnetz-bamberg.de
via DE-STADTNETZ-BAMBERG-20120117

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

37.60.0.0/23

Routing history

Pattern
Stable
First seen
Feb 2021
Current origin since
Feb 2021 · 5.7 yr
Origin networks
1