Data as of Nov 22, 2026

217.112.31.0/25

11 residential-proxy exits · 30 days

PJSC Moscow city telephone network

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

Residential-proxy exits

Proxy exits
11
8.6% of its addresses · 30 days
Providers
42
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

5.0K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HydraProxy
  • IPFly
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.112.16.0/204,096RU-MGTS-20030820PJSC Moscow city telephone network (ORG-OMCT1-RIPE) · RUALLOCATED PAAug 20, 2003abuse@spd-mgts.ru
└ 217.112.31.0/25128CNIITMASH-NETPJSC RPA "Cniitmash"ASSIGNED PAAug 31, 2005abuse@spd-mgts.ru
via RU-MGTS-20030820

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 217.112.16.0/20

217.112.16.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Nov 2019 · 7.0 yr
Origin networks
2
Last change of origin
Nov 2019
Recorded history

History

Handoffs
1