Data as of Nov 16, 2026

185.36.121.0/24

1 residential-proxy exit · 30 days

NetCom BW GmbH

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
1
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

6 observations

Proxy providers listing exits

  • FastProxy

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.36.120.0/221,024DE-ODR-TKG-20130930NetCom BW GmbH (ORG-OTG1-RIPE) · DEALLOCATED PASep 30, 2013abuse@netcom-bw.de
└ 185.36.121.0/2664IPv4_Range_for_OLYMP_Bezner_over_NetCom_BWunknownASSIGNED PAFeb 17, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.64/298IPv4_Range_for_Ibis_over_NetCom_BWunknownASSIGNED PADec 6, 2021abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.72/298IPv4_Range_for_Schwarz_IT_over_NetCom_BWunknownASSIGNED PAJan 20, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.80/298IPv4_Range_for_CAMLOG_over_NetCom_BWunknownASSIGNED PAJan 12, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.88/298IPv4_Range_for_Corden_Pharma_over_NetCom_BWunknownASSIGNED PAMar 17, 2023abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.96/298IPv4_Range_for_Schwarz_IT_over_NetCom_BWunknownASSIGNED PAJan 20, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.112/2816IPv4_Range_for_Stadtverwaltung_Sinsheim_over_NetCom_BWunknownASSIGNED PAJan 20, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.128/2732IPv4_Range_for_iTEC_Services_GmbH_over_NetCom_BWunknownASSIGNED PAJan 10, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.160/298IPv4_Range_for_Krankenhaus_vom_Roten_Kreuz_over_NetCom_BWunknownASSIGNED PAJan 18, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.168/298IPv4_Range_for_ENRW_Energieversorgung_Rottweil_over_NetCom_BWunknownASSIGNED PAJan 14, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.176/298IPv4_Range_for_Schaltec_over_NetCom_BWunknownASSIGNED PAJan 25, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.184/298IPv4_Range_for_Zeitfracht_over_NetCom_BWunknownASSIGNED PAJan 24, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.192/298IPv4_Range_for_Stadt_Munderkingen_over_NetCom_BWunknownASSIGNED PAFeb 14, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.200/298IPv4_Range_for_experimenta_over_NetCom_BWunknownASSIGNED PAFeb 1, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.216/298IPv4_Range_for_Rayher_Hobby_over_NetCom_BWunknownASSIGNED PAFeb 22, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.224/298IPv4_Range_for_Stadt_Muehlacker_over_NetCom_BWunknownASSIGNED PAMar 1, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.240/298IPv4_Range_for_Stadtzwerge_over_NetCom_BWunknownASSIGNED PAMar 14, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930
└ 185.36.121.248/298IPv4_Range_for_OTS_Astracon_over_NetCom_BWunknownASSIGNED PAApr 4, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20130930

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced 185.36.120.0/22

185.36.120.0/22

Routing history

Pattern
Stable
First seen
Mar 2014
Current origin since
Jun 2021 · 5.4 yr
Origin networks
3
Last change of origin
Mar 2020
Recorded history

History

Handoffs
3