Data as of Nov 16, 2026

185.80.50.0/24

1 residential-proxy exit · 30 days

Rackforest Zrt.

Announcement
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

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

Exits seen per day

804 observations

Proxy providers listing exits

  • BottingTools
  • CatProxies
  • DataImpulse
  • EZProxies
  • Geonode
  • HideProxy
  • InfiniteProxies
  • NextProxy
  • ProxiesVision
  • ProxyGeo
  • TrueProxies

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.80.48.0/221,024HU-RACKFOREST-20141204Rackforest Zrt. (ORG-RIKS1-RIPE) · HUALLOCATED PADec 29, 2016abuse@rackforest.net
└ 185.80.50.0/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.16/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.32/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.48/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.64/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.80/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.96/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.112/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.128/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.144/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.160/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.176/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.192/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.208/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.224/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204
└ 185.80.50.240/2816RACKFORESTRackForestASSIGNED PAFeb 25, 2017abuse@rackforest.net
via HU-RACKFOREST-20141204

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.80.48.0/22

185.80.48.0/22

Routing history

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