Data as of Nov 12, 2026
158.174.0.0/16
2 anonymizer addresses · <0.01%925 residential-proxy exits · 30 daysBahnhof AB
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
/24s with the most always-on exits
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
Operators, sellers and brokers
VPN services
| Name | Parent | In 158.174.0.0/16 | /24s |
|---|---|---|---|
| VPNSecure | 1<0.01% | 1 |
Tor
| Name | Parent | In 158.174.0.0/16 | /24s |
|---|---|---|---|
| Tor | The Tor Project | 1<0.01% | 1 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 158.174.0.0/16 | 65,536 | BAHNHOF-AGGREGATE | Bahnhof AB (ORG-BIA1-RIPE) · SE | LEGACY | — | abuse@ |
| └ 158.174.0.0/26 | 64 | GENERAL-PRIVATE-NET-A676-1 | Dynamic private network | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.0.64/27 | 32 | GENERAL-PRIVATE-NET-A684-1 | Dynamic private network | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.0.96/28 | 16 | GENERAL-PRIVATE-NET-A498-64 | Dynamic private network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.0.112/29 | 8 | GENERAL-CORPORATE-NET-A400-69 | Dynamic corporate network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.0.120/29 | 8 | GENERAL-PRIVATE-NET-A682-1 | Dynamic private network | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.0.144/28 | 16 | GENERAL-PRIVATE-NET-A689-1 | Dynamic private network | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.0.160/27 | 32 | RID-0000492569 | unknown | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.0.192/26 | 64 | RID-0000482854 | unknown | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.0/26 | 64 | GENERAL-PRIVATE-NET-A1560-1 | Dynamic private network | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.64/29 | 8 | RID-0000083171 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.72/29 | 8 | RID-0000351662 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.80/30 | 4 | RID-0000432988 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.84/30 | 4 | RID-0000855507 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.88/30 | 4 | RID-0000760127 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.92/31 | 2 | RID-0000328662 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.94/31 | 2 | RID-0000083171 | unknown | LEGACY | Dec 1, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.96/29 | 8 | RID-0000543550 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.104/29 | 8 | RID-0000341622 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.112/30 | 4 | RID-0000355809 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.116/30 | 4 | RID-0000926067 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.120/29 | 8 | RID-0000450554 | unknown | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.128/26 | 64 | GENERAL-PRIVATE-NET | Dynamic private network | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.1.192/26 | 64 | GENERAL-PRIVATE-NET-A498-276 | Dynamic private network | LEGACY | Sep 3, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.0/26 | 64 | GENERAL-CORPORATE-NET-A390-1 | Dynamic corporate network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.64/26 | 64 | GENERAL-PRIVATE-NET-A688-1 | Dynamic private network | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.128/30 | 4 | RID-0000510042 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.132/30 | 4 | RID-0000822747 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.136/30 | 4 | RID-0000836139 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.140/30 | 4 | RID-0000821852 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.144/28 | 16 | GENERAL-PRIVATE-NET | Dynamic private network | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.160/29 | 8 | RID-0000448184 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.168/29 | 8 | GENERAL-PRIVATE-NET-A1499-1 | Dynamic private network | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.176/28 | 16 | GENERAL-PRIVATE-NET-A1499-2 | Dynamic private network | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.192/30 | 4 | RID-0000361242 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.196/30 | 4 | RID-0000815564 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.200/29 | 8 | RID-0000691954 | unknown | LEGACY | Nov 22, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.232/30 | 4 | RID-0000992797 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.236/30 | 4 | RID-0000314038 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.240/29 | 8 | RID-0000647313 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.248/30 | 4 | RID-0000552482 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.2.252/30 | 4 | RID-0000433585 | unknown | LEGACY | May 27, 2021 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.3.0/24 | 256 | RID-0000165942 | unknown | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.4.0/26 | 64 | GENERAL-PRIVATE-NET-A1807-6 | Dynamic private network | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.4.80/30 | 4 | RID-0001047962 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.4.84/30 | 4 | RID-0001044495 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.4.88/30 | 4 | RID-0001020498 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.4.92/30 | 4 | RID-0001047955 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.5.0/27 | 32 | GENERAL-CORPORATE-NET-A324-4 | Dynamic corporate network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.5.32/27 | 32 | GENERAL-CORPORATE-NET-A137-254 | Dynamic corporate network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.5.64/28 | 16 | GENERAL-PRIVATE-NET-A498-65 | Dynamic private network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.5.80/28 | 16 | RID-0000851015 | unknown | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.5.96/27 | 32 | GENERAL-PRIVATE-NET-A400-69 | Dynamic private network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.5.128/26 | 64 | RID-0000487193 | unknown | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.5.192/28 | 16 | GENERAL-CORPORATE-NET-A499-1 | Dynamic corporate network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.6.0/24 | 256 | GENERAL-CORPORATE-NET-A980-2 | Dynamic corporate network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.7.0/24 | 256 | RID-0000024651 | unknown | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.176/30 | 4 | RID-0000147855 | unknown | LEGACY | Dec 21, 2020 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.180/30 | 4 | RID-0000766603 | unknown | LEGACY | Dec 21, 2020 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.184/29 | 8 | RID-0000820477 | unknown | LEGACY | Dec 21, 2020 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.192/27 | 32 | RID-0000067003 | unknown | LEGACY | Dec 21, 2020 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.224/29 | 8 | RID-0000157061 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.232/30 | 4 | RID-0000593912 | unknown | LEGACY | Dec 21, 2020 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.236/30 | 4 | RID-0000365626 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.240/30 | 4 | RID-0000278768 | unknown | LEGACY | Dec 21, 2020 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.244/30 | 4 | RID-0000817179 | unknown | LEGACY | Dec 21, 2020 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.248/30 | 4 | RID-0000626424 | unknown | LEGACY | Dec 21, 2020 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.8.252/30 | 4 | RID-0000214579 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.9.0/24 | 256 | GENERAL-PRIVATE-NET | Dynamic private network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.10.0/24 | 256 | GENERAL-PRIVATE-NET | Dynamic private network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.11.0/24 | 256 | GENERAL-PRIVATE-NET | Dynamic private network | LEGACY | May 11, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.12.0/24 | 256 | GENERAL-PRIVATE-NET-A351-5 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.13.0/24 | 256 | GENERAL-PRIVATE-NET-A351-6 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.14.0/24 | 256 | GENERAL-PRIVATE-NET-A357-34 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.15.0/24 | 256 | GENERAL-PRIVATE-NET-A357-35 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.16.0/24 | 256 | GENERAL-PRIVATE-NET-A357-36 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.17.0/24 | 256 | GENERAL-PRIVATE-NET-A357-37 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.18.0/24 | 256 | GENERAL-PRIVATE-NET-A357-38 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.19.0/24 | 256 | GENERAL-PRIVATE-NET-A357-39 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.21.192/27 | 32 | GENERAL-CORPORATE-NET-A137-256 | Dynamic corporate network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.21.224/30 | 4 | RID-0000440942 | unknown | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.21.228/30 | 4 | RID-0000124507 | unknown | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.22.0/24 | 256 | GENERAL-PRIVATE-NET | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.23.0/24 | 256 | GENERAL-PRIVATE-NET | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.32/27 | 32 | GENERAL-PRIVATE-NET-A498-70 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.64/27 | 32 | GENERAL-PRIVATE-NET-A498-71 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.112/28 | 16 | GENERAL-PRIVATE-NET-A498-72 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.128/27 | 32 | GENERAL-CORPORATE-NET-A137-257 | Dynamic corporate network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.208/28 | 16 | GENERAL-PRIVATE-NET-A498-73 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.224/28 | 16 | GENERAL-PRIVATE-NET-A498-74 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.240/29 | 8 | RID-0000270289 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.248/30 | 4 | RID-0000533772 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.252/31 | 2 | RID-0000301824 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.24.254/31 | 2 | RID-0000865921 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.25.0/25 | 128 | GENERAL-PRIVATE-NET-A160-18 | Dynamic private network | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.25.128/26 | 64 | GENERAL-PRIVATE-NET-A498-370 | Dynamic private network | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.25.240/30 | 4 | RID-0000977435 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.25.244/30 | 4 | RID-0000977451 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.26.0/24 | 256 | GENERAL-PRIVATE-NET-A463-25 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.0/29 | 8 | RID-0000707712 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.8/29 | 8 | RID-0000117839 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.16/30 | 4 | RID-0001016781 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.20/30 | 4 | RID-0000780627 | unknown | LEGACY | Sep 5, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.24/30 | 4 | RID-0000866868 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.28/30 | 4 | RID-0000915222 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.32/27 | 32 | GENERAL-CORPORATE-NET-A137-258 | Dynamic corporate network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.64/27 | 32 | GENERAL-PRIVATE-NET-A317-9 | Dynamic private network | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.128/28 | 16 | RID-0000531972 | unknown | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.144/29 | 8 | RID-0000020476 | unknown | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.152/31 | 2 | RID-0000020476 | unknown | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.154/31 | 2 | RID-0000020476 | unknown | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.160/29 | 8 | RID-0000017755 | unknown | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.176/28 | 16 | RID-0000098021 | unknown | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.192/27 | 32 | RID-0000493707 | unknown | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.27.240/30 | 4 | RID-0000631551 | unknown | LEGACY | Nov 12, 2019 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.28.0/24 | 256 | GENERAL-PRIVATE-NET-A159-10 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.29.0/24 | 256 | GENERAL-PRIVATE-NET-A192-7 | Dynamic private network | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.30.128/27 | 32 | RID-0000439302 | unknown | LEGACY | Jun 12, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.30.208/30 | 4 | RID-0000606255 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.30.212/30 | 4 | RID-0000962634 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.30.240/29 | 8 | RID-0000943279 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.30.248/30 | 4 | RID-0000956913 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.30.252/30 | 4 | RID-0000534026 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.8/30 | 4 | RID-0000586943 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.12/30 | 4 | RID-0000607182 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.16/29 | 8 | RID-0000733102 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.24/30 | 4 | RID-0000556097 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.28/31 | 2 | RID-0000556097 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.30/31 | 2 | RID-0000556097 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.32/30 | 4 | RID-0000556097 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.36/30 | 4 | RID-0000961407 | unknown | LEGACY | Feb 6, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.40/29 | 8 | RID-0000018959 | unknown | LEGACY | Jul 24, 2018 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.48/28 | 16 | RID-0000133214 | unknown | LEGACY | Sep 14, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.64/26 | 64 | RID-0000123992 | unknown | LEGACY | Sep 14, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.31.128/25 | 128 | GENERAL-PRIVATE-NET-A251-22 | Dynamic private network | LEGACY | Sep 14, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.32.0/22 | 1,024 | GENERAL-PRIVATE-NET-A333-5 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.36.0/22 | 1,024 | GENERAL-PRIVATE-NET-A333-7 | Dynamic private network | LEGACY | Jun 5, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.32/27 | 32 | RID-0000016321 | unknown | LEGACY | Jul 24, 2018 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.64/30 | 4 | RID-0000924082 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.68/30 | 4 | RID-0000924082 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.72/30 | 4 | RID-0000924082 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.76/30 | 4 | RID-0000204250 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.80/29 | 8 | RID-0000967157 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.88/30 | 4 | RID-0000976734 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.92/30 | 4 | RID-0000302479 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.96/30 | 4 | RID-0000985102 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.100/31 | 2 | RID-0000433585 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.102/31 | 2 | RID-0000682713 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.104/29 | 8 | RID-0000336140 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.112/29 | 8 | RID-0000424085 | unknown | LEGACY | Jul 24, 2018 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.120/29 | 8 | RID-0000336140 | unknown | LEGACY | Oct 3, 2023 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.160/27 | 32 | RID-0000512648 | unknown | LEGACY | Sep 14, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.192/29 | 8 | GENERAL-PRIVATE-NET-A400-70 | Dynamic private network | LEGACY | Sep 14, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.40.208/28 | 16 | GENERAL-PRIVATE-NET-A400-71 | Dynamic private network | LEGACY | Sep 14, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.41.0/24 | 256 | GENERAL-PRIVATE-NET-A412-125 | Dynamic private network | LEGACY | Sep 14, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.0/29 | 8 | RID-0000911520 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.8/30 | 4 | RID-0000918214 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.12/30 | 4 | RID-0000626079 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.16/29 | 8 | RID-0000157061 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.24/29 | 8 | RID-0000467553 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.32/30 | 4 | RID-0000916461 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.36/30 | 4 | RID-0000835731 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.40/29 | 8 | RID-0000917844 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.64/30 | 4 | RID-0000441329 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.68/30 | 4 | RID-0000015662 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.72/30 | 4 | RID-0000915387 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.76/30 | 4 | RID-0000327922 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.80/28 | 16 | RID-0000436428 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.96/29 | 8 | RID-0000918844 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.104/30 | 4 | RID-0000918692 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.108/30 | 4 | RID-0000015716 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.112/29 | 8 | RID-0000768830 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.128/30 | 4 | RID-0000911221 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.132/30 | 4 | RID-0000917330 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.136/30 | 4 | RID-0000465921 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.140/30 | 4 | RID-0000918956 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.144/29 | 8 | RID-0000912921 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.152/30 | 4 | RID-0000917557 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.156/30 | 4 | RID-0000714411 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.160/30 | 4 | RID-0000888471 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.164/30 | 4 | RID-0000299406 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.168/29 | 8 | RID-0000919202 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.176/30 | 4 | RID-0000918020 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.180/30 | 4 | RID-0000299406 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.184/31 | 2 | RID-0000299406 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.186/31 | 2 | RID-0000365765 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.188/30 | 4 | RID-0000914000 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.192/29 | 8 | RID-0000769925 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.200/29 | 8 | RID-0000873710 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.208/29 | 8 | RID-0000442554 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.216/30 | 4 | RID-0000918642 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.220/30 | 4 | RID-0000696675 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.224/30 | 4 | RID-0000838415 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.228/30 | 4 | RID-0000493088 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.232/29 | 8 | RID-0001048521 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.240/29 | 8 | RID-0000878830 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.248/30 | 4 | RID-0000892960 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.42.252/30 | 4 | RID-0000136420 | unknown | LEGACY | Jun 28, 2022 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.43.0/24 | 256 | GENERAL-PRIVATE-NET-A328-162 | Dynamic private network | LEGACY | Sep 14, 2017 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.44.40/30 | 4 | RID-0001017046 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
| └ 158.174.44.44/30 | 4 | RID-0001012467 | unknown | LEGACY | Aug 26, 2024 | abuse@ via BAHNHOF-AGGREGATE |
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
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 55,438 | 85% | 181 | |
| Business | 10,096 | 15% | 283 | |
| Tor exitanonymizer | 1 | <0.01% | 1 | |
| VPNanonymizer | 1 | <0.01% | 1 |
Network & registry
Origin network
AS8473
SE
- Name
- Bahnhof AB
- Type
- Internet provider
- Registered
- Sep 18, 1997
- Domain
- bahnhof.se
- Website
- www.bahnhof.net/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
- VPN servers
- 127
- Tor exits
- 2
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
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8473 | RIPE | Bahnhof Internet, Sweden | BAHNHOF-NCC | May 28, 2016 |
Whois
Registration for this announcement
- Range
- 158.
174. 0. 0/ 16 - Netname
- BAHNHOF-AGGREGATE
- Registrant
- Bahnhof AB
- Registrant country
- SE
- Organization
- Bahnhof AB (ORG-BIA1-RIPE)
- Org country
- SE
- Type
- LEGACY
- Created
- Not stated by the registry
- Updated
- Jul 3, 2023
- Maintainer
- BAHNHOF-NCC
- RIR
- RIPE NCC
- Country
- GB
- Delegated
- Mar 24, 1992
- Status
- assigned
Report abuse
Abuse contact
- abuse@
bahnhof. net - Name
- Abuse-C Role
- Handle
- AR13477-RIPE