Data as of Nov 10, 2026
213.158.0.0/20
57 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
57
1.4% of its addresses · 30 days
Always-on exits
4
7.0% of its exits
Spread
2 of 16
/24s with at least one exit
Providers
75
selling exits here
Oct 11, 2026 – Nov 9, 2026
Exits seen per day
7.5K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 213.158.1.0/24 | 4 | 17 | |
| 213.158.14.0/24 | 0 | 40 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- Ake.net
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GonzoProxy
- HPROXY
- IPFly
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- LUMIPROXY
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Oxylabs
- PROXYON
- PROXYSCRAPE
- PrivateProxy
- ProxiesVision
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RealProxy
- Shifter
- Smartproxy
- Thordata
- VantageProxies
- VibeProxies
- VitalExclusive
- VitalProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 213.158.1.0/24 since Nov 2018 | AS12389 | Residential | 17 4 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 |
|---|---|---|---|---|---|---|
| 213.158.0.0/19 | 8,192 | RU-RTK-19991220 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Sep 13, 2002 | abuse@ |
| └ 213.158.0.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.1.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.2.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.3.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.4.0/24 | 256 | SPBTLG | PJSC "Rostelecom" | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.5.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.6.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.7.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.8.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.9.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.10.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.11.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.12.0/24 | 256 | SPBTLG | PJSC "Rostelecom" | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.13.0/24 | 256 | SPBTLG | PJSC "Rostelecom" | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.14.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
| └ 213.158.15.0/24 | 256 | SPBTLG | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 7, 2019 | abuse@ via RU-RTK-19991220 |
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
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
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- Dec 2018 · 7.9 yr
- Origin networks
- 3
- Last change of origin
- Dec 2018
Recorded history
History
- Handoffs
- 2
Whois
Registration for this announcement
- Range
- 213.
158. 0. 0/ 19 - Netname
- RU-RTK-19991220
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Sep 13, 2002
- Updated
- Jun 4, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Dec 20, 1999
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE