Data as of Nov 21, 2026

213.27.0.0/17

118 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
98% of it

Residential-proxy exits

Proxy exits
118
0.36% of its addresses · 30 days
Always-on exits
12
10% of its exits
Spread
32 of 128
/24s with at least one exit
Providers
123
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

29K observations
  • Mobile
  • Business

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BUYPERSONALPROXY
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CROXY
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LOKIPROXY
  • LUMIPROXY
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSALE
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXY_CC
  • PYPROXY
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
213.27.24.0/23
since Apr 2026
AS8359Business28
7 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
213.27.0.0/1732,768RU-MTU-20021216MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 16, 2002abuse@mtu.ru
└ 213.27.0.0/198,192ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PADec 17, 2002abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.32.0/24256AAA-Azov-NETIP address space for Azov branch of Digital Telephone CommunicationsASSIGNED PAJun 7, 2004abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.33.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PADec 6, 2004abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.34.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PADec 6, 2004abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.35.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PADec 6, 2004abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.36.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAJan 25, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.37.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAJan 25, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.38.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAJan 25, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.39.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworksASSIGNED PAJan 25, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.40.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAJan 25, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.41.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAJan 25, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.42.0/23512CTSRND-NETIP address space for Digital Telephone Lines Ltd corporative Network, Rostov-on-Don, RussiaASSIGNED PAApr 7, 2008abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.44.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PANov 28, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.45.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PANov 28, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.46.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PANov 28, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.47.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PANov 28, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.48.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PANov 28, 2005abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.49.0 - 213.27.80.2558,192ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAJan 6, 2007abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.81.0/24256Teleline-tv-RostovJSC Telecompany Tv-MaydanASSIGNED PAJan 24, 2006abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.82.0/23512TAGANROG-GSPD-NETIP address space for TAganog MANASSIGNED PANov 28, 2006abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.84.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAApr 9, 2007abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.85.0/24256ROSTOV-GSPD-NETAddress space for Rostov-on-Don MANASSIGNED PAApr 1, 2009abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.86.0/24256Rostov-GSPD-NETRostov-GSPD-NETASSIGNED PAApr 2, 2009abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.87.0 - 213.27.89.255768ROSTOV-GSPD-NETAddress space for Rostov-on-Don MANASSIGNED PAApr 1, 2009abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.90.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAMar 21, 2007abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.91.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAMar 19, 2007abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.92.0/24256ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAFeb 9, 2007abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.93.0/24256COMTEL-TAGANROG-NETComtel-Taganrog Ltd. Taganrog City, Rostov-on-Don regionASSIGNED PAFeb 19, 2007abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.94.0/23512TAGANROG-GSPD-NETIP address space for Taganrog MANASSIGNED PANov 28, 2006abuse@mtu.ru
via RU-MTU-20021216
└ 213.27.96.0/198,192ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAJan 24, 2007abuse@mtu.ru
via RU-MTU-20021216

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

32,768 addresses
TypeAddressesShareRanges
Mobile32,25698%2
Business5121.6%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2025
Current origin since
Apr 2025 · 1.6 yr
Origin networks
1