Data as of Nov 18, 2026

213.87.96.0/23

4 residential-proxy exits · 30 days

MTS PJSC

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
1 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

8.5K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • IPFly
  • InfiniteProxies
  • NSocks
  • NiuProxy
  • Novada
  • PrivateProxy
  • Proxy-Cheap
  • ProxyEmpire
  • ProxyWing
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
213.87.96.0/24
since Aug 2016
AS39811Residential4
1 always on
MTS PJSC
213.87.97.0/24
since May 2008
AS39811ResidentialMTS PJSC

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.87.0.0/1665,536RU-MTU-20000410MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 14, 2001abuse@mtu.ru
└ 213.87.96.0/23512MTSNET-VLDVladivostok (Far East) division of Mobile Telesystems OJSCASSIGNED PAApr 4, 2006abuse@mtu.ru
via RU-MTU-20000410

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 213.87.0.0/16

213.87.0.0/16

Routing history

Pattern
Stable
First seen
Jun 2016
Current origin since
Jun 2016 · 10 yr
Origin networks
1