Data as of Nov 17, 2026

213.87.80.0/20

6 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
6
0.15% of its addresses · 30 days
Spread
4 of 16
/24s with at least one exit
Providers
22
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

208 observations

/24s with the most always-on exits

Proxy providers listing exits

  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • Geonode
  • GhostConnect
  • HPROXY
  • HideProxy
  • IPFly
  • InfiniteProxies
  • LudaxProxy
  • NovaProxy
  • PROXYFALL
  • PROXYON
  • PROXYSAVER
  • PROXYSCRAPE
  • ProxyGeo
  • PuraRoute
  • SPYDERPROXY_BASIC
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.87.0.0/16
since Jun 2016
AS8359Mobile1,059
175 always on
MTS PJSC
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
213.87.80.0/22
since Apr 2026
AS8359Mobile1MTS PJSC
213.87.94.0/23
since Apr 2026
AS8359MobileMTS 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.80.0/204,096MTSGPRS-2Mobile subscribers poolASSIGNED PAJan 19, 2005abuse@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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Apr 2013 · 14 yr
Origin networks
2
Last change of origin
Apr 2013
Recorded history

History

Handoffs
1