Data as of Nov 19, 2026

213.178.56.0/21

68 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Residential
77% of it

Residential-proxy exits

Proxy exits
68
3.3% of its addresses · 30 days
Always-on exits
2
2.9% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
95
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

4.6K observations
  • Residential
  • Business

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HASDATA
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LOKIPROXY
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TORCHPROXIES_PREMIUM
  • Thordata
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.56.192/2664AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAJan 20, 2010abuse@rt.ru
via RU-RTK-20080117
└ 213.178.57.176/2816AIST-AVIAOTELAIST ISP, Client AviaOtelASSIGNED PADec 9, 2011abuse@rt.ru
via RU-RTK-20080117
└ 213.178.57.208/2816AISTNETAIST ISP, ClientsASSIGNED PAJan 20, 2010abuse@rt.ru
via RU-RTK-20080117
└ 213.178.58.32/2732AISTNETAIST ISP, Clients. Core 005, TA 008ASSIGNED PAJan 23, 2009abuse@rt.ru
via RU-RTK-20080117
└ 213.178.59.0/25128AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAApr 11, 2012abuse@rt.ru
via RU-RTK-20080117
└ 213.178.59.192/2664AISTNETAIST ISP, Clients. Core 005, TA 008ASSIGNED PAJan 20, 2010abuse@rt.ru
via RU-RTK-20080117
└ 213.178.62.0/2732AISTNETAIST ISP, Core 5, AggregationASSIGNED PAFeb 9, 2011abuse@rt.ru
via RU-RTK-20080117
└ 213.178.62.32/2732AISTNETAIST ISP, Core 4, AggregationASSIGNED PAJan 23, 2009abuse@rt.ru
via RU-RTK-20080117
└ 213.178.62.64/2816AISTNETAIST ISP, Core 1, AggregationASSIGNED PAJan 23, 2009abuse@rt.ru
via RU-RTK-20080117
└ 213.178.62.128/2664AISTNETAIST ISP, Clients. Core 001, TA 020ASSIGNED PAJan 23, 2009abuse@rt.ru
via RU-RTK-20080117
└ 213.178.63.224/2732AISTNETAIST ISP, ClientsASSIGNED 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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

2,048 addresses
TypeAddressesShareRanges
Residential1,56877%8
Business48023%10

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