Data as of Nov 18, 2026

213.80.248.0/21

3 residential-proxy exits · 30 days

Joint Stock Company TransTeleCom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
0.15% of its addresses · 30 days
Spread
2 of 8
/24s with at least one exit
Providers
27
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

225 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
213.80.248.0/2402
213.80.249.0/2401

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • GSocks
  • GonzoProxy
  • HydraProxy
  • IPFly
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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
213.80.128.0/1732,768RU-TRANSTELECOM-20010313Joint Stock Company TransTeleCom (ORG-CJSC19-RIPE) · RUALLOCATED PADec 14, 2001abuse@ttk.ru
└ 213.80.248.0/24256VTT-SMALLCORPSmall corporate clients of VTT, part VIII.7ASSIGNED PAJun 25, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20010313
└ 213.80.249.0/24256VTT-SMALLCORPSmall corporate clients of VTT, part VIII.8ASSIGNED PAFeb 12, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20010313
└ 213.80.250.0/24256VTT-SMALLCORPSmall corporate clients of VTTASSIGNED PAApr 29, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20010313
└ 213.80.251.0/24256VTT-SMALLCORPSmall corporate clients of VTTASSIGNED PAApr 29, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20010313
└ 213.80.252.0/24256VTT-SMALLCORPSmall corporate clients of VTTASSIGNED PAApr 29, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20010313

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Aug 2007
Current origin since
Nov 2012 · 14 yr
Origin networks
2
Last change of origin
Nov 2012
Recorded history

History

Handoffs
1