Data as of Nov 16, 2026

78.138.145.0/24

3 residential-proxy exits · 30 days

PJSC 'Tattelecom'

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
22
selling exits here
Oct 17, 2026 – Nov 14, 2026

Exits seen per day

57 observations

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • Byteful
  • Evomi
  • GSocks
  • GhostConnect
  • HPROXY
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • NodeProxy
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • PuraRoute
  • SPYDERPROXY_BASIC
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
78.138.144.0/20
since Nov 2017
AS28840Residential70
3 always on
PJSC "Tattelecom"
78.138.128.0/19
since Feb 2009
AS28840Residential143
7 always on
PJSC "Tattelecom"
78.138.128.0/18
since Jul 2008
AS28840Residential1,442
19 always on
PJSC "Tattelecom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
78.138.128.0/1816,384RU-TATTELECOM-20070611PJSC "Tattelecom" (ORG-OT4-RIPE) · RUALLOCATED PAJun 11, 2007adm-group@tattelecom.ru
└ 78.138.128.0/198,192TATARBROADBANDNETSKazan Broad-band access poolsASSIGNED PAFeb 5, 2010adm-group@tattelecom.ru
via RU-TATTELECOM-20070611

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

78.138.144.0/21

Routing history

Pattern
Stable
First seen
Feb 2024
Current origin since
Feb 2024 · 2.7 yr
Origin networks
1