Data as of Nov 21, 2026

95.165.12.0/24

18 residential-proxy exits · 30 days

PJSC Moscow city telephone network

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

Residential-proxy exits

Proxy exits
18
7.0% of its addresses · 30 days
Always-on exits
2
11% of its exits
Providers
53
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

6.3K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPRoyal
  • Infatica
  • LemonLabs
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.165.0.0/1665,536RU-MGTS-20090127PJSC Moscow city telephone network (ORG-OMCT1-RIPE) · RUALLOCATED PAJan 27, 2009abuse@spd-mgts.ru
└ 95.165.0.0/1732,768MGTS-PPPOEMoscow Local Telephone Network (OAO MGTS)ASSIGNED PANov 27, 2009abuse@spd-mgts.ru
via RU-MGTS-20090127

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 95.165.0.0/16

95.165.0.0/16

Routing history

Pattern
Stable
First seen
Feb 2009
Current origin since
Feb 2009 · 18 yr
Origin networks
1