Data as of Nov 16, 2026

185.22.180.0/22

4 residential-proxy exits · 30 days

JSC 'RetnNet'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
14
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

127 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.22.182.0/2402
185.22.181.0/2401
185.22.183.0/2401

Proxy providers listing exits

  • BirdProxies
  • DataImpulse
  • EnigmaProxy
  • IPFly
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • Proxy4U
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • ResiProxies
  • VantageProxies

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
185.22.180.0/221,024RU-RETNNET-20130402JSC "RetnNet" (ORG-CA1293-RIPE) · RUALLOCATED PAApr 2, 2013abuse@retn.ru
└ 185.22.182.0/24256RU-RETNNET-SPBCJSC "RetnNet" Saint Petersburg customersASSIGNED PANov 5, 2014abuse@retn.ru
via RU-RETNNET-20130402
└ 185.22.183.0/25128RETNRU-LLCJSC "RetnNet" external interconnectionsASSIGNED PAOct 1, 2013abuse@retn.ru
via RU-RETNNET-20130402
└ 185.22.183.128/25128RETNRU-INTCJSC "RetnNet" network equipment & public serversASSIGNED PAOct 1, 2013abuse@retn.ru
via RU-RETNNET-20130402

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2013
Current origin since
Apr 2013 · 14 yr
Origin networks
1