Data as of Nov 18, 2026

62.118.131.0/24

4 residential-proxy exits · 30 days

MTS PJSC

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
31
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.118.0.0/16
since May 2005
AS8359Mobile2,073
165 always on
MTS PJSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
62.118.0.0/1665,536RU-MTU-20000911MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMar 19, 2002abuse@mtu.ru
└ 62.118.128.0/212,048VNOV-users-20071120ZAO MTU-IntelASSIGNED PAJul 29, 2013abuse@mtu.ru
via RU-MTU-20000911

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

62.118.128.0/19

Routing history

Pattern
Stable
First seen
Nov 2011
Current origin since
Sep 2021 · 5.1 yr
Origin networks
2
Last change of origin
Sep 2021
Recorded history

History

Handoffs
2