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

213.87.96.0/24

4 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
RPKI valid
Announced by
AS39811
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
28
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

5.8K 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

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.87.0.0/16
since Jun 2016
AS8359Mobile1,056
155 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.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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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