Data as of Nov 18, 2026

213.231.172.0/22

10 residential-proxy exits · 30 days

Rimex Ltd.

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

Residential-proxy exits

Proxy exits
10
0.98% of its addresses · 30 days
Always-on exits
1
10% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
35
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

796 observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • AETHYN_BASIC
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • BestProxy
  • BlurPath
  • BottingTools
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • FastProxy
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LudaxProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NovProxy
  • Proxies.fo
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.231.160.0/19
since Nov 2010
AS38932Residential38
10 always on
Rimex Ltd.

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.231.128.0/1816,384BG-RIMEX-LTD-20080211Rimex Ltd. (ORG-RL54-RIPE) · BGALLOCATED PAFeb 11, 2008abuse@rimex-ltd.com
└ 213.231.172.0/221,024BG-RIMEX-LTDRimex Ltd. clients spaceASSIGNED PANov 3, 2010abuse@rimex-ltd.com
via BG-RIMEX-LTD-20080211

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2010
Current origin since
Nov 2010 · 16 yr
Origin networks
1