Data as of Nov 3, 2026
80.246.72.0/21
523 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
523
26% of its addresses · 30 days
Always-on exits
3
0.57% 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
90K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 80.246.73.0/24 | 2 | 12 | |
| 80.246.76.0/24 | 1 | 22 | |
| 80.246.77.0/24 | 0 | 256 | |
| 80.246.79.0/24 | 0 | 82 | |
| 80.246.72.0/24 | 0 | 78 | |
| 80.246.74.0/24 | 0 | 71 | |
| 80.246.75.0/24 | 0 | 2 | |
| 80.246.78.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- ResiProxies
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 80.246.72.0/24 since Sep 2017 | AS12389 | Residential | 78 | PJSC Rostelecom | |
| 80.246.74.0/24 since Sep 2017 | AS12389 | Residential | 71 | PJSC Rostelecom | |
| 80.246.79.0/24 since Sep 2017 | AS12389 | Residential | 82 | 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 |
|---|---|---|---|---|---|---|
| 80.246.64.0/19 | 8,192 | RU-RTK-20011108 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jun 15, 2004 | [email protected] |
| └ 80.246.72.0/21 | 2,048 | Tver-TeleNet | JSC "TeleNET" | ASSIGNED PA | Jan 10, 2017 | [email protected] via RU-RTK-20011108 |
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 80.246.64.0/19
- Prefix
- 80.246.64.0/19
- Announced by
- AS21378 PJSC Rostelecom
- Type
- Residential
- Proxy exits
- 1,839
- Always-on exits
- 401
- RPKI
- RPKI valid
- Netname
- RU-RTK-20011108
- Registrant
- PJSC Rostelecom
- RIR
- RIPE NCC
Origin network
AS21378
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Nov 20, 2001
- Domain
- tversvyaz.ru
- Industry
- Computer and Information Technology
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced 80.246.64.0/19
80.246.64.0/19
Routing history
- Pattern
- Stable
- First seen
- Oct 2011
- Current origin since
- Oct 2011 · 15 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 80.246.64.0/19 | AS21378 | /19 | RIPE | RPKI valid |
IRR
Route objects on 80.246.64.0/19
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS21378 | RIPE | TeleNET | ROSTELECOM-MNT | Dec 23, 2024 |
Whois
Registration for this announcement
- Range
- 80.246.64.0/19
- Netname
- RU-RTK-20011108
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jun 15, 2004
- Updated
- Jun 15, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Nov 8, 2001
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE