Data as of Nov 3, 2026
5.141.82.0/23
25 residential-proxy exits · 30 daysPJSC Rostelecom
Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby
Residential-proxy exits
Proxy exits
25
4.9% of its addresses · 30 days
Always-on exits
5
20% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
45
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
7.2K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 5.141.82.0/24 | 3 | 22 | |
| 5.141.83.0/24 | 2 | 3 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- BestProxy
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- EZProxies
- EnigmaProxy
- Evomi
- FlashProxy
- GSocks
- Geonix
- GhostConnect
- GonzoProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- InfiniteProxies
- LightningProxies
- MangoProxy
- NSocks
- NiuProxy
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyHat
- Proxyma
- PuraRoute
- RainProxy
- RoamProxy
- Shifter
- Smartproxy
- VantageProxies
- VibeProxies
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 5.136.0.0/13 since Sep 2018 | AS12389 | Residential | 113,295 1,204 always on | PJSC Rostelecom |
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 |
|---|---|---|---|---|---|---|
| 5.136.0.0/13 | 524,288 | RU-RTK-20120703 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jul 3, 2012 | [email protected] |
| └ 5.141.0.0/16 | 65,536 | Ural_Branch | unknown | LIR-PARTITIONED PA | Dec 1, 2022 | [email protected] via RU-RTK-20120703 |
| └ 5.141.0.0/17 | 32,768 | Ural_Branch | unknown | ASSIGNED PA | Dec 1, 2022 | [email protected] via Ural_Branch |
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
IPv4 market
Holder
- Organization
- PJSC Rostelecom
- Handle
- ORG-JR8-RIPE
- Range
- 5.136.0.0/13
- Registration type
- ALLOCATED PA
- Record created
- Jul 3, 2012
- Reallocated to
- Not named in the registry
- Reallocated range
- 5.141.0.0/16
- Reallocation type
- LIR-PARTITIONED PA
- Reallocated
- Dec 1, 2022
Origin network
AS12389
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Jul 1, 2005
- Domain
- rt.ru
- Website
- www.company.rt.ru/en/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Nov 2013
- Current origin since
- Nov 2017 · 8.9 yr
- Origin networks
- 2
- Last change of origin
- Nov 2017
Recorded history
History
- Handoffs
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 5.141.82.0/23 | AS12389 | /23 | RIPE | RPKI valid |
| 5.136.0.0/13 | AS12389 | /24 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Oct 9, 2018 |
Whois
Registration for this announcement
- Range
- 5.141.0.0/17
- Netname
- Ural_Branch
- Registrant country
- RU
- Organization
- Not stated by the registry
- Type
- ASSIGNED PA
- Created
- Dec 1, 2022
- Updated
- Jun 5, 2024
- Maintainer
- ROSTELECOM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jul 3, 2012
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE