Data as of Nov 17, 2026

93.90.228.0/22

5 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
5
0.49% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
38
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

1.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
93.90.228.0/2413
93.90.230.0/2401
93.90.231.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • LudaxProxy
  • Maskify
  • NodeMaven
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Q2IP
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
93.90.224.0/204,096RU-MTU-20080424MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAApr 24, 2008abuse@mtu.ru
└ 93.90.228.0/221,024b2b_ekaterinburgunknownASSIGNED PANov 22, 2022abuse@mtu.ru
via RU-MTU-20080424

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

Who has announced 93.90.224.0/20

93.90.224.0/20

Routing history

Pattern
Rotating
First seen
May 2008
Current origin since
Feb 2024 · 2.7 yr
Origin networks
2
Last change of origin
Feb 2024
Recorded history

History

Handoffs
1