Data as of Nov 10, 2026

95.55.236.0/24

24 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
24
9.4% of its addresses · 30 days
Providers
38
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

687 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonix
  • Geonode
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.52.0.0/14
since Sep 2018
AS12389Residential32,760
1,921 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.52.0.0/14262,144RU-RTK-20081113PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 13, 2008abuse@rt.ru
└ 95.55.224.0/198,192RU-AVANGARD-DSLOJSC "North-West Telecom"ASSIGNED PAMay 13, 2009abuse@rt.ru
via RU-RTK-20081113

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

Covering aggregate above, the prefix's own history below

95.55.192.0/18

Routing history

Pattern
Stable
First seen
Dec 2009
Current origin since
Jan 2017 · 9.8 yr
Origin networks
2
Last change of origin
Jan 2017
Recorded history

History

Handoffs
1