Data as of Nov 20, 2026

31.13.16.192/30

No anonymizer space · no proxy exits in 30 days

JSC 'ER-Telecom Holding'

Announcement
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
100% of its addresses · listed by providers
Providers
44
selling exits here

Proxy providers listing exits

  • 9HTTP
  • Ake.net
  • BUYPERSONALPROXY
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GhostConnect
  • GonzoProxy
  • HASDATA
  • HPROXY
  • HideProxy
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYSAVER
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • Smartproxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
31.13.16.0/212,048RU-RAID-20110418JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAOct 1, 2026abuse@domru.ru
└ 31.13.16.192/304NavigatorMoscow, Marksistskaya 22-3ASSIGNED PAApr 13, 2015abuse@domru.ru
via RU-RAID-20110418

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 31.13.16.0/21

31.13.16.0/21

Routing history

Pattern
Stable
First seen
Apr 2011
Current origin since
Apr 2011 · 16 yr
Origin networks
1