Data as of Nov 17, 2026

178.206.235.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
24
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

191 observations

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BottingTools
  • Byteful
  • CatProxies
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • GeekProxy
  • IPFly
  • IPRoyal
  • MarsProxies
  • NovaProxy
  • PSBProxy
  • PrivateByte
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • SpyderProxy
  • TrustProxy
  • VProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.206.224.0/19
since Dec 2010
AS28840Residential2,390
2 always on
PJSC "Tattelecom"
178.206.0.0/15
since Aug 2012
AS28840Residential38,392
23 always on
PJSC "Tattelecom"
178.204.0.0/14
since Dec 2010
AS28840Residential68,451
60 always on
PJSC "Tattelecom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.204.0.0/14262,144RU-TATTELECOM-20100331PJSC "Tattelecom" (ORG-OT4-RIPE) · RUALLOCATED PAMar 31, 2010adm-group@tattelecom.ru
└ 178.206.224.0/204,096TATARBROADBANDNETSKazan Broad-band access poolsASSIGNED PAMar 6, 2012adm-group@tattelecom.ru
via RU-TATTELECOM-20100331

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

178.206.224.0/20

Routing history

Pattern
Stable
First seen
Mar 2019
Current origin since
Mar 2019 · 7.7 yr
Origin networks
1