LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

213.158.22.0/24

9 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
1
11% of its exits
Providers
42
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

3.4K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.158.0.0/198,192RU-RTK-19991220PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 13, 2002abuse@rt.ru
└ 213.158.16.0/204,096ATNET-RUOJSC "North-West Telecom"ASSIGNED PAJun 16, 2004abuse@rt.ru
via RU-RTK-19991220

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 213.158.16.0/20

213.158.16.0/20

Routing history

Pattern
Rotating
First seen
May 2005
Current origin since
Oct 2023 · 3.1 yr
Origin networks
3
Last change of origin
Oct 2023
Recorded history

History

Handoffs
4