Data as of Nov 21, 2026

171.22.212.0/24

6 residential-proxy exits · 30 days

R-Line 1 LLC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
4
67% of its exits
Providers
41
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

32K observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • B2Proxy
  • BUYPERSONALPROXY
  • BirdProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • Datarama
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LOKIPROXY
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxy-Seller
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalExclusive

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
171.22.212.0/221,024RU-RLINE1-20190201R-Line 1 LLC (ORG-RL351-RIPE) · RUALLOCATED PAFeb 1, 2019r-line1@mail.ru
└ 171.22.212.0/23512R-LINE1-20190201unknownASSIGNED PAMar 6, 2024r-line1@mail.ru
via RU-RLINE1-20190201

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
Sep 2023
Current origin since
Sep 2023 · 3.2 yr
Origin networks
1