Data as of Nov 14, 2026
5.141.228.0/23
97 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
97
19% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
63
selling exits here
Oct 15, 2026 – Nov 13, 2026
Exits seen per day
2.7K observations
Proxy providers listing exits
- 9Proxy
- Ake.net
- AnyIP
- BartProxies
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- HPROXY
- HideProxy
- IPFly
- IPPeak
- IPROCKET_BASIC
- Infatica
- InfiniteProxies
- KindProxy
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- NextProxy
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- PROXYLANE
- PROXYON
- PROXYSCRAPE
- PrivateProxy
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- ProxyWing
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- SPYDERPROXY_BASIC
- Shifter
- VantageProxies
- VitalExclusive
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 5.136.0.0/13 since Sep 2018 | AS12389 | Residential | 115,270 867 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 | abuse@ |
| └ 5.141.0.0/16 | 65,536 | Ural_ | unknown | LIR-PARTITIONED PA | Dec 1, 2022 | abuse@ via RU-RTK-20120703 |
| └ 5. | 2,304 | Urals_ | unknown | ASSIGNED PA | Dec 1, 2022 | abuse@ 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
- Mar 2014
- Current origin since
- Aug 2017 · 9.2 yr
- Origin networks
- 2
- Last change of origin
- Aug 2017
Recorded history
History
- Handoffs
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 5.141.228.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. 224. 0 - 5. 141. 232. 255 - Netname
- Urals_
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
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE