Data as of Nov 11, 2026

91.103.77.0/24

2 residential-proxy exits · 30 days

JSC Rosin.telekom

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
22
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

465 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • GSocks
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.103.76.0/23
since Dec 2019
AS24689Residential2JSC Rosin.telekom
91.103.76.0/22
since Dec 2019
AS24689Residential140
29 always on
JSC Rosin.telekom
91.103.72.0/21
since Dec 2006
AS24689Residential147
29 always on
JSC 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.77.0 - 91.103.79.255768ROSINTEL-NETJSC Rosin.telekomASSIGNED PAMay 12, 2010abuse@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
Jun 2008
Current origin since
Jun 2008 · 18 yr
Origin networks
1