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

84.17.229.0/24

4 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
AS16256
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
13
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

218 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • GSocks
  • IPFly
  • NovaProxy
  • Novada
  • PROXYLANE
  • Proxiware
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.17.224.0/19
since May 2005
AS16256Residential17
2 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
84.17.224.0/198,192RU-MTU-20040804MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAAug 4, 2004abuse@mtu.ru
└ 84.17.224.0/212,048ReComMobile TeleSystems, OJSC, MR CenterASSIGNED PAAug 7, 2009abuse@mtu.ru
via RU-MTU-20040804

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 historyWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2018
Current origin since
Mar 2018 · 8.7 yr
Origin networks
1