Data as of Nov 10, 2026

213.158.26.0/24

42 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
42
16% of its addresses · 30 days
Always-on exits
2
4.8% of its exits
Providers
56
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.9K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateByte
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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

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