Data as of Nov 7, 2026
82.215.78.0/23
14 residential-proxy exits · 30 daysJC LLC Sarkor-Telecom
Residential-proxy exits
Proxy exits
14
2.7% of its addresses · 30 days
Always-on exits
2
14% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
62
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
4.1K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 82.215.79.0/24 | 2 | 8 | |
| 82.215.78.0/24 | 0 | 6 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- B2Proxy
- BirdProxies
- BlurPath
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- DataImpulse
- Decodo
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- GSocks
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LudaxProxy
- MangoProxy
- MoMoProxy
- NextProxy
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyRack
- ProxyWing
- Proxyma
- PuraRoute
- Q2IP
- RapidProxy
- RolaProxy
- Shifter
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VibeProxies
- VitalData
- VitalExclusive
- Webshare
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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 82. | 1,792 | UZ-SARKOR-20031117 | JC LLC Sarkor-Telecom (ORG-SA72-RIPE) · UZ | ALLOCATED PA | Jun 17, 2020 | abuse@ |
| └ 82.215.78.0/23 | 512 | Dynamic-customer-PPPoE-pool-5 | unknown | ASSIGNED PA | Jun 17, 2020 | abuse@ via UZ-SARKOR-20031117 |
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
Registry
Holder
- Organization
- JC LLC Sarkor-Telecom
- Handle
- ORG-SA72-RIPE
- Range
- 82.
215. 77. 0 - 82. 215. 83. 255 - Registration type
- ALLOCATED PA
- Record created
- Jun 17, 2020
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Jun 2020
- Current origin since
- Mar 2024 · 2.7 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 82.215.78.0/23 | AS12365 | /23 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12365 | RIPE | Sarkor-Telecom Co, ISP in Uzbekistan | SARKOR-MNT | Jun 29, 2020 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 82.215.78.0/24 | AS12365 | RIPE | ISP Sarkor Telecom, Tashkent, Uzbekistan | SARKOR-MNT | Sep 17, 2020 |
| 82.215.79.0/24 | AS12365 | RIPE | ISP Sarkor Telecom, Tashkent, Uzbekistan | SARKOR-MNT | Sep 17, 2020 |
Whois
Registration for this announcement
- Range
- 82.
215. 78. 0/ 23 - Netname
- Dynamic-customer-PPPoE-pool-5
- Registrant country
- UZ
- Organization
- Not stated by the registry
- Type
- ASSIGNED PA
- Created
- Jun 17, 2020
- Updated
- Jun 17, 2020
- Maintainer
- SARKOR-MNT
- RIR
- RIPE NCC
- Country
- UZ
- Delegated
- Nov 17, 2003
- Status
- assigned
Report abuse
Abuse contact
- abuse@
sarkor. uz - Name
- Abuse-C Role
- Handle
- AR18039-RIPE