Data as of Nov 3, 2026
212.3.136.0/22
283 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
283
28% of its addresses · 30 days
Always-on exits
121
43% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
74
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
196K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 212.3.139.0/24 | 116 | 256 | |
| 212.3.137.0/24 | 4 | 9 | |
| 212.3.136.0/24 | 1 | 17 | |
| 212.3.138.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- Bright Data
- ByteProxies
- Byteful
- CliProxy
- CoreProxy
- DataImpulse
- Decodo
- EnigmaProxy
- Evomi
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GoProxies
- GonzoProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LightningProxies
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NiuProxy
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- PacketStream
- PrivateProxy
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- Shifter
- Smartproxy
- StrikeProxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
Registrations in this block
The registry's network records over this block, widest first, each under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 212.3.128.0/19 | 8,192 | RU-RTK-20050607 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jun 7, 2005 | [email protected] |
| └ 212.3.136.0/22 | 1,024 | MACROREGIONAL_CENTER | OJSC Rostelecom, Smolensk branch | ASSIGNED PA | Oct 21, 2025 | [email protected] via RU-RTK-20050607 |
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
Announced by
Covering announcement 212.3.128.0/19
- Prefix
- 212.3.128.0/19
- Announced by
- AS35125 PJSC Rostelecom
- Type
- Residential
- Proxy exits
- 2,170
- Always-on exits
- 1,018
- RPKI
- RPKI valid
- Netname
- RU-RTK-20050607
- Registrant
- PJSC Rostelecom
- RIR
- RIPE NCC
Origin network
AS35125
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Jun 7, 2005
- Domain
- rostelecom.ru
- Industry
- Computer and Information Technology
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced 212.3.128.0/19
212.3.128.0/19
Routing history
- Pattern
- Stable
- First seen
- Aug 2005
- Current origin since
- Aug 2005 · 21 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 212.3.128.0/19 | AS35125 | /19 | RIPE | RPKI valid |
IRR
Route objects on 212.3.128.0/19
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS35125 | RIPE | Smolensk branch of the PJSC Rostelecom | ROSTELECOM-MNT | Dec 23, 2024 |
Whois
Registration for this announcement
- Range
- 212.3.128.0/19
- Netname
- RU-RTK-20050607
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jun 7, 2005
- Updated
- May 25, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jun 7, 2005
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE