Data as of Nov 10, 2026
81.2.6.0/23
118 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
118
23% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
62
selling exits here
Oct 11, 2026 – Nov 9, 2026
Exits seen per day
5.8K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 81.2.6.0/24 | 0 | 62 | |
| 81.2.7.0/24 | 0 | 56 |
Proxy providers listing exits
- 711Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FastProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- IPFly
- IPPeak
- Infatica
- InfiniteProxies
- Kookey
- LemonLabs
- LemonPrime
- LudaxProxy
- MangoProxy
- MoMoProxy
- NodeProxy
- NovProxy
- NovaProxy
- PROXYON
- PROXYSCRAPE
- PROXYWING_BASIC
- PrivateProxy
- Proxio
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- SPYDERPROXY_PREMIUM
- Shifter
- VantageProxies
- VitalExclusive
- ZENPROXY_PREMIUM
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 81.2.0.0/19 since May 2005 | AS12332 | Residential | 580 2 always on | PJSC Rostelecom | |
| 81.2.0.0/18 since May 2005 | AS12332 | Residential | 1,293 2 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 |
|---|---|---|---|---|---|---|
| 81.2.0.0/18 | 16,384 | RU-RTK-20020304 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Mar 4, 2002 | abuse@ |
| └ 81.2.6.32/27 | 32 | POL-PRIMTECHNOPOLIS-NET | Primtechnopolis Co Ltd | ASSIGNED PA | May 7, 2003 | abuse@ via RU-RTK-20020304 |
| └ 81.2.6.64/26 | 64 | POL-PPPOE-NET-UNL | Dynamic Broadband Clients. | ASSIGNED PA | Jul 17, 2012 | abuse@ via RU-RTK-20020304 |
| └ 81.2.6.128/25 | 128 | POL-PPPOE-NET-UNL | Dynamic Broadband Clients. | ASSIGNED PA | Jul 17, 2012 | abuse@ via RU-RTK-20020304 |
| └ 81.2.7.0/24 | 256 | POL-PPPOE-NET-UNL | Dynamic Broadband Clients. | ASSIGNED PA | Jul 17, 2012 | abuse@ via RU-RTK-20020304 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
512 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 480 | 94% | 2 | |
| Business | 32 | 6.3% | 1 |
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
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Aug 2016
- Current origin since
- Aug 2016 · 10 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 81.2.6.0/23 | AS12389 | /23 | RIPE | RPKI valid |
| 81.2.0.0/19 | AS12332 | /24 | RIPE | Another network |
| 81.2.0.0/18 | AS12332 | /19 | RIPE | Another network |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Oct 25, 2018 |
Whois
Registration for this announcement
- Range
- 81.
2. 0. 0/ 18 - Netname
- RU-RTK-20020304
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Mar 4, 2002
- Updated
- Jun 22, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Mar 4, 2002
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE