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.185.48/2816GENERAL-PRIVATE-NET-A498-304Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.64/304RID-0000954462unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.68/304RID-0000941211unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.72/298RID-0000924413unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.80/298RID-0000714314unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.88/298RID-0000815793unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.96/2816RID-0000204399unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.112/298RID-0000157061unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.120/298RID-0000157061unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.185.128/25128GENERAL-PRIVATE-NET-A251-16Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.186.0/24256GENERAL-PRIVATE-NET-A980-135Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.187.0/24256GENERAL-PRIVATE-NET-A980-136Dynamic private networkLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.188.0/24256GENERAL-PRIVATE-NET-A412-108Dynamic private networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.0/298RID-0001010863unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.8/298RID-0000932553unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.16/2816RID-0000667442unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.32/304RID-0000928140unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.36/304RID-0000928765unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.40/304RID-0000186108unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.44/304RID-0000923074unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.48/298RID-0000186108unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.56/298RID-0000874056unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.64/304RID-0000958706unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.68/304RID-0001030137unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.72/304RID-0000780627unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.76/304RID-0000916719unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.80/304RID-0000065464unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.84/304RID-0000976259unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.88/298RID-0000851015unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.128/2664GENERAL-PRIVATE-NET-A303-31Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.189.192/2664GENERAL-PRIVATE-NET-A303-32Dynamic private networkLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.190.0/24256GENERAL-PRIVATE-NET-A197-18Dynamic private networkLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.191.0/24256GENERAL-PRIVATE-NET-A197-19Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.192.0/24256GENERAL-PRIVATE-NET-A785-11Dynamic private networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.193.0/24256GENERAL-PRIVATE-NET-A159-9Dynamic private networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.194.0/24256GENERAL-PRIVATE-NET-A230-22Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.195.0/24256GENERAL-PRIVATE-NET-A412-110Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.196.0/24256GENERAL-PRIVATE-NET-A192-19Dynamic private networkLEGACYMar 30, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.197.0/24256GENERAL-PRIVATE-NET-A980-65Dynamic private networkLEGACYApr 4, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.198.0/24256GENERAL-PRIVATE-NET-A785-12Dynamic private networkLEGACYApr 4, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.0/298RID-0000086803unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.8/304RID-0000562767unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.12/304RID-0000952220unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.32/304RID-0000148293unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.36/304RID-0000933654unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.40/298RID-0000949823unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.48/304RID-0001030925unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.52/304RID-0000488618unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.56/304RID-0000953211unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.60/304RID-0000952874unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.64/2732GENERAL-PRIVATE-NET-A498-346Dynamic private networkLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.96/304RID-0000954392unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.100/304RID-0000952634unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.104/304RID-0000926107unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.108/304RID-0000299728unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.112/304RID-0000961569unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.116/304RID-0000524781unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.120/304RID-0000952208unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.124/304RID-0000254273unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.128/304RID-0000773404unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.132/304RID-0000946624unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.136/298RID-0000950122unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.152/304RID-0000761558unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.156/304RID-0000363734unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.160/304RID-0000906002unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.164/304RID-0000220504unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.168/304RID-0000623336unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.172/304RID-0000948886unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.176/304RID-0000884194unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.180/304RID-0000301255unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.184/298RID-0000859019unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.192/298RID-0000935969unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.200/298RID-0000954167unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.224/298RID-0000494846unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.232/304RID-0000794541unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.236/304RID-0000955583unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.240/304RID-0000948367unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.244/304RID-0000885614unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.248/304RID-0000954205unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.199.252/304RID-0000576620unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.200.0/221,024GENERAL-PRIVATE-NET-A317-6Dynamic private networkLEGACYApr 4, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.204.0/24256GENERAL-PRIVATE-NET-A463-17Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.205.0/24256GENERAL-PRIVATE-NET-A357-19Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.206.0/25128GENERAL-CORPORATE-NET-A259-5Dynamic corporate networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.206.128/25128GENERAL-CORPORATE-NET-A251-2Dynamic corporate networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.207.0/24256GENERAL-PRIVATE-NET-A316-7Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.208.0/24256GENERAL-PRIVATE-NET-A324-18Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.209.0/24256GENERAL-PRIVATE-NET-A463-18Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.210.0/24256GENERAL-PRIVATE-NET-A197-16Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.211.0/24256GENERAL-PRIVATE-NET-A412-113Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.212.0/24256GENERAL-PRIVATE-NET-A980-108Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.213.0/24256GENERAL-PRIVATE-NET-A980-109Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.214.0/24256GENERAL-PRIVATE-NET-A1733-1Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.215.0/24256GENERAL-PRIVATE-NET-A980-110Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.0/2664GENERAL-PRIVATE-NET-A498-292Dynamic private networkLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.64/2816GENERAL-PRIVATE-NET-A1658-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.80/298RID-0000024235unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.88/298RID-0000875434unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.96/2816RID-0000879178unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.112/2816RID-0000873096unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.128/298RID-0000719338unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.136/298RID-0000796092unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.144/2816GENERAL-PRIVATE-NET-A498-295Dynamic private networkLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.160/298RID-0000889557unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.168/298RID-0000886301unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.176/304RID-0000639917unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.180/304RID-0000878744unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.184/304RID-0000776140unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.188/304RID-0000911048unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.192/304RID-0000887849unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.196/304RID-0000891721unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.200/298RID-0000028532unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.212/304RID-0000841115unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.216/304RID-0000266172unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.220/304RID-0000889304unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.224/2816RID-0000889358unknownLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.240/298RID-0000266172unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.248/304RID-0000986389unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.216.252/304RID-0000941209unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.217.0/24256GENERAL-PRIVATE-NET-A980-111Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.218.0/24256GENERAL-PRIVATE-NET-A980-112Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.219.0/24256GENERAL-PRIVATE-NET-A980-113Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.220.0/24256GENERAL-PRIVATE-NET-A216-11Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.221.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.222.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.223.0/24256GENERAL-PRIVATE-NET-A412-120Dynamic private networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.224.0/24256GENERAL-CORPORATE-NET-A463-10Dynamic corporate networkLEGACYMay 31, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.225.0/24256GENERAL-PRIVATE-NET-A444-6Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.0/25128GENERAL-CORPORATE-NET-A463-12Dynamic corporate networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.136/298RID-0000235879unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.144/304RID-0000732784unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.148/304RID-0000440431unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.152/298RID-0000442391unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.160/2816GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.176/2816RID-0000092425unknownLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.192/2816GENERAL-PRIVATE-NET-A584-1Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.208/2816GENERAL-PRIVATE-NET-A498-47Dynamic private networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.226.224/2732GENERAL-CORPORATE-NET-A137-206Dynamic corporate networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.227.0/24256GENERAL-PRIVATE-NET-A785-13Dynamic private networkLEGACYJun 16, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.228.0/23512GENERAL-PRIVATE-NET-A197-10Dynamic private networkLEGACYJun 16, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.230.0/24256GENERAL-PRIVATE-NET-A980-114Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.231.0/24256GENERAL-PRIVATE-NET-A980-46Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.232.0/24256GENERAL-PRIVATE-NET-A357-20Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.233.0/24256GENERAL-PRIVATE-NET-A357-21Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.234.0/24256GENERAL-PRIVATE-NET-A357-22Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.235.0/24256GENERAL-PRIVATE-NET-A357-23Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.236.0/24256GENERAL-PRIVATE-NET-A158-3Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.237.0/24256GENERAL-PRIVATE-NET-A463-15Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.238.0/24256GENERAL-PRIVATE-NET-A463-19Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.239.0/24256GENERAL-PRIVATE-NET-A785-14Dynamic private networkLEGACYAug 24, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.240.0/24256GENERAL-PRIVATE-NET-A216-13Dynamic private networkLEGACYMar 2, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.0/2732GENERAL-PRIVATE-NET-A400-66Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.32/2816GENERAL-PRIVATE-NET-A400-67Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.48/2816RID-0000005550unknownLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.64/2732GENERAL-PRIVATE-NET-A498-61Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.96/2816GENERAL-PRIVATE-NET-A498-62Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.112/2816GENERAL-PRIVATE-NET-A666-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.128/2816GENERAL-CORPORATE-NET-A184-2Dynamic corporate networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.144/2816GENERAL-PRIVATE-NET-A661-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.160/2732GENERAL-PRIVATE-NET-A615-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.192/2816GENERAL-PRIVATE-NET-A659-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.208/298GENERAL-PRIVATE-NET-A659-2Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.216/298GENERAL-PRIVATE-NET-A498-63Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.241.224/2732GENERAL-CORPORATE-NET-A137-253Dynamic corporate networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.242.0/24256GENERAL-PRIVATE-NET-A175-12Dynamic private networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.243.0/24256GENERAL-PRIVATE-NETDynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.244.0/23512RID-0000656849unknownLEGACYMay 27, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.246.0/24256GENERAL-PRIVATE-NET-A444-5Dynamic private networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.247.0/24256GENERAL-PRIVATE-NET-A412-122Dynamic private networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.248.0/24256GENERAL-PRIVATE-NET-A328-142Dynamic private networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.249.0/24256GENERAL-PRIVATE-NET-A463-23Dynamic private networkLEGACYDec 22, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.250.0/24256GENERAL-PRIVATE-NET-A412-123Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.251.0/24256GENERAL-PRIVATE-NET-A324-19Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.252.0/24256GENERAL-PRIVATE-NET-A980-91Dynamic private networkLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.253.0/24256GENERAL-PRIVATE-NET-A980-6Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.254.0/23512GENERAL-PRIVATE-NET-A324-4Dynamic private networkLEGACYMay 11, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous601–776 of 776 · page 4 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