Data as of Nov 14, 2026

213.136.32.0/19

23 residential-proxy exits · 30 days

Bahnhof AB

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
66% of it

Residential-proxy exits

Proxy exits
23
0.28% of its addresses · 30 days
Always-on exits
1
4.3% of its exits
Spread
15 of 32
/24s with at least one exit
Providers
61
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

14K observations
  • Residential
  • Business

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • ColaProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • MarsProxies
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PSBProxy
  • PacketStream
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • 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
213.136.32.0/198,192SE-BAHNHOF-20001019Bahnhof AB (ORG-BIA1-RIPE) · SEALLOCATED PA—abuse@bahnhof.net
└ 213.136.32.0/2664BAHNHOF-ADMIN-2Bahnhof ABASSIGNED PA—abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.64/304RID-0000935582unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.68/304RID-0000552601unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.72/298RID-0000173476unknownASSIGNED PASep 22, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.82/312RID-0000140520unknownASSIGNED PAFeb 13, 2014abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.84/304RID-0000015367unknownASSIGNED PAFeb 13, 2014abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.88/298RID-0000118115unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.96 - 213.136.32.15964CSH1-CSH-NETCity Server HostingASSIGNED PAApr 4, 2002abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.160/298RID-0000130179unknownASSIGNED PAApr 13, 2010abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.168/298RID-0000018230unknownASSIGNED PAApr 8, 2014abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.184/298INFRA-AW-BIABInfrastructure networkASSIGNED PAJan 12, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.192/298RID-0000167194unknownASSIGNED PAJul 2, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.200/298RID-0000017741unknownASSIGNED PAAug 5, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.224/298RID-0000857949unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.232/304RID-0000514298unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.236/304RID-0000514298unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.32.248/298RID-0000537411unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.0/2816BAHNHOF-SERVERS-1Bahnhof ABASSIGNED PA—abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.16/2816RID-0000274997unknownASSIGNED PAOct 3, 2014abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.32/298RID-0000017665unknownASSIGNED PADec 13, 2004abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.40/298RID-0000555188unknownASSIGNED PAMay 27, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.48/2816RID-0000055539unknownASSIGNED PAMay 3, 2010abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.64/2816RID-0000548452unknownASSIGNED PASep 14, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.84/304RID-0000230277unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.88/312RID-0000299406unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.90/312RID-0000299406unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.92/304RID-0000833896unknownASSIGNED PAMay 27, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.96/298RID-0000834400unknownASSIGNED PAMay 27, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.104/298INFRA-AW-BIABInfrastructure networkASSIGNED PAJan 12, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.112/2816RID-0000857955unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.128/298RID-0000026243unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.144/298RID-0000268915unknownASSIGNED PAFeb 13, 2014abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.152/298RID-0000857946unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.160/304RID-0000924037unknownASSIGNED PAJun 28, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.164/312GENERAL-PRIVATE-NETDynamic private networkASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.168/298RID-0000078452unknownASSIGNED PAMay 11, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.176/298RID-0000857946unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.184/298RID-0000163956unknownASSIGNED PAApr 28, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.192/2732RID-0000018339unknownASSIGNED PAApr 4, 2002abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.33.224/2732RID-0000017726unknownASSIGNED PAJan 5, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.24/304RID-0000752992unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.28/304RID-0000505674unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.32/2732RID-0000018959unknownASSIGNED PAJan 20, 2016abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.64/312RID-0000083773unknownASSIGNED PASep 14, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.66/312RID-0000083773unknownASSIGNED PASep 14, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.72/298RID-0000024651unknownASSIGNED PAJan 20, 2005abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.80/298RID-0000018130unknownASSIGNED PADec 14, 2004abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.96/2816RID-0000005368unknownASSIGNED PAJan 12, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.112/2816RID-0000024651unknownASSIGNED PAJan 27, 2005abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.160/2732RID-0000168176unknownASSIGNED PAJun 5, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.34.192/2664RID-0000170226unknownASSIGNED PAJul 2, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.0/2732CSH3-CSH-NETCity Server HostingASSIGNED PANov 27, 2002abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.32/2732CSH4-CSH-NETCity Server HostingASSIGNED PANov 27, 2002abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.64/2732GENERAL-CORPORATE-NET-A137-34Dynamic corporate networkASSIGNED PAJan 12, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.96/2732GENERAL-PRIVATE-NET-A246-2Dynamic private networkASSIGNED PANov 9, 2009abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.128/298RID-0000184191unknownASSIGNED PANov 3, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.144/2816RID-0000028047unknownASSIGNED PAJan 17, 2005abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.160/298RID-0000846477unknownASSIGNED PASep 3, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.168/298RID-0000018130unknownASSIGNED PAAug 18, 2006abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.176/2816GENERAL-PRIVATE-NET-A498-18Dynamic private networkASSIGNED PADec 22, 2016abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.192/298RID-0000020462unknownASSIGNED PADec 14, 2004abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.200/304RID-0000551650unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.204/304GENERAL-CORPORATE-NETDynamic corporate networkASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.208/298RID-0000857947unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.216/298BAHNHOF-CSH-NETBahnhof ABASSIGNED PADec 14, 2004abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.224/304RID-0000614308unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.228/304RID-0000872478unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.232/304RID-0000592752unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.35.236/304RID-0000867707unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.0/298RID-0000733845unknownASSIGNED PAMay 27, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.8/298RID-0000857940unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.16/298RID-0000257117unknownASSIGNED PAJan 12, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.24/298RID-0000187229unknownASSIGNED PADec 20, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.32/2732GENERAL-PRIVATE-NET-A1013-1Dynamic private networkASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.64/298RID-0000024651unknownASSIGNED PAAug 13, 2009abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.72/298RID-0000024651unknownASSIGNED PAAug 13, 2009abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.80/298RID-0000024650unknownASSIGNED PAJul 8, 2004abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.88/298RID-0000319339unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.96/2732BAHNHOF-CSH-STHBahnhof AB - City Server HostingASSIGNED PADec 14, 2004abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.128/2732GENERAL-CORPORATE-NET-A137-201Dynamic corporate networkASSIGNED PADec 22, 2016abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.168/304RID-0000778470unknownASSIGNED PANov 22, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.172/304RID-0000690970unknownASSIGNED PAFeb 6, 2023abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.36.192/2664DEDICATED-SERVERS-NETDedicated servers, StockholmASSIGNED PAAug 25, 2008abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.0/2732GENERAL-CORPORATE-NET-A240-4Dynamic corporate networkASSIGNED PAOct 2, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.32/298RID-0000099331unknownASSIGNED PAMay 10, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.40/298RID-0000200462unknownASSIGNED PAJul 13, 2012abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.48/2816RID-0000160441unknownASSIGNED PAJun 10, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.64/2664RID-0000019035unknownASSIGNED PAJul 30, 2008abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.128/298RID-0000164421unknownASSIGNED PANov 23, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.136/298RID-0000068693unknownASSIGNED PAJan 12, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.144/298RID-0000050044unknownASSIGNED PAJul 10, 2006abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.152/312RID-0000649045unknownASSIGNED PAFeb 6, 2023abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.156/304RID-0000287146unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.160/2816RID-0000061170unknownASSIGNED PAAug 13, 2009abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.180/304RID-0000860435unknownASSIGNED PASep 3, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.184/304RID-0000330906unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.188/312RID-0000083773unknownASSIGNED PASep 14, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.190/312RID-0000083773unknownASSIGNED PASep 14, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.37.192/2664GENERAL-PRIVATE-NET-A412-34Dynamic private networkASSIGNED PANov 9, 2009abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.38.0/24256RID-0000024651unknownASSIGNED PAAug 19, 2008abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.0/304RID-0001049197unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.4/304RID-0000614308unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.8/304RID-0000487879unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.12/304RID-0000869943unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.16/2816RID-0000689916unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.32/2816RID-0000602606unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.48/304RID-0001041342unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.52/304RID-0001045725unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.56/298RID-0000488792unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.96/298RID-0000697333unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.104/298RID-0000928981unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.112/298RID-0000181964unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.39.128/25128GENERAL-PRIVATE-NET-A331-4Dynamic private networkASSIGNED PANov 9, 2009abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.0/2732GENERAL-CORPORATE-NET-A412-21Dynamic corporate networkASSIGNED PAJun 10, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.32/2732GENERAL-CORPORATE-NET-A137-105Dynamic corporate networkASSIGNED PAJun 10, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.64/298RID-0000049593unknownASSIGNED PANov 13, 2009abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.72/304RID-0000299406unknownASSIGNED PAMar 9, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.76/304RID-0000308719unknownASSIGNED PAMar 9, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.80/298RID-0000017029unknownASSIGNED PADec 15, 2004abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.88/298RID-0000446651unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.96/298RID-0000269291unknownASSIGNED PAJun 10, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.104/304RID-0000585696unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.112/304RID-0000057746unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.118/312RID-0000301255unknownASSIGNED PAFeb 6, 2023abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.120/304RID-0000187196unknownASSIGNED PAJun 10, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.124/312RID-0000361242unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.126/312RID-0000470785unknownASSIGNED PAFeb 6, 2023abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.128/312RID-0000433430unknownASSIGNED PAOct 3, 2023abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.130/312RID-0000588682unknownASSIGNED PAOct 3, 2023abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.132/304RID-0000269086unknownASSIGNED PAOct 3, 2023abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.136/298GENERAL-PRIVATE-NET-A530-44Dynamic private networkASSIGNED PAOct 3, 2023abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.152/304RID-0000017578unknownASSIGNED PAAug 13, 2009abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.156/312RID-0000488792unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.158/312RID-0000363553unknownASSIGNED PAMar 30, 2016abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.160/298RID-0000078452unknownASSIGNED PAMay 11, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.168/298RID-0000048344unknownASSIGNED PANov 22, 2010abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.176/2816GENERAL-PRIVATE-NET-A498-19Dynamic private networkASSIGNED PADec 22, 2016abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.192/298RID-0000643268unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.200/304RID-0000779433unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.204/304RID-0000884688unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.208/298RID-0000134379unknownASSIGNED PAOct 2, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.216/304RID-0001033664unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.220/304RID-0000707874unknownASSIGNED PAAug 26, 2024abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.224/298RID-0000872211unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.232/298RID-0000335688unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.240/298RID-0000921841unknownASSIGNED PAJun 28, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.40.248/298RID-0000162176unknownASSIGNED PAFeb 13, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.32/304RID-0000940046unknownASSIGNED PAOct 25, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.36/304RID-0000873525unknownASSIGNED PAOct 25, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.40/298RID-0000667474unknownASSIGNED PAOct 25, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.48/298RID-0000933654unknownASSIGNED PAOct 25, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.56/298RID-0000288121unknownASSIGNED PAOct 25, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.64/2732GENERAL-CORPORATE-NET-A137-35Dynamic corporate networkASSIGNED PAJan 12, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.96/2732GENERAL-CORPORATE-NET-A137-36Dynamic corporate networkASSIGNED PAJan 12, 2015abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.128/298RID-0000187196unknownASSIGNED PAJan 17, 2012abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.136/304GENERAL-CORPORATE-NETDynamic corporate networkASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.140/312RID-0000432657unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.142/312GENERAL-PRIVATE-NETDynamic private networkASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.152/298RID-0000019509unknownASSIGNED PASep 22, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.160/298RID-0000340658unknownASSIGNED PAMay 27, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.168/298RID-0000016870unknownASSIGNED PAFeb 14, 2005abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.176/298RID-0000019509unknownASSIGNED PAFeb 14, 2005abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.184/298RID-0000165942unknownASSIGNED PAMar 24, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.192/298RID-0000167335unknownASSIGNED PAApr 28, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.200/298RID-0000194395unknownASSIGNED PAMay 31, 2016abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.208/298RID-0000172290unknownASSIGNED PAJul 2, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.216/304RID-0000173476unknownASSIGNED PAMay 27, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.220/304RID-0000212175unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.224/298RID-0000057454unknownASSIGNED PAApr 13, 2006abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.232/298RID-0000908695unknownASSIGNED PAJun 28, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.240/298RID-0000125738unknownASSIGNED PAMay 31, 2016abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.41.248/298RID-0000501307unknownASSIGNED PAMay 11, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.0/2732STHOFFICE2-SHSthOffice2ASSIGNED PAJul 30, 2008abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.32/2816RID-0000016112unknownASSIGNED PAJul 30, 2008abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.48/304RID-0000521343unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.52/304RID-0000782982unknownASSIGNED PADec 1, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.56/304RID-0000331901unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.60/304RID-0000330906unknownASSIGNED PANov 12, 2019abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.64/304RID-0000330519unknownASSIGNED PASep 3, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.68/304RID-0000856892unknownASSIGNED PASep 3, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.72/304RID-0000862344unknownASSIGNED PASep 3, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.76/304RID-0000242030unknownASSIGNED PASep 3, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.96/2816RID-0000048439unknownASSIGNED PAApr 12, 2006abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.112/2816GENERAL-PRIVATE-NET-A498-20Dynamic private networkASSIGNED PADec 22, 2016abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.128/298RID-0000235962unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.136/298RID-0000365626unknownASSIGNED PANov 25, 2020abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.144/2816RID-0000020354unknownASSIGNED PAJan 5, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.160/2732GENERAL-CORPORATE-NET-A400-6Dynamic corporate networkASSIGNED PAOct 3, 2014abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.208/304RID-0000025765unknownASSIGNED PAAug 13, 2009abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.212/304INFRA-AW-BIABInfrastructure networkASSIGNED PANov 3, 2011abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.216/298RID-0000055126unknownASSIGNED PANov 14, 2012abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.224/304RID-0000194395unknownASSIGNED PAOct 3, 2014abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.228/304RID-0000194395unknownASSIGNED PAOct 3, 2014abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.232/298INFRA-AW-BIABInfrastructure networkASSIGNED PANov 20, 2017abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.240/304RID-0000937892unknownASSIGNED PASep 5, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.244/304RID-0000733529unknownASSIGNED PASep 5, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.248/304RID-0000937031unknownASSIGNED PASep 5, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.42.252/304RID-0000936770unknownASSIGNED PASep 5, 2022abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.43.0/304RID-0000860663unknownASSIGNED PASep 3, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
└ 213.136.43.4/304RID-0000861093unknownASSIGNED PASep 3, 2021abuse@bahnhof.net
via SE-BAHNHOF-20001019
← Previous1–200 of 599 · page 1 of 3Next →

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

8,192 addresses
TypeAddressesShareRanges
Residential5,39066%54
Business2,78634%84
Hosting160.20%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1