Data as of Nov 20, 2026

86.103.128.0/24

4 residential-proxy exits · 30 days

TNG Stadtnetz GmbH

Announcement
RPKI valid
Announced by
Type
Business
72% of it

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
32
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.3K observations
  • Residential
  • Business

Proxy providers listing exits

  • 2Extract
  • AETHYN_ELITE
  • AnyIP
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FLEETPROXY
  • FlexyProxies
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • 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
86.103.0.0/1665,536DE-TNGSTADTNETZ-20050602TNG Stadtnetz GmbH (ORG-TSG19-RIPE) · DEALLOCATED PAJun 2, 2005abuse@tng.de
└ 86.103.128.0/298Flyconnect-MedusaNetwork of FlyconnectASSIGNED PAFeb 28, 2006abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.8/304Paulsen-Ivers-NETunknownASSIGNED PASep 2, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.12/304AVT-SW-NETunknownASSIGNED PASep 26, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.16/2816Bogdol-NETNetwork of bogdolASSIGNED PAFeb 28, 2006abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.32/2732WTSH-NetzNetwork of WTSHASSIGNED PAFeb 28, 2006abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.68/304PSD-NuernbergunknownASSIGNED PAAug 10, 2023abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.80/304GYMNASIUM-SOLTAU-NETunknownASSIGNED PAFeb 21, 2023abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.88/298Hohenhausen-NETunknownASSIGNED PAAug 16, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.96/2732Flyconnect-NET2 Network of FlyconnectASSIGNED PAFeb 28, 2006abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.132/304Gemeinde-SPO-NETunknownASSIGNED PADec 14, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.144/298Avacad-NETNetwork of AvacadASSIGNED PAJun 7, 2006abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.153/321Duennemeile-staticunknownASSIGNED PADec 14, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.156/312Nordsee-Internat-SPOunknownASSIGNED PADec 14, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.176/298PSD-Bank-NETunknownASSIGNED PAOct 14, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.184/312PSD-Bank-NETunknownASSIGNED PAOct 14, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.192/298STIFTUNG-NATURSHUTZ-NETunknownASSIGNED PAJan 12, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.200/298STIFTUNG-NATURSCHUTZ-NET-2unknownASSIGNED PAJan 12, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.208/321OT-Kiel-NiemannswegunknownASSIGNED PAMay 12, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.209/321Weiss-UMunknownASSIGNED PAMay 12, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.210/321Capital-ConceptunknownASSIGNED PAMay 12, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.211/321PlanIT-BuechelunknownASSIGNED PAMay 12, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.216/312Static-Dialup-MikatelunknownASSIGNED PAJun 1, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.218/321PBB-BiogasunknownASSIGNED PAJun 8, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.219/321AWesulsMetallbauSchlossereiunknownASSIGNED PAJun 8, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.220/321KanzleiKerstinSuetelunknownASSIGNED PAJun 8, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.221/321Seniorenzentrum-Kaiser-WilhelmunknownASSIGNED PAJun 21, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.223/321VitadromunknownASSIGNED PAJun 10, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.224/321Itenos-NETunknownASSIGNED PAJun 21, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.225/321LBS-WellseedammunknownASSIGNED PAJun 21, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.226/321Hamm-Kliniken-NETunknownASSIGNED PAJul 11, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.227/321Favre-Wind-NETunknownASSIGNED PAJul 11, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.228/321Meinicke-NETunknownASSIGNED PAJul 11, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.230/321Autodienst-Menzel-StaticunknownASSIGNED PAJul 13, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.234/321Static-Dialup-MikatelunknownASSIGNED PAAug 15, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.238/321SOLconsult-NETunknownASSIGNED PASep 2, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.240/304BEUTLER-NETunknownASSIGNED PAJun 30, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.244/304Regionalverkehre-Start-NETunknownASSIGNED PASep 2, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.128.248/298Denker-Wulf-NETunknownASSIGNED PAAug 29, 2022abuse@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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business18572%36
Residential7128%14

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