Data as of Nov 11, 2026

91.103.74.0/23

5 residential-proxy exits · 30 days

JSC Rosin.telekom

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
5
0.98% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

411 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.103.72.0/22
since Feb 2012
AS24689Residential7JSC Rosin.telekom
91.103.72.0/21
since Dec 2006
AS24689Residential147
29 always on
JSC Rosin.telekom
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
91.103.74.0/24
since Sep 2016
AS24689ResidentialJSC Rosin.telekom
91.103.75.0/24
since Sep 2016
AS24689Residential5JSC Rosin.telekom

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
91.103.72.0/212,048RU-ROSINTEL-20061123JSC Rosin.telekom (ORG-JR11-RIPE) · RUALLOCATED PANov 23, 2006abuse@rosintel.com
└ 91.103.72.0/221,024ROSINTEL-NETJSC Rosin.telekomASSIGNED PANov 23, 2006abuse@rosintel.com
via RU-ROSINTEL-20061123

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

Summary

Routing history

Pattern
Stable
First seen
Jul 2007
Current origin since
Jul 2007 · 19 yr
Origin networks
1