Data as of Nov 16, 2026

213.178.53.0/24

36 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
36
14% of its addresses · 30 days
Providers
48
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.0K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GEEKPROXY_TURBO
  • GSocks
  • GhostConnect
  • GonzoProxy
  • HASDATA
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.178.32.0/198,192RU-RTK-20080117PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 14, 2022abuse@rt.ru
└ 213.178.53.0/24256AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAJan 20, 2010abuse@rt.ru
via RU-RTK-20080117

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 213.178.48.0/20

213.178.48.0/20

Routing history

Pattern
Stable
First seen
Sep 2010
Current origin since
Sep 2010 · 16 yr
Origin networks
1