Data as of Nov 12, 2026

158.174.0.0/16

2 anonymizer addresses · <0.01%925 residential-proxy exits · 30 days

Bahnhof AB

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
85% of it

Residential-proxy exits

Proxy exits
925
1.4% of its addresses · 30 days
Always-on exits
60
6.5% of its exits
Spread
159 of 256
/24s with at least one exit
Providers
126
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

227K observations
  • Tor exit · anonymizer
  • Residential
  • Business

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
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • MrScraper
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PacketStream
  • PrivateByte
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyBase
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • TrustProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
2 · Leased from
not leased
3 · Announced by
AS8473 Bahnhof AB
since Jun 2016 · 10.4 yr ago
4 · Use
VPN servicesnamed VPNSecurenamed Tor
Residential

Operators, sellers and brokers

VPN services

NameParentIn 158.174.0.0/16/24s
VPNSecure
1<0.01%
1

Tor

NameParentIn 158.174.0.0/16/24s
TorThe Tor Project
1<0.01%
1

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

158.174.0.0/16

From the registry to its use

  1. May 28, 2016
    Route object
    AS8473 Bahnhof AB
    RIPE route object for AS8473 Bahnhof AB, maintainer BAHNHOF-NCC
  2. Jun 1, 2016– today
    Announced
    AS8473 Bahnhof AB
    Internet provider
  3. today
    Registry record
    Bahnhof AB
    LEGACY
    158.174.0.0/16
  4. today
    Used
    VPNSecure
    VPN
  5. today
    Used
    Tor
    Tor

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
158.174.0.0/1665,536BAHNHOF-AGGREGATEBahnhof AB (ORG-BIA1-RIPE) · SELEGACY—abuse@bahnhof.net
└ 158.174.0.0/2664GENERAL-PRIVATE-NET-A676-1Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.0.64/2732GENERAL-PRIVATE-NET-A684-1Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.0.96/2816GENERAL-PRIVATE-NET-A498-64Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.0.112/298GENERAL-CORPORATE-NET-A400-69Dynamic corporate networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.0.120/298GENERAL-PRIVATE-NET-A682-1Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.0.144/2816GENERAL-PRIVATE-NET-A689-1Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.0.160/2732RID-0000492569unknownLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.0.192/2664RID-0000482854unknownLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.0/2664GENERAL-PRIVATE-NET-A1560-1Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.64/298RID-0000083171unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.72/298RID-0000351662unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.80/304RID-0000432988unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.84/304RID-0000855507unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.88/304RID-0000760127unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.92/312RID-0000328662unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.94/312RID-0000083171unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.96/298RID-0000543550unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.104/298RID-0000341622unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.112/304RID-0000355809unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.116/304RID-0000926067unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.120/298RID-0000450554unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.128/2664GENERAL-PRIVATE-NETDynamic private networkLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.1.192/2664GENERAL-PRIVATE-NET-A498-276Dynamic private networkLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.0/2664GENERAL-CORPORATE-NET-A390-1Dynamic corporate networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.64/2664GENERAL-PRIVATE-NET-A688-1Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.128/304RID-0000510042unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.132/304RID-0000822747unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.136/304RID-0000836139unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.140/304RID-0000821852unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.144/2816GENERAL-PRIVATE-NETDynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.160/298RID-0000448184unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.168/298GENERAL-PRIVATE-NET-A1499-1Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.176/2816GENERAL-PRIVATE-NET-A1499-2Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.192/304RID-0000361242unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.196/304RID-0000815564unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.200/298RID-0000691954unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.232/304RID-0000992797unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.236/304RID-0000314038unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.240/298RID-0000647313unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.248/304RID-0000552482unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.2.252/304RID-0000433585unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.3.0/24256RID-0000165942unknownLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.4.0/2664GENERAL-PRIVATE-NET-A1807-6Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.4.80/304RID-0001047962unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.4.84/304RID-0001044495unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.4.88/304RID-0001020498unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.4.92/304RID-0001047955unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.5.0/2732GENERAL-CORPORATE-NET-A324-4Dynamic corporate networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.5.32/2732GENERAL-CORPORATE-NET-A137-254Dynamic corporate networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.5.64/2816GENERAL-PRIVATE-NET-A498-65Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.5.80/2816RID-0000851015unknownLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.5.96/2732GENERAL-PRIVATE-NET-A400-69Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.5.128/2664RID-0000487193unknownLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.5.192/2816GENERAL-CORPORATE-NET-A499-1Dynamic corporate networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.6.0/24256GENERAL-CORPORATE-NET-A980-2Dynamic corporate networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.7.0/24256RID-0000024651unknownLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.176/304RID-0000147855unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.180/304RID-0000766603unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.184/298RID-0000820477unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.192/2732RID-0000067003unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.224/298RID-0000157061unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.232/304RID-0000593912unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.236/304RID-0000365626unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.240/304RID-0000278768unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.244/304RID-0000817179unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.248/304RID-0000626424unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.8.252/304RID-0000214579unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.9.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.10.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.11.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.12.0/24256GENERAL-PRIVATE-NET-A351-5Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.13.0/24256GENERAL-PRIVATE-NET-A351-6Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.14.0/24256GENERAL-PRIVATE-NET-A357-34Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.15.0/24256GENERAL-PRIVATE-NET-A357-35Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.16.0/24256GENERAL-PRIVATE-NET-A357-36Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.17.0/24256GENERAL-PRIVATE-NET-A357-37Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.18.0/24256GENERAL-PRIVATE-NET-A357-38Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.19.0/24256GENERAL-PRIVATE-NET-A357-39Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.21.192/2732GENERAL-CORPORATE-NET-A137-256Dynamic corporate networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.21.224/304RID-0000440942unknownLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.21.228/304RID-0000124507unknownLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.22.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.23.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.32/2732GENERAL-PRIVATE-NET-A498-70Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.64/2732GENERAL-PRIVATE-NET-A498-71Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.112/2816GENERAL-PRIVATE-NET-A498-72Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.128/2732GENERAL-CORPORATE-NET-A137-257Dynamic corporate networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.208/2816GENERAL-PRIVATE-NET-A498-73Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.224/2816GENERAL-PRIVATE-NET-A498-74Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.240/298RID-0000270289unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.248/304RID-0000533772unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.252/312RID-0000301824unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.24.254/312RID-0000865921unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.25.0/25128GENERAL-PRIVATE-NET-A160-18Dynamic private networkLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.25.128/2664GENERAL-PRIVATE-NET-A498-370Dynamic private networkLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.25.240/304RID-0000977435unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.25.244/304RID-0000977451unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.26.0/24256GENERAL-PRIVATE-NET-A463-25Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.0/298RID-0000707712unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.8/298RID-0000117839unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.16/304RID-0001016781unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.20/304RID-0000780627unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.24/304RID-0000866868unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.28/304RID-0000915222unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.32/2732GENERAL-CORPORATE-NET-A137-258Dynamic corporate networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.64/2732GENERAL-PRIVATE-NET-A317-9Dynamic private networkLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.128/2816RID-0000531972unknownLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.144/298RID-0000020476unknownLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.152/312RID-0000020476unknownLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.154/312RID-0000020476unknownLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.160/298RID-0000017755unknownLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.176/2816RID-0000098021unknownLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.192/2732RID-0000493707unknownLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.27.240/304RID-0000631551unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.28.0/24256GENERAL-PRIVATE-NET-A159-10Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.29.0/24256GENERAL-PRIVATE-NET-A192-7Dynamic private networkLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.30.128/2732RID-0000439302unknownLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.30.208/304RID-0000606255unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.30.212/304RID-0000962634unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.30.240/298RID-0000943279unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.30.248/304RID-0000956913unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.30.252/304RID-0000534026unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.8/304RID-0000586943unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.12/304RID-0000607182unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.16/298RID-0000733102unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.24/304RID-0000556097unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.28/312RID-0000556097unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.30/312RID-0000556097unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.32/304RID-0000556097unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.36/304RID-0000961407unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.40/298RID-0000018959unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.48/2816RID-0000133214unknownLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.64/2664RID-0000123992unknownLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.31.128/25128GENERAL-PRIVATE-NET-A251-22Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.32.0/221,024GENERAL-PRIVATE-NET-A333-5Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.36.0/221,024GENERAL-PRIVATE-NET-A333-7Dynamic private networkLEGACYJun 5, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.32/2732RID-0000016321unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.64/304RID-0000924082unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.68/304RID-0000924082unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.72/304RID-0000924082unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.76/304RID-0000204250unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.80/298RID-0000967157unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.88/304RID-0000976734unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.92/304RID-0000302479unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.96/304RID-0000985102unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.100/312RID-0000433585unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.102/312RID-0000682713unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.104/298RID-0000336140unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.112/298RID-0000424085unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.120/298RID-0000336140unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.160/2732RID-0000512648unknownLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.192/298GENERAL-PRIVATE-NET-A400-70Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.40.208/2816GENERAL-PRIVATE-NET-A400-71Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.41.0/24256GENERAL-PRIVATE-NET-A412-125Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.0/298RID-0000911520unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.8/304RID-0000918214unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.12/304RID-0000626079unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.16/298RID-0000157061unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.24/298RID-0000467553unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.32/304RID-0000916461unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.36/304RID-0000835731unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.40/298RID-0000917844unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.64/304RID-0000441329unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.68/304RID-0000015662unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.72/304RID-0000915387unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.76/304RID-0000327922unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.80/2816RID-0000436428unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.96/298RID-0000918844unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.104/304RID-0000918692unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.108/304RID-0000015716unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.112/298RID-0000768830unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.128/304RID-0000911221unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.132/304RID-0000917330unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.136/304RID-0000465921unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.140/304RID-0000918956unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.144/298RID-0000912921unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.152/304RID-0000917557unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.156/304RID-0000714411unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.160/304RID-0000888471unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.164/304RID-0000299406unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.168/298RID-0000919202unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.176/304RID-0000918020unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.180/304RID-0000299406unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.184/312RID-0000299406unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.186/312RID-0000365765unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.188/304RID-0000914000unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.192/298RID-0000769925unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.200/298RID-0000873710unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.208/298RID-0000442554unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.216/304RID-0000918642unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.220/304RID-0000696675unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.224/304RID-0000838415unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.228/304RID-0000493088unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.232/298RID-0001048521unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.240/298RID-0000878830unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.248/304RID-0000892960unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.42.252/304RID-0000136420unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.43.0/24256GENERAL-PRIVATE-NET-A328-162Dynamic private networkLEGACYSep 14, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.40/304RID-0001017046unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 158.174.44.44/304RID-0001012467unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous1–200 of 1,781 · page 1 of 9Next →

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
Residential55,43885%181
Business10,09615%283
Tor exitanonymizer1<0.01%1
VPNanonymizer1<0.01%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2016
Current origin since
Jun 2016 · 10 yr
Origin networks
1