Data as of Nov 9, 2026
178.66.0.0/16
1 anonymizer address · <0.01% · VPN9,665 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
9,665
15% of its addresses · 30 days
Always-on exits
1,467
15% of its exits
Spread
248 of 256
/24s with at least one exit
Providers
123
selling exits here
Oct 10, 2026 – Nov 8, 2026
Exits seen per day
2.6M observations
- VPN · anonymizer
- Residential
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 178.66.130.0/24 | 154 | 256 | |
| 178.66.131.0/24 | 152 | 256 | |
| 178.66.159.0/24 | 150 | 256 | |
| 178.66.128.0/24 | 149 | 256 | |
| 178.66.156.0/24 | 149 | 256 | |
| 178.66.129.0/24 | 143 | 256 | |
| 178.66.157.0/24 | 136 | 255 | |
| 178.66.158.0/24 | 133 | 254 | |
| 178.66.161.0/24 | 6 | 34 | |
| 178.66.38.0/24 | 5 | 38 | |
| 178.66.216.0/24 | 5 | 35 | |
| 178.66.86.0/24 | 5 | 30 | |
| 178.66.5.0/24 | 4 | 49 | |
| 178.66.154.0/24 | 4 | 39 | |
| 178.66.164.0/24 | 4 | 35 | |
| 178.66.179.0/24 | 4 | 32 | |
| 178.66.180.0/24 | 4 | 28 | |
| 178.66.211.0/24 | 4 | 28 | |
| 178.66.204.0/24 | 4 | 24 | |
| 178.66.50.0/24 | 4 | 16 | |
| 178.66.138.0/24 | 3 | 50 | |
| 178.66.4.0/24 | 3 | 42 | |
| 178.66.192.0/24 | 3 | 41 | |
| 178.66.105.0/24 | 3 | 38 |
Proxy providers listing exits
- 2Captcha
- 2Extract
- 711Proxy
- 911Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSCRAPE
- PROXYWING_BASIC
- PSBProxy
- PacketStream
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RH7Proxy
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- WealthProxies
- Webshare
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 178.66.0.0/16 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 1<0.01% | 1 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
178.66.0.0/16
From the registry to its use
- Jan 5, 2010Registry recordPJSC RostelecomALLOCATED PA178.64.0.0/13
- Jan 7, 2010– Oct 27, 2018
- Nov 8, 2010– Oct 15, 2018AnnouncedAS8997 PJSC Rostelecom
- Oct 4, 2018– today
- Oct 16, 2018– today
- Oct 18, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- todayUsedVPN GateVPN
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 178.64.0.0/13 since Oct 2018 | AS12389 | Residential | 68,145 3,847 always on | PJSC Rostelecom |
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 178.66.73.0/24 since Feb 2020 | AS12389 | Residential | 20 | PJSC Rostelecom | |
| 178.66.74.0/24 since Feb 2020 | AS12389 | Residential | 25 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 |
|---|---|---|---|---|---|---|
| 178.64.0.0/13 | 524,288 | RU-RTK-20100105 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jan 5, 2010 | abuse@ |
| └ 178.66.0.0/18 | 16,384 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.64.0/21 | 2,048 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.72.0/24 | 256 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.73.0/24 | 256 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.74.0/24 | 256 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.75.0/24 | 256 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.76.0/23 | 512 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.78.0/23 | 512 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.80.0/23 | 512 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.82.0/24 | 256 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.83.0/24 | 256 | RU-RTK-GGC-SZ | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.84.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.88.0/23 | 512 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.90.0/23 | 512 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.92.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.96.0/19 | 8,192 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178. | 768 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.131.0/24 | 256 | RU-RTK-NAT-SZ | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.132.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.136.0/21 | 2,048 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.144.0/23 | 512 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.146.0/23 | 512 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.148.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.152.0/24 | 256 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.153.0/24 | 256 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.154.0/24 | 256 | RU-AVANGARD-DSL | Arkhangelsk branch of the PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.155.0/24 | 256 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.156.0/23 | 512 | RU-RTK-NAT-SZL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.158.0/23 | 512 | RU-RTK-NAT-SZL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.160.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.164.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.168.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.172.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.176.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.180.0/22 | 1,024 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.184.0/21 | 2,048 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.192.0/23 | 512 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.194.0/23 | 512 | RU-AVANGARD-DSL | PJSC Rostelecom | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.196.0/23 | 512 | RU-AVANGARD-DSL | Saint-Peterburg branch of the OJSC "Rostelecom" | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.198.0/23 | 512 | RU-AVANGARD-DSL | Saint-Peterburg branch of the OJSC "Rostelecom" | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.200.0/21 | 2,048 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.208.0/20 | 4,096 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
| └ 178.66.224.0/19 | 8,192 | RU-AVANGARD-DSL | PJSC "Rostelecom" North-West Region | ASSIGNED PA | Nov 11, 2021 | abuse@ via RU-RTK-20100105 |
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
65,536 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 65,535 | >99% | 15 | |
| VPNanonymizer | 1 | <0.01% | 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
- Nov 2010
- Current origin since
- Oct 2018 · 8.1 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 |
|---|---|---|---|---|
| 178.66.0.0/16 | AS12389 | /16 | RIPE | RPKI valid |
| 178.64.0.0/13 | AS12389 | /23 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Oct 18, 2018 |
Whois
Registration for this announcement
- Range
- 178.
64. 0. 0/ 13 - Netname
- RU-RTK-20100105
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jan 5, 2010
- Updated
- May 29, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jan 5, 2010
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE