Data as of Nov 14, 2026
95.106.0.0/16
1 anonymizer address · <0.01% · VPN17,929 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
17,929
27% of its addresses · 30 days
Always-on exits
2
0.01% of its exits
Spread
256 of 256
/24s with at least one exit
Providers
138
selling exits here
Oct 15, 2026 – Nov 13, 2026
Exits seen per day
908K observations
- VPN · anonymizer
- Residential
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 95.106.50.0/24 | 1 | 74 | |
| 95.106.89.0/24 | 1 | 71 | |
| 95.106.250.0/24 | 0 | 97 | |
| 95.106.251.0/24 | 0 | 94 | |
| 95.106.255.0/24 | 0 | 93 | |
| 95.106.228.0/24 | 0 | 92 | |
| 95.106.236.0/24 | 0 | 92 | |
| 95.106.238.0/24 | 0 | 92 | |
| 95.106.145.0/24 | 0 | 92 | |
| 95.106.132.0/24 | 0 | 91 | |
| 95.106.243.0/24 | 0 | 90 | |
| 95.106.131.0/24 | 0 | 89 | |
| 95.106.156.0/24 | 0 | 88 | |
| 95.106.153.0/24 | 0 | 88 | |
| 95.106.142.0/24 | 0 | 87 | |
| 95.106.226.0/24 | 0 | 87 | |
| 95.106.129.0/24 | 0 | 85 | |
| 95.106.232.0/24 | 0 | 85 | |
| 95.106.248.0/24 | 0 | 85 | |
| 95.106.234.0/24 | 0 | 85 | |
| 95.106.158.0/24 | 0 | 85 | |
| 95.106.235.0/24 | 0 | 85 | |
| 95.106.241.0/24 | 0 | 83 | |
| 95.106.206.0/24 | 0 | 83 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- APROXY
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CROXY
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- FuseProxy
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HELODATA
- HPROXY
- HideProxy
- HydraProxy
- IP2WORLD
- IPCola
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPROCKET_BASIC
- IPROCKET_PREMIUM
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- KocerRoxy
- Kookey
- LOKIPROXY
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYFALL
- PROXYLANE
- PROXYON
- PROXYSAVER
- PROXYSCRAPE
- PROXYWING_BASIC
- PROXY_CC
- PYPROXY
- PacketStream
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RH7Proxy
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SIMPLYNODE
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TORCHPROXIES_BASIC
- TORCHPROXIES_PREMIUM
- TORCHPROXIES_X
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 95.106.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 →
95.106.0.0/16
From the registry to its use
- Jul 6, 2011Registry recordPJSC RostelecomALLOCATED PA95.106.0.0 - 95.107.127.255
- Feb 16, 2012Route objectAS34267 PJSC RostelecomRIPE route object for AS34267 PJSC Rostelecom, maintainer BRSI-RU-MNT95.106.224.0/20
- Jan 12, 2017Route objectAS21378 PJSC RostelecomRIPE route object for AS21378 PJSC Rostelecom, maintainer ROSTELECOM-MNT95.106.128.0/19
- Nov 9, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- Nov 9, 2018– today
- todayUsedVPN GateVPN
Announcements
Nesting
More-specifics by size
Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific
Announcements inside
| Prefix | Origin | Type | Anonymizer addresses | Operator | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|---|---|
| 95.106.0.0/17 since Dec 2008 | AS12730 | Residential | 8,689 2 always on | PJSC Rostelecom | |||
| 95.106.0.0/18 since Mar 2017 | AS12389 | Residential | 4,479 1 always on | PJSC Rostelecom | |||
| 95.106.64.0/18 since Mar 2017 | AS12389 | Residential | 4,210 1 always on | PJSC Rostelecom | |||
| 95.106.128.0/21 since Sep 2017 | AS12389 | Residential | 623 | PJSC Rostelecom via PJSC Rostelecom | |||
| 95.106.136.0/21 since Sep 2017 | AS12389 | Residential | 587 | PJSC Rostelecom via PJSC Rostelecom | |||
| 95.106.144.0/21 since Sep 2017 | AS12389 | Residential | 610 | PJSC Rostelecom via PJSC Rostelecom | |||
| 95.106.152.0/21 since Sep 2017 | AS12389 | Residential | 634 | PJSC Rostelecom via PJSC Rostelecom | |||
| 95.106.160.0/19 since Feb 2012 | AS13118 | Residential | 2,038 | PJSC Rostelecom | |||
| 95.106.160.0/21 since Oct 2017 | AS12389 | Residential | 515 | PJSC Rostelecom | |||
| 95.106.168.0/21 since Oct 2017 | AS12389 | Residential | 509 | PJSC Rostelecom | |||
| 95.106.176.0/21 since Oct 2018 | AS12389 | Residential | 502 | PJSC Rostelecom | |||
| 95.106.184.0/21 since Oct 2017 | AS12389 | Residential | 512 | PJSC Rostelecom | |||
| 95.106.192.0/19 since Mar 2017 | AS12389 | Residential | 10.01%VPN | VPN servicesoperated by VPN Gate | 2,119 | PJSC Rostelecom | |
| 95.106.224.0/21 since Jan 2017 | AS12389 | Residential | 651 | PJSC Rostelecom | |||
| 95.106.232.0/21 since Jan 2017 | AS12389 | Residential | 669 | PJSC Rostelecom | |||
| 95.106.240.0/21 since Jan 2017 | AS12389 | Residential | 632 | PJSC Rostelecom | |||
| 95.106.248.0/21 since Jan 2017 | AS12389 | Residential | 667 | 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 |
|---|---|---|---|---|---|---|
| 95. | 98,304 | RU-RTK-20081202 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jul 6, 2011 | abuse@ |
| └ 95.106.0.0/18 | 16,384 | MACROREGIONAL_ | OJSC Rostelecom, Ryazan Branch | ASSIGNED PA | Jun 25, 2026 | abuse@ via RU-RTK-20081202 |
| └ 95.106.64.0/20 | 4,096 | MACROREGIONAL_ | OJSC Rostelecom, Ryazan Branch | ASSIGNED PA | Jun 30, 2026 | abuse@ via RU-RTK-20081202 |
| └ 95.106.80.0/20 | 4,096 | MACROREGIONAL_ | OJSC Rostelecom, Ryazan Branch | ASSIGNED PA | Jun 30, 2026 | abuse@ via RU-RTK-20081202 |
| └ 95.106.96.0/19 | 8,192 | MACROREGIONAL_ | OJSC Rostelecom, Ryazan Branch | ASSIGNED PA | Jun 30, 2026 | abuse@ via RU-RTK-20081202 |
| └ 95.106.128.0/19 | 8,192 | MACROREGIONAL_ | PJSC Rostelecom (ORG-JR8-RIPE) · RU | SUB-ALLOCATED PA | Jan 12, 2017 | abuse@ |
| └ 95.106.128.0/21 | 2,048 | MACROREGIONAL_ | OJSC Rostelecom, Tver branch | ASSIGNED PA | Jan 12, 2017 | abuse@ via MACROREGIONAL_CENTER |
| └ 95.106.136.0/21 | 2,048 | MACROREGIONAL_ | OJSC Rostelecom, Tver branch | ASSIGNED PA | Jan 12, 2017 | abuse@ via MACROREGIONAL_CENTER |
| └ 95.106.144.0/21 | 2,048 | MACROREGIONAL_ | OJSC Rostelecom, Tver branch | ASSIGNED PA | Jan 12, 2017 | abuse@ via MACROREGIONAL_CENTER |
| └ 95.106.152.0/21 | 2,048 | MACROREGIONAL_ | OJSC Rostelecom, Tver branch | ASSIGNED PA | Jan 12, 2017 | abuse@ via MACROREGIONAL_CENTER |
| └ 95.106.160.0/19 | 8,192 | MACROREGIONAL_ | OJSC Rostelecom, Yaroslavl branch | ASSIGNED PA | Feb 3, 2012 | abuse@ via RU-RTK-20081202 |
| └ 95.106.192.0/19 | 8,192 | MACROREGIONAL_ | OJSC Rostelecom | ASSIGNED PA | Nov 24, 2025 | abuse@ via RU-RTK-20081202 |
| └ 95.106.224.0/20 | 4,096 | MACROREGIONAL_ | PJSC Rostelecom, Bryansk branch | ASSIGNED PA | Feb 16, 2012 | abuse@ via RU-RTK-20081202 |
| └ 95.106.240.0/20 | 4,096 | MACROREGIONAL_ | PJSC Rostelecom, Bryansk branch | ASSIGNED PA | Aug 29, 2012 | abuse@ via RU-RTK-20081202 |
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% | 16 | |
| 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
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Nov 2018
- Current origin since
- Nov 2018 · 8.0 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 95.106.0.0/16 | AS12389 | /21 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Nov 9, 2018 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 95.106.128.0/19 | AS21378 | RIPE | 95.106.128.0/19 | ROSTELECOM-MNT | Jun 15, 2026 |
| 95.106.224.0/20 | AS34267 | RIPE | PJSC Rostelecom, Bryansk branch | BRSI-RU-MNT | Sep 13, 2022 |
Whois
Registration for this announcement
- Range
- 95.
106. 0. 0 - 95. 107. 127. 255 - Netname
- RU-RTK-20081202
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jul 6, 2011
- Updated
- May 25, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Dec 2, 2008
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE