Data as of Nov 4, 2026
80.246.64.0/21
349 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
349
17% of its addresses · 30 days
Always-on exits
2
0.57% of its exits
Spread
6 of 8
/24s with at least one exit
Providers
78
selling exits here
Oct 5, 2026 – Nov 3, 2026
Exits seen per day
92K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 80.246.69.0/24 | 2 | 12 | |
| 80.246.68.0/24 | 0 | 256 | |
| 80.246.70.0/24 | 0 | 75 | |
| 80.246.67.0/24 | 0 | 3 | |
| 80.246.65.0/24 | 0 | 2 | |
| 80.246.66.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PacketStream
- PrivateByte
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- Shifter
- Smartproxy
- Thordata
- VantageProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 80.246.64.0/19 since Oct 2011 | AS21378 | Residential | 1,836 387 always on | PJSC Rostelecom |
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 80.246.70.0/24 since Sep 2017 | AS12389 | Residential | 75 | 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 |
|---|---|---|---|---|---|---|
| 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.64.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
IPv4 market
Holder
- Organization
- PJSC Rostelecom
- Handle
- ORG-JR8-RIPE
- Range
- 80.246.64.0/19
- Registration type
- ALLOCATED PA
- Record created
- Jun 15, 2004
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
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Jun 2009
- Current origin since
- Jan 2017 · 9.8 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 80.246.64.0/21 | AS21378 | /21 | RIPE | RPKI valid |
| 80.246.64.0/19 | AS21378 | /19 | RIPE | Too specific |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS21378 | RIPE | TeleNET | ROSTELECOM-MNT | Dec 23, 2024 |
Whois
Registration for this announcement
- Range
- 80.246.64.0/21
- Netname
- Tver-TeleNet
- Registrant
- JSC "TeleNET"
- Registrant country
- RU
- Organization
- JSC "TeleNET"
- Org country
- RU
- Type
- ASSIGNED PA
- Created
- Jan 10, 2017
- Updated
- Jun 15, 2026
- Maintainer
- ROSTELECOM-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