Data as of Nov 19, 2026

84.18.101.0/24

2 residential-proxy exits · 30 days

PJSC 'Tattelecom'

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
27
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • Infatica
  • Kookey
  • LightningProxies
  • NodeMaven
  • Novada
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • Shifter
  • Smartproxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.18.100.0/23
since Jun 2021
AS28840Residential3PJSC "Tattelecom"
84.18.96.0/19
since May 2005
AS28840Residential2,750
3 always on
PJSC "Tattelecom"

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.18.96.0/198,192RU-TATTELECOM-20040812PJSC "Tattelecom" (ORG-OT4-RIPE) · RUALLOCATED PAAug 12, 2004adm-group@tattelecom.ru
└ 84.18.96.0/204,096TATTELECOMISP TATTELECOM, Russian Federation, city KazanASSIGNED PAMar 5, 2007adm-group@tattelecom.ru
via RU-TATTELECOM-20040812

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
Jun 2015
Current origin since
Jun 2015 · 11 yr
Origin networks
1