Data as of Nov 20, 2026

194.135.4.0/22

5 residential-proxy exits · 30 days

PJSC Moscow city telephone network

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
28
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

511 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
194.135.7.0/2403
194.135.5.0/2402

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • Smartproxy
  • VitalExclusive

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
194.135.4.0 - 194.135.15.2553,072RU-MGTS-19950206PJSC Moscow city telephone network (ORG-OMCT1-RIPE) · RUALLOCATED PASep 12, 2014abuse@spd-mgts.ru
└ 194.135.4.0/221,024RU-MGTS-RFCPJSC Moscow city telephone network (ORG-OMCT1-RIPE) · RUSUB-ALLOCATED PASep 18, 2014abuse@spd-mgts.ru

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2014
Current origin since
Sep 2014 · 12 yr
Origin networks
1