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

86.103.0.0/16

5,280 residential-proxy exits · 30 days

TNG Stadtnetz GmbH

Announcement
this exact prefix
RPKI valid
Announced by
AS13101
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
5,280
8.1% of its addresses · 30 days
Always-on exits
2
0.04% of its exits
Spread
88 of 256
/24s with at least one exit
Providers
128
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

535K observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
86.103.51.0/241253
86.103.43.0/24130
86.103.48.0/240254
86.103.50.0/240254
86.103.49.0/240251
86.103.33.0/240251
86.103.34.0/240250
86.103.32.0/240249
86.103.35.0/240246
86.103.58.0/240244
86.103.56.0/240244
86.103.59.0/240239
86.103.57.0/240238
86.103.26.0/240219
86.103.25.0/240214
86.103.24.0/240213
86.103.27.0/240212
86.103.55.0/240165
86.103.53.0/240164
86.103.54.0/240153
86.103.52.0/240140
86.103.41.0/24038
86.103.253.0/24035
86.103.46.0/24033

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PYPROXY
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • QUANTICDATA
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • TrustProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • 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
86.103.0.0/1665,536DE-TNGSTADTNETZ-20050602TNG Stadtnetz GmbH (ORG-TSG19-RIPE) · DEALLOCATED PAJun 2, 2005abuse@tng.de
└ 86.103.16.0/23512STADTWERKE-BARMSTEDT-NETNetzwerk der Stadtwerke BarmstedtASSIGNED PANov 4, 2015abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.23.0/24256STADTWERKE-BARMSTEDT-NETNetzwerk der Stadtwerke BarmstedtASSIGNED PANov 4, 2015abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.28.0/24256STADTWERKE-BARMSTEDT-NETNetzwerk der Stadtwerke BarmstedtASSIGNED PAJan 22, 2020abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.29.0/24256STADTWERKE-BARMSTEDT-NETNetzwerk der Stadtwerke BarmstedtASSIGNED PAJan 22, 2020abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.40.0/212,048Dynamic-Dialup-PoolunknownASSIGNED PAApr 28, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.48.0/221,024Dynamic-Dialup-PoolunknownASSIGNED PAJul 22, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.52.0/221,024Dynamic-Dialup-PoolunknownASSIGNED PAJul 25, 2022abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.65.0/24256DYNAMIC-DIALUP-POOLunknownASSIGNED PAJun 7, 2023abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.66.0/23512DYNAMIC-DIALUP-POOLunknownASSIGNED PAJun 7, 2023abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 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
└ 86.103.130.0/298ETRIBES-KIEL-NETNetwork of eTribesASSIGNED PADec 20, 2012abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.130.64/2664TRANSFAIR-NETWORKNetwork of Transfair GmbHASSIGNED PAJul 28, 2014abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.130.128/25128TNGDYNAMIC DIAL UP POOL Broadband CustomersASSIGNED PAJun 3, 2014abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.132.0/221,024VBB-DIALUP-POOLnetwork of Versorgungsbetriebe Bordesholm GmbHASSIGNED PAJun 24, 2014abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.136.0/24256VBB-DIALUP-POOLnetwork of Versorgungsbetriebe Bordesholm GmbHASSIGNED PAFeb 13, 2015abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.137.0/24256VBB-DIALUP-POOLnetwork of Versorgungsbetriebe Bordesholm GmbHASSIGNED PAJan 19, 2016abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.138.0/24256VBB-DIALUP-POOLunknownASSIGNED PAFeb 5, 2026abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.139.0/24256VBB-DIALUP-POOLnetwork of Versorgungsbetriebe Bordesholm GmbHASSIGNED PASep 18, 2019abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.140.0/23512VBB-DIALUP-POOLnetwork of Versorgungsbetriebe Bordesholm GmbHASSIGNED PAFeb 5, 2026abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.142.0/23512DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAMay 22, 2018abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.144.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.145.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.146.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.147.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.148.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.149.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.150.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.151.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.152.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.153.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.154.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.155.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.156.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.157.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.158.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.159.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.160.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.161.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.162.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.163.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.164.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.165.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.166.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.167.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.168.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.169.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.170.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.171.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.172.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.173.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.174.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.175.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.176.0/204,096TNGDYNAMIC DIAL UP POOL Broadband CustomersASSIGNED PAJan 9, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.192.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.193.0/24256TRANSFER-NETWORKS-KELunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.194.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.195.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.196.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.197.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.198.0/24256VBB-DIALUP-POOLnetwork of Versorgungsbetriebe Bordesholm GmbHASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.199.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.200.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.201.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.202.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.203.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.204.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.205.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.206.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.207.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.208.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.209.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.210.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.211.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.212.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.213.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.214.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.215.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.216.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.217.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.218.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.219.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.220.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.221.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.222.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.223.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.224.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.225.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.226.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.227.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.228.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.229.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.230.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.231.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.232.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.233.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.234.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.235.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.236.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.237.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.238.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.239.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.240.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.241.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.242.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.243.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.244.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.245.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.246.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.247.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.248.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.249.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.250.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.251.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.252.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.253.0/24256DYNAMIC-IP-ADDRESS-SPACEunknownASSIGNED PAFeb 20, 2017abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.254.0/304rDNS-ServerunknownASSIGNED PASep 21, 2021abuse@tng.de
via DE-TNGSTADTNETZ-20050602
└ 86.103.255.0/24256TRANSFER-NETWORKS-KELunknownASSIGNED PAFeb 20, 2017abuse@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

65,536 addresses
TypeAddressesShareRanges
Residential65,275>99%19
Business2610.40%39

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

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