Data as of Nov 17, 2026

62.220.58.0/24

3 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
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
24
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • FlashProxy
  • IPFly
  • IPOasis
  • IPRoyal
  • Oxylabs
  • PrivateByte
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy4U
  • ProxyRack
  • Q2IP
  • StrikeProxy
  • ThunderProxy
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.220.56.0/22
since Dec 2010
AS41209Residential4
1 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
62.220.32.0/198,192RU-MTU-20081016MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAOct 16, 2008abuse@mtu.ru
└ 62.220.56.0/221,024CMST-SAMARA-2010112500Samarsky CSC of Privolgsky macro branch JSC "Comstar-Region"ASSIGNED PAAug 23, 2017abuse@mtu.ru
via RU-MTU-20081016

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
Mar 2012
Current origin since
Mar 2012 · 15 yr
Origin networks
1