Data as of Nov 17, 2026

77.43.144.0/22

6 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
33
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
77.43.144.0/2405
77.43.146.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.43.128.0/17
since Oct 2025
AS8359Mobile7,779
288 always on
MTS PJSC

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
77.43.128.0/1732,768RU-MTU-20061208MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 8, 2006abuse@mtu.ru
└ 77.43.144.0/221,024CCL-PPPOE01For PPPoE CustomersASSIGNED PASep 1, 2015abuse@mtu.ru
via RU-MTU-20061208

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jul 2007
Current origin since
Jul 2007 · 19 yr
Origin networks
1