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

93.90.233.0/24

6 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
39
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

4.2K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • BestProxy
  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • IPFly
  • IPOasis
  • IPPeak
  • InfiniteProxies
  • LUMIPROXY
  • NSocks
  • NiuProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyStyler
  • Proxying
  • PuraRoute
  • RainProxy
  • RealProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.232.0/212,048UTC_HOMENETdynamic-pool 2ASSIGNED PAMay 8, 2008abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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