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

155.4.0.0/16

1,279 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,279
2.0% of its addresses · 30 days
Always-on exits
114
8.9% of its exits
Spread
140 of 256
/24s with at least one exit
Providers
116
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

423K observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
155.4.130.0/2418115
155.4.221.0/2415108
155.4.129.0/2412101
155.4.132.0/2411107
155.4.131.0/2410112
155.4.128.0/248111
155.4.133.0/247106
155.4.222.0/24370
155.4.14.0/24322
155.4.89.0/24213
155.4.190.0/2429
155.4.37.0/2427
155.4.34.0/2423
155.4.183.0/2422
155.4.109.0/24111
155.4.218.0/2417
155.4.68.0/2416
155.4.15.0/2415
155.4.231.0/2415
155.4.206.0/2415
155.4.139.0/2413
155.4.187.0/2413
155.4.97.0/2413
155.4.92.0/2412

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
  • 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.0.0/23512BAHNHOF-NOunknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.2.0/23512GENERAL-PRIVATE-NET-A240-11Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.4.0/24256GENERAL-PRIVATE-NET-A175-9Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.5.0/24256GENERAL-PRIVATE-NET-A463-3Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.6.0/24256GENERAL-PRIVATE-NET-A444-2Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.7.0/24256GENERAL-PRIVATE-NET-A980-77Dynamic private networkLEGACYJun 12, 2017abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.8.0/23512GENERAL-PRIVATE-NET-A357-13Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.10.0/23512GENERAL-PRIVATE-NET-A246-9Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.12.0/23512GENERAL-PRIVATE-NET-A165-8Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.14.0/2664RID-0000242360unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.14.64/2664GENERAL-PRIVATE-NET-A481-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.14.128/25128GENERAL-PRIVATE-NET-A412-91Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.15.0/24256GENERAL-PRIVATE-NET-A163-28Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.16.0/24256RID-0000327756unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.17.0/24256GENERAL-PRIVATE-NET-A1259-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.32/298RID-0000489931unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.40/298RID-0000489931unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.48/298RID-0000581066unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.64/304RID-0000951632unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.68/304RID-0000980995unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.72/304RID-0000099506unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.76/304RID-0000663196unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.80/304RID-0000900918unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.84/304RID-0000815821unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.88/304RID-0000319537unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.92/304RID-0000852777unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.96/298RID-0000852777unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.104/304RID-0000510525unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.108/304RID-0000973515unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.112/304RID-0000606538unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.116/304RID-0000961873unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.128/2664GENERAL-PRIVATE-NET-A303-21Dynamic private networkLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.192/298GENERAL-PRIVATE-NET-A1652-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.200/304RID-0000891327unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.204/304RID-0000910952unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.208/298RID-0000888362unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.216/298RID-0000598949unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.224/304RID-0000220504unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.228/304RID-0000811661unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.232/298RID-0000531871unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.240/298RID-0000877356unknownLEGACYDec 1, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.18.248/298GENERAL-PRIVATE-NET-A1666-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.19.0/25128GENERAL-CORPORATE-NET-A137-219Dynamic corporate networkLEGACYDec 23, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.19.128/2732RID-0000188531unknownLEGACYOct 2, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.19.160/2732GENERAL-CORPORATE-NET-A137-109Dynamic corporate networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.19.192/298RID-0000015094unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.19.200/298GENERAL-PRIVATE-NET-A498-299Dynamic private networkLEGACYMar 9, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.19.208/304RID-0000142644unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.19.212/312RID-0000173376unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.19.216/298RID-0000327931unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.19.224/2732GENERAL-PRIVATE-NET-A412-93Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.0/25128RID-0000058453unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.128/2816GENERAL-CORPORATE-NET-A469-1Dynamic corporate networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.144/312RID-0000650660unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.146/312RID-0000650660unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.148/312RID-0000650660unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.150/312RID-0000650660unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.152/304RID-0000650660unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.156/304RID-0000650660unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.160/2816GENERAL-CORPORATE-NET-A137-110Dynamic corporate networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.176/312RID-0000956811unknownLEGACYFeb 6, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.178/312RID-0000753235unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.184/298RID-0000313010unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.20.192/2664GENERAL-CORPORATE-NET-A463-4Dynamic corporate networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.21.0/25128GENERAL-PRIVATE-NET-A355-4Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.21.128/2732GENERAL-CORPORATE-NET-A137-111Dynamic corporate networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.21.160/2732GENERAL-CORPORATE-NET-A444-2Dynamic corporate networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.21.192/2664RID-0000327931unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.22.0/25128RID-0000049441unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.22.128/2732GENERAL-CORPORATE-NET-A137-112Dynamic corporate networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.22.160/2732GENERAL-CORPORATE-NET-A137-113Dynamic corporate networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.22.192/2664GENERAL-CORPORATE-NET-A324-15Dynamic corporate networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.23.0/24256GENERAL-PRIVATE-NET-A980-83Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.24.0/24256GENERAL-PRIVATE-NET-A980-97Dynamic private networkLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.25.0/24256GENERAL-PRIVATE-NET-A980-84Dynamic private networkLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.0/298RID-0000962323unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.8/298RID-0000989673unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.16/298RID-0000979930unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.24/298RID-0000433269unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.32/2816RID-0000757366unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.48/298RID-0000729820unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.56/298RID-0000991490unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.64/298RID-0000989964unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.72/298RID-0000973760unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.80/298RID-0000863343unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.88/298RID-0000989943unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.112/298RID-0000920320unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.120/298RID-0000870836unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.128/298RID-0000993391unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.136/298RID-0000190474unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.144/298RID-0000994157unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.152/298RID-0000994233unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.160/2732RID-0000816673unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.216/298RID-0000284905unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.26.224/2732GENERAL-PRIVATE-NET-A498-369Dynamic private networkLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.27.0/25128GENERAL-PRIVATE-NET-A324-16Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.27.128/2732RID-0000308081unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.27.160/2732RID-0000650660unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.27.192/2664GENERAL-PRIVATE-NET-A350-2Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.28.0/23512GENERAL-PRIVATE-NET-A317-4Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.30.0/25128GENERAL-PRIVATE-NET-A295-18Dynamic private networkLEGACYDec 27, 2016abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.30.128/2816GENERAL-PRIVATE-NET-A473-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.30.160/2732RID-0000251257unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.30.192/2664RID-0000266283unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.31.0/25128RID-0000331217unknownLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.31.128/25128GENERAL-PRIVATE-NET-A412-95Dynamic private networkLEGACYJun 10, 2015abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.32.0/221,024GENERAL-PRIVATE-NET-A182-2Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.16/298RID-0000157045unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.24/298RID-0000024235unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.48/298RID-0000648139unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.56/304RID-0001000395unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.60/304RID-0000542088unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.64/298GENERAL-PRIVATE-NET-A1775-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.72/298RID-0000732459unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.80/298RID-0000660852unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.88/298RID-0000527426unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.96/304RID-0001007679unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.104/298GENERAL-PRIVATE-NET-A879-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.112/298RID-0000066868unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.128/304RID-0000948044unknownLEGACYNov 22, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.132/304RID-0000327309unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.136/304RID-0000225816unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.144/2816GENERAL-PRIVATE-NET-A873-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.160/2816GENERAL-PRIVATE-NET-A877-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.176/298GENERAL-PRIVATE-NET-A877-2Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.184/298GENERAL-PRIVATE-NET-A908-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.36.192/2732GENERAL-PRIVATE-NET-A908-2Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.37.0/24256GENERAL-PRIVATE-NET-A887-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.0/2664GENERAL-PRIVATE-NET-A887-2Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.64/304RID-0000698929unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.68/304RID-0000597275unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.72/304RID-0001058825unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.76/304RID-0000326147unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.80/2816GENERAL-PRIVATE-NET-A889-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.96/2732GENERAL-PRIVATE-NET-A498-149Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.128/2732GENERAL-PRIVATE-NET-A889-2Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.160/298GENERAL-PRIVATE-NET-A889-3Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.168/312RID-0000131058unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.172/304RID-0000096942unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.176/304RID-0000328106unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.180/304RID-0000330105unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.184/304RID-0000527368unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.188/312RID-0000470785unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.190/312RID-0000483318unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.192/304RID-0000330906unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.196/304RID-0000652811unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.200/304RID-0000592786unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.204/304RID-0000638544unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.208/298RID-0000905323unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.218/312GENERAL-CORPORATE-NETDynamic corporate networkLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.220/304RID-0000874014unknownLEGACYOct 25, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.232/304RID-0000906005unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.236/304RID-0000910661unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.240/298RID-0000196940unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.248/304RID-0000929942unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.38.252/304RID-0000859570unknownLEGACYJan 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.0/304RID-0000928888unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.4/304RID-0000605254unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.8/304RID-0000856882unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.12/304RID-0000601726unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.16/304RID-0001012970unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.20/304RID-0000585696unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.24/304RID-0000434895unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.28/312RID-0000560154unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.30/312RID-0000560154unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.32/2732GENERAL-PRIVATE-NET-A498-150Dynamic private networkLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.64/312RID-0000560154unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.66/312RID-0000560154unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.68/304RID-0000982224unknownLEGACYOct 3, 2023abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.72/312RID-0000560154unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.74/312RID-0000560154unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.78/312RID-0000452847unknownLEGACYSep 5, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.80/298RID-0000551543unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.88/298RID-0000365825unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.96/304RID-0000255850unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.100/304RID-0000574158unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.104/298GENERAL-PRIVATE-NET-A905-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.112/304RID-0000600414unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.116/304RID-0000910277unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.120/298RID-0000497339unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.128/298GENERAL-PRIVATE-NET-A840-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.136/304RID-0000504920unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.140/304RID-0000574158unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.144/298RID-0000835127unknownLEGACYSep 3, 2021abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.152/304RID-0000604627unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.156/304RID-0000590120unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.160/304RID-0000606255unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.164/304RID-0001026024unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.168/304RID-0000186649unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.172/312RID-0000055009unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.174/312RID-0000285015unknownLEGACYNov 12, 2019abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.176/2816GENERAL-PRIVATE-NET-A790-1Dynamic private networkLEGACYJul 1, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.192/298RID-0001008705unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.200/304RID-0000911273unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.204/304RID-0000908266unknownLEGACYAug 26, 2024abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.208/304RID-0000607060unknownLEGACYNov 25, 2020abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.212/304RID-0000179946unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.216/298RID-0000829504unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.224/304RID-0000431580unknownLEGACYJul 24, 2018abuse@bahnhof.net
via BAHNHOF-AGGREGATE
└ 155.4.39.228/304RID-0000911486unknownLEGACYJun 28, 2022abuse@bahnhof.net
via BAHNHOF-AGGREGATE
← Previous1–200 of 776 · page 1 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
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2015
Current origin since
Mar 2015 · 12 yr
Origin networks
1