LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

176.102.68.0/22

11 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
11
1.1% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
21
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

240 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
176.102.68.0/2408
176.102.69.0/2401
176.102.70.0/2401
176.102.71.0/2401

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • BlurPath
  • BottingTools
  • Byteful
  • CROXY
  • CliProxy
  • Geonode
  • IPFly
  • IPPeak
  • InfiniteProxies
  • NSocks
  • PrivateProxy
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ZENPROXY_PREMIUM

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
176.102.68.0/221,024RU-MTU-20180703MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 29, 2025abuse@mtu.ru
└ 176.102.68.0/23512SISTEMY-SVYAZI-NETunknownASSIGNED PADec 7, 2018abuse@mtu.ru
via RU-MTU-20180703

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2018
Current origin since
Dec 2018 · 7.9 yr
Origin networks
1