Data as of Nov 17, 2026

86.103.66.0/23

41 residential-proxy exits · 30 days

TNG Stadtnetz GmbH

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

Residential-proxy exits

Proxy exits
41
8.0% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
33
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

1.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
86.103.67.0/24024
86.103.66.0/24018

Proxy providers listing exits

  • 2Extract
  • AETHYN_ELITE
  • AnyIP
  • BirdProxies
  • BlurPath
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GSocks
  • IPPeak
  • IPRoyal
  • Infatica
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Proxiware
  • ProxyEmpire
  • ProxyWing
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.103.0.0/1665,536DE-TNGSTADTNETZ-20050602TNG Stadtnetz GmbH (ORG-TSG19-RIPE) · DEALLOCATED PAJun 2, 2005abuse@tng.de
└ 86.103.66.0/23512DYNAMIC-DIALUP-POOLunknownASSIGNED PAJun 7, 2023abuse@tng.de
via DE-TNGSTADTNETZ-20050602

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 86.103.0.0/16

86.103.0.0/16

Routing history

Pattern
Stable
First seen
Jun 2005
Current origin since
Jun 2005 · 21 yr
Origin networks
1