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

155.4.0.0/16

1,292 residential-proxy exits · 30 days

Bahnhof AB

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

Residential-proxy exits

Proxy exits
1,292
2.0% of its addresses · 30 days
Always-on exits
95
7.4% of its exits
Spread
141 of 256
/24s with at least one exit
Providers
119
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

426K observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
155.4.130.0/2418114
155.4.132.0/2412109
155.4.129.0/2412102
155.4.131.0/249110
155.4.221.0/249107
155.4.128.0/248111
155.4.133.0/245107
155.4.222.0/24273
155.4.14.0/24222
155.4.89.0/24213
155.4.37.0/2429
155.4.183.0/2422
155.4.190.0/2419
155.4.68.0/2416
155.4.218.0/2416
155.4.206.0/2415
155.4.34.0/2413
155.4.139.0/2413
155.4.92.0/2412
155.4.108.0/2412
155.4.189.0/2412
155.4.69.0/2411
155.4.219.0/2411
155.4.113.0/2411

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
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PacketStream
  • PrivateByte
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • TrustProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare
  • 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
155.4.0.0/1665,536BAHNHOF-AGGREGATEBahnhof AB (ORG-BIA1-RIPE) · SELEGACY—abuse@bahnhof.net
└ 155.4.39.232/298GENERAL-PRIVATE-NET-A893-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.240/2816RID-0000589883unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.40.0/24256GENERAL-PRIVATE-NET-A240-20Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.0/304RID-0000442275unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.4/304RID-0000907300unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.8/312RID-0000213024unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.10/312RID-0000055009unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.12/304RID-0000750802unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.16/304RID-0000769848unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.20/304RID-0000928120unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.24/298RID-0000067182unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.32/304RID-0000319869unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.36/304RID-0000231410unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.40/304RID-0000783909unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.44/304RID-0000464627unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.48/2816GENERAL-PRIVATE-NET-A498-303Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.64/2732GENERAL-PRIVATE-NET-A904-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.96/298RID-0000526522unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.104/304RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.108/304RID-0001036710unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.112/304RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.116/304RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.120/304RID-0000603576unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.124/304RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.41.128/25128GENERAL-PRIVATE-NET-A904-2Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.42.0/24256GENERAL-PRIVATE-NET-A444-25Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.0/298RID-0000578410unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.8/312RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.10/312RID-0000452847unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.12/312RID-0000452847unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.14/312RID-0000452847unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.16/312RID-0000452847unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.18/312RID-0000452847unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.20/312RID-0000452847unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.22/312RID-0000452847unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.24/312RID-0000235529unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.26/312RID-0000235529unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.28/312RID-0000235529unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.30/312RID-0000235529unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.32/304RID-0000963328unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.36/312RID-0000235529unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.38/312RID-0000235529unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.40/304RID-0001025899unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.44/304RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.48/2816RID-0000196570unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.64/304RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.68/304RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.72/304RID-0000606375unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.76/304RID-0000607165unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.80/2816GENERAL-PRIVATE-NET-A498-151Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.96/2732GENERAL-PRIVATE-NET-A498-152Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.128/304RID-0000254752unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.132/304RID-0000610956unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.140/304RID-0000971260unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.144/298RID-0000254379unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.152/304RID-0000491653unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.156/304RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.176/2816GENERAL-PRIVATE-NET-A822-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.192/304RID-0000584958unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.200/304RID-0000338581unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.204/304RID-0000586193unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.208/304RID-0000859076unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.212/304RID-0000668112unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.216/304RID-0000748409unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.220/304RID-0000453885unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.224/304RID-0000911467unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.228/304RID-0000864840unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.232/298RID-0000539224unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.248/304RID-0000640471unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.43.252/304RID-0000713965unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.0/304RID-0000626465unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.4/304RID-0000608898unknownLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.8/298RID-0000053486unknownLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.16/298RID-0000433640unknownLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.24/312RID-0000028551unknownLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.28/304RID-0000554863unknownLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.32/304RID-0000938947unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.36/304RID-0000552384unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.40/304RID-0000603709unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.44/304RID-0000998897unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.50/312RID-0000213024unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.52/304RID-0000599261unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.56/298RID-0000213024unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.64/304RID-0000606511unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.68/312RID-0000213024unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.70/312RID-0000213024unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.72/312RID-0000213024unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.76/304RID-0000909121unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.80/304RID-0000602669unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.88/298RID-0000213024unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.98/312RID-0000443402unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.100/304RID-0000891313unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.104/304RID-0000186649unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.108/304RID-0000780627unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.112/304RID-0000209939unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.116/304RID-0000789338unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.120/304RID-0000338140unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.124/304RID-0000204607unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.128/304RID-0000982692unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.132/304RID-0000616914unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.144/312RID-0000055009unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.146/312RID-0000055009unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.148/312RID-0000055009unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.150/312RID-0000055009unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.152/312RID-0000055009unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.156/304RID-0000277929unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.160/2816GENERAL-PRIVATE-NET-A848-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.192/2732GENERAL-PRIVATE-NET-A848-2Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.45.224/2732GENERAL-PRIVATE-NET-A498-153Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.46.0/24256GENERAL-PRIVATE-NET-A163-8Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.0/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.4/304RID-0000588904unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.8/298RID-0000359470unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.16/298RID-0000968096unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.28/304RID-0000476119unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.32/298RID-0000349600unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.40/304RID-0000291607unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.44/304RID-0000314795unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.48/298RID-0000273986unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.56/304RID-0000591335unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.60/304GENERAL-CORPORATE-NETDynamic corporate networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.64/2732GENERAL-PRIVATE-NET-A498-154Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.96/304RID-0000609782unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.100/304RID-0000364946unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.104/298RID-0000715391unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.112/304RID-0000752201unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.116/304RID-0000599187unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.128/2732GENERAL-PRIVATE-NET-A498-155Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.160/2732GENERAL-PRIVATE-NET-A1283-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.47.192/2664GENERAL-PRIVATE-NET-A916-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.48.0/24256GENERAL-PRIVATE-NET-A163-3Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.0/2664GENERAL-PRIVATE-NET-A882-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.64/304RID-0000990658unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.68/304RID-0000963517unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.72/304RID-0000443402unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.76/304RID-0000592836unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.80/304GENERAL-PRIVATE-NET-A1247-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.84/304RID-0000441557unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.88/298RID-0000493088unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.100/304RID-0001052556unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.104/298GENERAL-PRIVATE-NET-A530-10Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.112/304RID-0000436654unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.116/304RID-0000575008unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.120/304RID-0000835209unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.124/304RID-0000588483unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.128/2816RID-0000528858unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.144/304RID-0000491715unknownLEGACYDec 21, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.150/312INFRA-AW-BIABInfrastructure networkLEGACYAug 13, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.152/298GENERAL-PRIVATE-NET-A955-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.160/2816GENERAL-PRIVATE-NET-A956-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.176/298GENERAL-PRIVATE-NET-A967-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.184/298GENERAL-PRIVATE-NET-A960-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.192/2816GENERAL-PRIVATE-NET-A957-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.208/2816GENERAL-PRIVATE-NET-A959-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.224/2816GENERAL-PRIVATE-NET-A958-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.49.240/2816GENERAL-PRIVATE-NET-A961-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.50.0/23512GENERAL-PRIVATE-NET-A980-85Dynamic private networkLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.52.0/24256GENERAL-PRIVATE-NET-A213-11Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.53.0/24256GENERAL-PRIVATE-NET-A357-14Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.54.0/24256GENERAL-PRIVATE-NET-A980-67Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.55.0/24256GENERAL-PRIVATE-NET-A444-26Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.56.0/24256GENERAL-PRIVATE-NET-A412-96Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.57.0/24256GENERAL-PRIVATE-NET-A412-97Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.58.0/24256GENERAL-PRIVATE-NET-A328-85Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.59.0/24256GENERAL-PRIVATE-NET-A980-86Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.60.0/24256GENERAL-PRIVATE-NET-A412-99Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.61.0/24256GENERAL-PRIVATE-NET-A980-87Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.62.0/24256GENERAL-PRIVATE-NET-A980-44Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.63.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.64.0/221,024GENERAL-PRIVATE-NET-A183-3Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.68.0/221,024GENERAL-PRIVATE-NET-A785-10Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.72.0/23512GENERAL-PRIVATE-NET-A192-6Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.74.0/24256GENERAL-PRIVATE-NET-A444-27Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.75.0/24256GENERAL-PRIVATE-NET-A1160-1Dynamic private networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.76.0/23512GENERAL-CORPORATE-NET-A182-9Dynamic corporate networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.78.0/24256GENERAL-PRIVATE-NET-A295-13Dynamic private networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.79.0/24256GENERAL-PRIVATE-NET-A463-8Dynamic private networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.0/2816RID-0000942393unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.16/304RID-0000948061unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.20/304RID-0000322264unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.24/304RID-0000944793unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.28/304RID-0000780627unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.32/2816RID-0000939882unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.64/2664GENERAL-CORPORATE-NET-A444-21Dynamic corporate networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.128/2664GENERAL-CORPORATE-NET-A444-22Dynamic corporate networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.224/298RID-0000941999unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.80.232/298RID-0000357675unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.81.0/24256GENERAL-PRIVATE-NET-A980-98Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.82.0/24256GENERAL-PRIVATE-NET-A980-99Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.83.0/24256GENERAL-PRIVATE-NET-A980-100Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.84.0/221,024GENERAL-PRIVATE-NET-A980-101Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.88.0/24256GENERAL-PRIVATE-NET-A159-7Dynamic private networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.89.0/2732GENERAL-PRIVATE-NET-A1322-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.89.32/2816GENERAL-PRIVATE-NET-A1315-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.89.52/304RID-0000188844unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.89.56/298RID-0000583075unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.89.128/25128RID-00002423605th of July FoundationLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.0/2664GENERAL-PRIVATE-NETDynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.64/2816GENERAL-PRIVATE-NET-A498-182Dynamic private networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.80/298RID-0000171023unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous201–400 of 776 · page 2 of 4Next →

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
Residential58,30489%70
Business7,23211%168

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
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