Data as of Nov 10, 2026

91.103.76.0/23

2 residential-proxy exits · 30 days

JSC Rosin.telekom

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
2
0.39% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
22
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

453 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/22
since Dec 2019
AS24689Residential143
32 always on
JSC Rosin.telekom
91.103.72.0/21
since Dec 2006
AS24689Residential149
32 always on
JSC Rosin.telekom
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
91.103.76.0/24
since Sep 2016
AS24689ResidentialJSC Rosin.telekom
91.103.77.0/24
since Jun 2008
AS24689Residential2JSC 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.76.0/24256ROSINTEL-NETJSC Rosin.telekomASSIGNED PAAug 3, 2007abuse@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
Feb 2012
Current origin since
Dec 2019 · 6.9 yr
Origin networks
1