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.90.88/298RID-0000663631unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.96/298INFRA-AW-BIABInfrastructure networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.104/298GENERAL-CORPORATE-NET-A324-16Dynamic corporate networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.112/2816GENERAL-CORPORATE-NET-A137-126Dynamic corporate networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.128/2664GENERAL-PRIVATE-NET-A505-3Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.192/2732GENERAL-CORPORATE-NET-A444-3Dynamic corporate networkLEGACYFeb 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.224/2816GENERAL-PRIVATE-NET-A517-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.90.240/2816INFRA-AW-BIABInfrastructure networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.91.0/24256GENERAL-PRIVATE-NET-A240-12Dynamic private networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.92.0/24256GENERAL-PRIVATE-NET-A980-45Dynamic private networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.93.0/24256GENERAL-PRIVATE-NET-A980-68Dynamic private networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.94.0/23512GENERAL-PRIVATE-NET-A980-64Dynamic private networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.96.0/24256GENERAL-PRIVATE-NET-A980-102Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.97.0/24256GENERAL-PRIVATE-NET-A980-103Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.98.0/24256GENERAL-PRIVATE-NET-A197-8Dynamic private networkLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.16/2816RID-0001022855unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.32/2816RID-0001022855unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.64/298RID-0000987008unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.80/2816RID-0001022855unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.112/298RID-0000335271unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.128/298RID-0000995875unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.144/298RID-0000677365unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.160/298RID-0000820918unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.176/298RID-0001023990unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.184/298RID-0000994371unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.200/298RID-0001014148unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.208/298RID-0000299406unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.216/298RID-0000955126unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.224/298RID-0000997279unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.232/298RID-0000279334unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.99.240/2816RID-0000441905unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.0/2732GENERAL-PRIVATE-NET-A498-343Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.32/2732GENERAL-PRIVATE-NET-A498-344Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.64/298RID-0000733871unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.72/304RID-0000947370unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.76/304RID-0000983058unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.80/304RID-0000666778unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.84/304RID-0000983106unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.88/298RID-0000325388unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.96/2816GENERAL-PRIVATE-NET-A498-345Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.112/298RID-0000911337unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.120/304RID-0000940889unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.124/304RID-0000450649unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.128/2664GENERAL-PRIVATE-NETDynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.192/298RID-0000920274unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.200/298RID-0000170776unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.100.216/298RID-0000939444unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.101.0/24256GENERAL-PRIVATE-NET-A980-104Dynamic private networkLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.102.0/24256GENERAL-PRIVATE-NET-A980-105Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.103.0/24256GENERAL-PRIVATE-NET-A444-3Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.104.0/25128GENERAL-PRIVATE-NETDynamic private networkLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.104.128/25128GENERAL-PRIVATE-NET-A1191-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.105.0/24256GENERAL-PRIVATE-NET-A469-2Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.0/2732GENERAL-PRIVATE-NET-A498-156Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.32/298RID-0000594073unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.40/304RID-0000594073unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.44/304RID-0000489137unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.48/304RID-0000025171unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.52/304RID-0000484017unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.56/304RID-0000578489unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.60/304RID-0000648050unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.64/2732GENERAL-PRIVATE-NET-A498-157Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.96/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.100/304RID-0000597912unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.104/298RID-0000200912unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.112/298RID-0000588764unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.120/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.124/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.106.128/25128GENERAL-PRIVATE-NET-A392-7Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.107.0/24256GENERAL-PRIVATE-NET-A246-10Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.108.0/24256GENERAL-PRIVATE-NET-A980-106Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.109.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.110.0/23512GENERAL-PRIVATE-NET-A357-17Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.112.0/25128GENERAL-PRIVATE-NET-A444-24Dynamic private networkLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.112.128/2664GENERAL-PRIVATE-NET-A1779-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.112.192/2816RID-0000605163unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.112.208/298RID-0000492299unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.112.216/298RID-0000249282unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.112.224/2816GENERAL-PRIVATE-NET-A1758-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.112.240/298RID-0000073018unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.112.248/298RID-0000920288unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.113.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.114.0/24256GENERAL-PRIVATE-NET-A980-133Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.115.0/24256RID-0000959363unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.116.0/23512GENERAL-PRIVATE-NET-A785-2Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.118.0/24256RID-0000165845Ansluten Blekinge ABLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.119.0/24256GENERAL-PRIVATE-NET-A240-13Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.120.0/221,024GENERAL-PRIVATE-NET-A259-29Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.124.0/24256GENERAL-PRIVATE-NET-A246-11Dynamic private networkLEGACYJun 16, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.125.0/24256GENERAL-PRIVATE-NET-A463-14Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.126.0/2664GENERAL-PRIVATE-NET-A1441-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.126.64/2664GENERAL-PRIVATE-NET-A1505-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.126.128/2732RID-0000188531unknownLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.126.160/2816GENERAL-PRIVATE-NET-A1318-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.126.176/2816RID-0000098021unknownLEGACYFeb 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.126.192/2732RID-0000086414unknownLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.126.224/2732GENERAL-CORPORATE-NET-A137-141Dynamic corporate networkLEGACYFeb 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.127.0/25128GENERAL-PRIVATE-NET-A216-10Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.127.128/25128GENERAL-PRIVATE-NET-A324-17Dynamic private networkLEGACYFeb 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.128.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.129.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.130.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.131.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.132.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.133.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.136.0/23512GENERAL-PRIVATE-NET-A376-16Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.138.0/23512GENERAL-PRIVATE-NET-A317-5Dynamic private networkLEGACYJan 20, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.140.0/24256GENERAL-PRIVATE-NET-A505-1Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.141.0/24256GENERAL-PRIVATE-NET-A197-9Dynamic private networkLEGACYFeb 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.142.0/24256GENERAL-PRIVATE-NET-A159-8Dynamic private networkLEGACYFeb 23, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.143.0/2732RID-0000170995unknownLEGACYMar 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.143.32/2732GENERAL-PRIVATE-NET-A542-1Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.143.64/2732RID-0000850968unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.143.96/2732GENERAL-PRIVATE-NET-A400-1Dynamic private networkLEGACYMar 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.143.128/2732GENERAL-CORPORATE-NET-A400-1Dynamic corporate networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.143.160/2732GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.143.192/2664GENERAL-PRIVATE-NET-A572-1Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.144.0/204,096GENERAL-PRIVATE-NET-A163-9Dynamic private networkLEGACYFeb 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.160.0/2664RID-0000153832unknownLEGACYMar 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.160.64/2732GENERAL-CORPORATE-NET-A137-152Dynamic corporate networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.160.96/2732RID-0000363515unknownLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.160.128/2732GENERAL-CORPORATE-NET-A137-153Dynamic corporate networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.160.160/2732GENERAL-CORPORATE-NET-A137-154Dynamic corporate networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.160.192/2732GENERAL-CORPORATE-NET-A324-17Dynamic corporate networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.160.224/2816GENERAL-PRIVATE-NET-A537-1Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.160.240/2816GENERAL-PRIVATE-NET-A538-1Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.161.0/25128RID-0000228192unknownLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.161.128/2664GENERAL-PRIVATE-NET-A515-1Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.161.192/2732GENERAL-PRIVATE-NET-A518-1Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.161.224/2732GENERAL-CORPORATE-NET-A137-155Dynamic corporate networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.162.0/24256INFRA-AW-BIABInfrastructure networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.163.0/24256GENERAL-PRIVATE-NET-A498-46Dynamic private networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.0/298RID-0000508406unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.8/304RID-0000882412unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.12/304RID-0000194183unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.16/298RID-0000987920unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.24/298RID-0000271085unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.32/304RID-0000232735unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.36/304RID-0000973022unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.40/304RID-0000285177unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.56/304RID-0000996900unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.60/304RID-0000513100unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.144/298RID-0000978637unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.152/298RID-0000893343unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.160/2732RID-0000100022unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.208/304RID-0000769925unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.212/304RID-0000117839unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.216/304RID-0000999102unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.220/304RID-0000924082unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.164.224/2732RID-0001001233unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.165.0/24256GENERAL-PRIVATE-NET-A522-1Dynamic private networkLEGACYFeb 23, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.166.0/24256GENERAL-PRIVATE-NET-A980-134Dynamic private networkLEGACYFeb 23, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.167.0/24256GENERAL-PRIVATE-NET-A463-16Dynamic private networkLEGACYFeb 23, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.0/2732GENERAL-PRIVATE-NET-A498-158Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.32/304RID-0000833896unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.36/312RID-0000588682unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.38/312RID-0000588682unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.40/298RID-0000588682unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.48/2816RID-0000235577unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.64/2732GENERAL-PRIVATE-NET-A498-159Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.96/2732GENERAL-PRIVATE-NET-A498-160Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.128/304RID-0000348516unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.132/304RID-0000575541unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.140/304RID-0000589806unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.144/304RID-0000008874unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.148/304RID-0000304981unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.152/304RID-0000591344unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.156/304RID-0000304981unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.160/2732GENERAL-PRIVATE-NET-A498-161Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.192/2732GENERAL-PRIVATE-NET-A498-162Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.168.224/2732GENERAL-PRIVATE-NET-A498-163Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.169.0/24256GENERAL-PRIVATE-NET-A357-59Dynamic private networkLEGACYMar 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.170.0/24256GENERAL-PRIVATE-NET-A357-18Dynamic private networkLEGACYMar 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.0/304RID-0000590534unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.4/304RID-0000751556unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.8/298RID-0000117588unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.16/2816GENERAL-PRIVATE-NET-A866-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.32/2732GENERAL-PRIVATE-NET-A498-164Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.64/2732GENERAL-PRIVATE-NET-A916-2Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.96/304RID-0000096942unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.100/304RID-0000888706unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.104/298RID-0000299406unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.120/304RID-0001019589unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.124/304RID-0001019589unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.128/2664GENERAL-CORPORATE-NET-A412-40Dynamic corporate networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.192/2816GENERAL-PRIVATE-NET-A675-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.208/2816GENERAL-PRIVATE-NET-A668-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.171.224/2732RID-0000364652unknownLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.172.0/23512GENERAL-PRIVATE-NET-A1139-1Dynamic private networkLEGACYMar 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.174.0/24256RID-0000097893unknownLEGACYMar 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.175.0/24256GENERAL-PRIVATE-NET-A333-1Dynamic private networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.176.0/221,024GENERAL-PRIVATE-NET-A785-3Dynamic private networkLEGACYMar 1, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.180.0/221,024GENERAL-PRIVATE-NET-A240-15Dynamic private networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.184.0/24256GENERAL-PRIVATE-NET-A246-20Dynamic private networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.0/298RID-0000204751unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.8/298RID-0000847006unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.16/298RID-0000425585unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.24/298RID-0000815395unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.32/298RID-0000543745unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.40/298RID-0000835712unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous401–600 of 776 · page 3 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