Data as of Nov 9, 2026
88.215.160.0/19
226 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
226
2.8% of its addresses · 30 days
Spread
12 of 32
/24s with at least one exit
Providers
84
selling exits here
Oct 10, 2026 – Nov 8, 2026
Exits seen per day
9.9K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 88.215.182.0/24 | 0 | 106 | |
| 88.215.186.0/24 | 0 | 98 | |
| 88.215.176.0/24 | 0 | 4 | |
| 88.215.183.0/24 | 0 | 4 | |
| 88.215.160.0/24 | 0 | 3 | |
| 88.215.165.0/24 | 0 | 3 | |
| 88.215.179.0/24 | 0 | 2 | |
| 88.215.162.0/24 | 0 | 1 | |
| 88.215.173.0/24 | 0 | 1 | |
| 88.215.175.0/24 | 0 | 1 | |
| 88.215.180.0/24 | 0 | 1 | |
| 88.215.190.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- 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
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYWING_BASIC
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_PREMIUM
- Shifter
- StrikeProxy
- SwiftProxy
- Thordata
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- ZENPROXY_PREMIUM
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 88.215.182.0/24 since Aug 2015 | AS12389 | Residential | 106 | PJSC Rostelecom | |
| 88.215.186.0/24 since Aug 2015 | AS12389 | Residential | 98 | PJSC Rostelecom |
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 |
|---|---|---|---|---|---|---|
| 88.215.128.0/18 | 16,384 | RU-RTK-20060124 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jan 24, 2006 | abuse@ |
| └ 88.215.160.0/19 | 8,192 | Macroregional_ | OJSC Rostelecom Macroregional Branch South | ASSIGNED PA | May 17, 2012 | abuse@ via RU-RTK-20060124 |
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 88.215.128.0/18
- Prefix
- 88.215.128.0/18
- Announced by
- AS12683 PJSC Rostelecom
- Type
- Residential
- Proxy exits
- 273
- RPKI
- RPKI valid
- Netname
- RU-RTK-20060124
- Registrant
- PJSC Rostelecom
- RIR
- RIPE NCC
Origin network
AS12683
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Sep 27, 1999
- Domain
- rostelecom.ru
- Industry
- Computer and Information Technology
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced 88.215.128.0/18
88.215.128.0/18
Routing history
- Pattern
- Stable
- First seen
- Feb 2006
- Current origin since
- Feb 2006 · 21 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 88.215.128.0/18 | AS12683 | /18 | RIPE | RPKI valid |
IRR
Route objects on 88.215.128.0/18
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12683 | RIPE | Multihomed AS talking to AS8342 and AS20485 | ROSTELECOM-MNT | Dec 10, 2024 |
Whois
Registration for this announcement
- Range
- 88.
215. 128. 0/ 18 - Netname
- RU-RTK-20060124
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jan 24, 2006
- Updated
- Jun 23, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jan 24, 2006
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE