Data as of Nov 3, 2026
5.136.8.0/21
439 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
439
21% of its addresses · 30 days
Always-on exits
10
2.3% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
89
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
29K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 5.136.14.0/24 | 4 | 62 | |
| 5.136.15.0/24 | 2 | 67 | |
| 5.136.13.0/24 | 2 | 48 | |
| 5.136.8.0/24 | 1 | 58 | |
| 5.136.9.0/24 | 1 | 48 | |
| 5.136.12.0/24 | 0 | 53 | |
| 5.136.11.0/24 | 0 | 52 | |
| 5.136.10.0/24 | 0 | 47 |
Proxy providers listing exits
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PrivateByte
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 5.136.0.0/15 since Aug 2016 | AS12389 | Residential | 22,927 216 always on | PJSC Rostelecom | |
| 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.136.0.0/17 | 32,768 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jul 16, 2012 | [email protected] via RU-RTK-20120703 |
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
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
- Jan 2024
- Current origin since
- Jan 2024 · 2.8 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 5.136.8.0/21 | AS12389 | /21 | RIPE | RPKI valid |
| 5.136.0.0/15 | AS12389 | /15 | RIPE | Too specific |
| 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-MNT | Feb 24, 2025 |
Whois
Registration for this announcement
- Range
- 5.136.0.0/17
- Netname
- WEBSTREAM
- Registrant
- OJSC "Sibirtelecom"
- Registrant country
- RU
- Organization
- OJSC "Sibirtelecom"
- Org country
- RU
- Type
- ASSIGNED PA
- Created
- Jul 16, 2012
- Updated
- Jul 2, 2025
- 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