Data as of Nov 12, 2026

46.38.4.0/22

3 residential-proxy exits · 30 days

Joint Stock Company TransTeleCom

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

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
26
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.38.4.0/2412
46.38.6.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • GloryCloud
  • GonzoProxy
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • StrikeProxy
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.38.0.0/19
since May 2016
AS20485Residential1,023
10 always on
Joint Stock Company TransTeleCom

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
46.38.0.0/198,192RU-TRANSTELECOM-20101122Joint Stock Company TransTeleCom (ORG-CJSC19-RIPE) · RUALLOCATED PANov 22, 2010abuse@ttk.ru
└ 46.38.4.0/221,024TTKDV-RTL-DYNAMIC-2L2TP customers (dynamic ip address pool)ASSIGNED PADec 28, 2010abuse@ttk.ru
via RU-TRANSTELECOM-20101122

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
Feb 2011
Current origin since
Feb 2021 · 5.7 yr
Origin networks
1