Data as of Nov 3, 2026
77.51.16.0/21
460 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
460
22% of its addresses · 30 days
Always-on exits
2
0.43% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
82
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
28K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 77.51.20.0/24 | 2 | 51 | |
| 77.51.21.0/24 | 0 | 66 | |
| 77.51.19.0/24 | 0 | 64 | |
| 77.51.22.0/24 | 0 | 63 | |
| 77.51.18.0/24 | 0 | 57 | |
| 77.51.23.0/24 | 0 | 56 | |
| 77.51.17.0/24 | 0 | 53 | |
| 77.51.16.0/24 | 0 | 48 |
Proxy providers listing exits
- 711Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- 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
- RoamProxy
- Shifter
- Smartproxy
- StrikeProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VantageProxies
- VitalData
- VitalExclusive
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 77.51.0.0/16 since Feb 2007 | AS25515 | Residential | 9,380 81 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 |
|---|---|---|---|---|---|---|
| 77.51.0.0/16 | 65,536 | RU-RTK-20070112 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jan 12, 2007 | [email protected] |
| └ 77.51.0.0 - 77.51.52.255 | 13,568 | MACROREGIONAL_CENTER | ex-netname: CTC-DSLAM-4 | ASSIGNED PA | Nov 24, 2011 | [email protected] via RU-RTK-20070112 |
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
- 77.51.0.0/16
- Registration type
- ALLOCATED PA
- Record created
- Jan 12, 2007
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
- Apr 2007
- Current origin since
- Oct 2018 · 8.0 yr
- Origin networks
- 2
- Last change of origin
- Oct 2018
Recorded history
History
- Handoffs
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 77.51.16.0/21 | AS12389 | /21 | RIPE | RPKI valid |
| 77.51.0.0/16 | AS25515 | /16 | RIPE | Another network |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Oct 31, 2018 |
Whois
Registration for this announcement
- Range
- 77.51.0.0 - 77.51.52.255
- Netname
- MACROREGIONAL_CENTER
- Registrant
- ex-netname: CTC-DSLAM-4
- Registrant country
- RU
- Organization
- ex-netname: CTC-DSLAM-4
- Org country
- RU
- Type
- ASSIGNED PA
- Created
- Nov 24, 2011
- Updated
- May 22, 2026
- Maintainer
- ROSTELECOM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jan 12, 2007
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE