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

178.141.0.0/16

7,206 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
RPKI valid
Announced by
AS8359
Type
Residential

Residential-proxy exits

Proxy exits
7,206
11% of its addresses · 30 days
Always-on exits
43
0.60% of its exits
Spread
238 of 256
/24s with at least one exit
Providers
133
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

885K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.141.224.0/2414255
178.141.244.0/2413254
178.141.242.0/247251
178.141.243.0/242253
178.141.227.0/241255
178.141.17.0/24151
178.141.246.0/24124
178.141.253.0/2419
178.141.80.0/2414
178.141.255.0/2412
178.141.232.0/2411
178.141.226.0/240255
178.141.225.0/240254
178.141.24.0/24072
178.141.15.0/24071
178.141.28.0/24070
178.141.1.0/24068
178.141.25.0/24067
178.141.31.0/24067
178.141.2.0/24066
178.141.30.0/24065
178.141.18.0/24064
178.141.29.0/24063
178.141.3.0/24062

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • FuseProxy
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • TrustProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • 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
178.141.0.0/1665,536RU-MTU-20100422MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAApr 22, 2010abuse@mtu.ru
└ 178.141.0.0/212,048MTS-KRV-PPPOE-1-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.8.0/212,048MTS-KRV-PPPOE-2-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.16.0/212,048MTS-KRV-PPPOE-3-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.24.0/212,048MTS-KRV-PPPOE-4-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.32.0/212,048MTS-KRV-PPPOE-5-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.40.0/212,048MTS-KRV-PPPOE-6-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.48.0/212,048MTS-KRV-PPPOE-7-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.56.0/212,048MTS-KRV-PPPOE-8-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.64.0/212,048MTS-KRV-PPPOE-9-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.72.0/212,048MTS-KRV-PPPOE-10-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.80.0/24256MTS-KRV-PPPOE-80-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAApr 1, 2015abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.81.0 - 178.141.87.2551,792MTS-KRV-PPPOE-11-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAApr 1, 2015abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.88.0/212,048MTS-KRV-PPPOE-12-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.96.0/212,048MTS-KRV-PPPOE-13-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.104.0/212,048MTS-KRV-PPPOE-14-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.112.0/212,048MTS-KRV-PPPOE-15-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.120.0/212,048MTS-KRV-PPPOE-20-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.128.0/212,048MTS-KRV-PPPOE-21-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.136.0/212,048MTS-KRV-PPPOE-22-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.144.0/212,048MTS-KRV-PPPOE-23-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.152.0/212,048MTS-KRV-PPPOE-24-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.160.0/212,048MTS-KRV-PPPOE-25-NETMobile TeleSystems PJSC, Kirov branchASSIGNED PAFeb 21, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.168.0/212,048MTS-KRV-PPPOE-26-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.176.0/212,048MTS-KRV-PPPOE-27-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.184.0/212,048MTS-KRV-PPPOE-28-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.192.0/212,048MTS-KRV-PPPOE-29-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.200.0/212,048MTS-KRV-PPPOE-30-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.208.0/212,048MTS-KRV-PPPOE-31-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.216.0/212,048MTS-KRV-PPPOE-32-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.224.0/212,048MTS-KRV-PPPOE-33-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.232.0/212,048MTS-KRV-PPPOE-34-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.240.0/212,048MTS-KRV-PPPOE-35-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.248.0/23512MTS-KRV-ETH-36-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 20, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.250.0/23512MTS-KRV-ETH-37-NETMobile Telesystems PJSC, Kirov branchASSIGNED PAAug 26, 2014abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.253.0 - 178.141.254.255512MTS-KRV-PPPOE-254-NETMobile Telesystems PJSC, Kirov branchASSIGNED PANov 28, 2013abuse@mtu.ru
via RU-MTU-20100422
└ 178.141.255.128/25128MTS-KRV-ETH-255-NETMobile Telesystems OJSC, Kirov branchASSIGNED PAMar 25, 2015abuse@mtu.ru
via RU-MTU-20100422

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
May 2010
Current origin since
Aug 2020 · 6.3 yr
Origin networks
2
Last change of origin
Aug 2020
Recorded history

History

Handoffs
1