Data as of Nov 18, 2026

213.231.162.0/24

2 residential-proxy exits · 30 days

Rimex Ltd.

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
24
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

687 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • ASHBURNPROXIES
  • BestProxy
  • BottingTools
  • DataImpulse
  • GeekProxy
  • IPFly
  • LUMIPROXY
  • NSocks
  • NiuProxy
  • PSBProxy
  • PrivateByte
  • Proxies.fo
  • Proxmint
  • Proxy4U
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Smartproxy
  • VProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.231.160.0/19
since Nov 2010
AS38932Residential37
9 always on
Rimex Ltd.

Registrations in this block

The registry's network records over this block, widest first, each 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.160.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

213.231.160.0/22

Routing history

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