Data as of Nov 7, 2026
91.238.104.0/23
5 residential-proxy exits · 30 daysFOP 'Reznichenko Sergey Mykolayovich'
Residential-proxy exits
Proxy exits
5
0.98% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
19
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
707 observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 91.238.104.0/24 | 1 | 3 | |
| 91.238.105.0/24 | 0 | 1 |
Proxy providers listing exits
- BottingTools
- DataImpulse
- EZProxies
- GSocks
- GeekProxy
- GoProxies
- IPFly
- Novada
- PSBProxy
- PacketStream
- PrivateByte
- Proxmint
- Proxy4U
- ProxyRack
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- RoamProxy
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
91.238.104.0/23
From the registry to its use
- Apr 11, 2012Registry recordFOP "Reznichenko Sergey Mykolayovich"ASSIGNED PI91.238.104.0/23
- Apr 27, 2012Route objectAS50321 FOP 'Reznichenko Sergey Mykolayovich'RIPE route object for AS50321 FOP 'Reznichenko Sergey Mykolayovich', maintainer REZNICHENKO-MNT
- May 1, 2012– Jun 17, 2018
- Aug 5, 2018– today
- todayLeased fromInterLIRLessor
Network & registry
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2012
- Current origin since
- Aug 2018 · 8.3 yr
- Origin networks
- 1
Whois
Registration for this announcement
- Range
- 91.
238. 104. 0/ 23 - Netname
- BYTES-UA-DC
- Registrant
- FOP "Reznichenko Sergey Mykolayovich"
- Registrant country
- UA
- Organization
- FOP "Reznichenko Sergey Mykolayovich" (ORG-REZN1-RIPE)
- Org country
- UA
- Type
- ASSIGNED PI
- Created
- Apr 11, 2012
- Updated
- Aug 20, 2020
- Maintainer
- RIPE-NCC-END-MNT
- RIR
- RIPE NCC
- Country
- UA
- Delegated
- Apr 11, 2012
- Status
- assigned
Report abuse
Abuse contact
- reseni@
gmail. com - Name
- Abuse-C Role
- Handle
- AR30575-RIPE