Data as of Nov 11, 2026
80.72.112.0/20
32 residential-proxy exits · 30 daysJSC Telephone Company 'Sotcom'
Residential-proxy exits
Proxy exits
32
0.78% of its addresses · 30 days
Always-on exits
2
6.3% of its exits
Spread
12 of 16
/24s with at least one exit
Providers
48
selling exits here
Oct 12, 2026 – Nov 10, 2026
Exits seen per day
3.2K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 80.72.125.0/24 | 2 | 4 | |
| 80.72.122.0/24 | 0 | 5 | |
| 80.72.116.0/24 | 0 | 4 | |
| 80.72.127.0/24 | 0 | 4 | |
| 80.72.114.0/24 | 0 | 3 | |
| 80.72.123.0/24 | 0 | 3 | |
| 80.72.118.0/24 | 0 | 2 | |
| 80.72.121.0/24 | 0 | 2 | |
| 80.72.124.0/24 | 0 | 2 | |
| 80.72.115.0/24 | 0 | 1 | |
| 80.72.117.0/24 | 0 | 1 | |
| 80.72.119.0/24 | 0 | 1 |
Proxy providers listing exits
- 711Proxy
- 911Proxy
- ASHBURNPROXIES
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- Evomi
- FastProxy
- FloppyData
- Geonode
- GhostConnect
- HideProxy
- IPFly
- IPPeak
- InfiniteProxies
- KocerRoxy
- LUMIPROXY
- LemonBright
- LudaxProxy
- NSocks
- NextProxy
- NiuProxy
- NovaProxy
- Oxylabs
- PROXYSCRAPE
- ProxiesVision
- Proxio
- Proxiware
- ProxyGeo
- ProxyRack
- PuraRoute
- RainProxy
- Shifter
- Smartproxy
- TrueProxies
- ZENPROXY_PREMIUM
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.72.112.0/20 | 4,096 | RU-SOTCOM-20050124 | JSC Telephone Company "Sotcom" (ORG-JTC5-RIPE) · RU | ALLOCATED PA | Jan 24, 2005 | support@ |
| └ 80.72.112.0/24 | 256 | SOTCOM-NET | Sotcom core net | ASSIGNED PA | Jan 24, 2005 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.113.0/24 | 256 | SOTCOM-LL-NET | Sotcom customer LL net | ASSIGNED PA | Jan 24, 2005 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.114.0/24 | 256 | SOTCOM-DU-NET | Sotcom DialUp net | ASSIGNED PA | Jan 24, 2005 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.115.0/24 | 256 | SOTCOM-DU-NET | Sotcom DialUp net | ASSIGNED PA | Jan 24, 2005 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.116.0/25 | 128 | SOTCOM-DU-ADD-NET | Sotcom DialUp net | ASSIGNED PA | Apr 18, 2005 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.116.128/25 | 128 | SOTCOM-LL-ADD-NET | Sotcom customer LL net #2 | ASSIGNED PA | Feb 14, 2006 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.117.0/24 | 256 | SOTCOM-ADSL-NET | Sotcom customer ADSL net #2 | ASSIGNED PA | Feb 14, 2006 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.118.0/24 | 256 | SOTCOM-LL-ADD2-NET | Sotcom customer LL net #3 | ASSIGNED PA | Nov 20, 2006 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.119.0/25 | 128 | EPAM-RZ-NET | EPAM Systems,Ryazan, Russia | ASSIGNED PA | Apr 26, 2007 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.119.128/25 | 128 | SOTCOM-LL-ADD2-NET | Sotcom customer LL net #5 | ASSIGNED PA | Apr 26, 2007 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.120.0/24 | 256 | SOTCOM-LL-ADD5-NET | Sotcom customer LL net #4 | ASSIGNED PA | Jan 23, 2008 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.121.0/24 | 256 | SOTCOM-ADSL-ADD1-NET | Sotcom customer ADSL net #3 | ASSIGNED PA | Mar 2, 2007 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.122.0/25 | 128 | INET-H-NET | network for company INET | ASSIGNED PA | Nov 20, 2006 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.122.128/25 | 128 | SOTCOM-LL-ADD3-NET | Sotcom customer LL net #4 | ASSIGNED PA | Mar 2, 2007 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.123.0/24 | 256 | SOTCOM-LL-ADD4-NET | Sotcom customer LL net #5 | ASSIGNED PA | Mar 4, 2009 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.124.0/24 | 256 | NN2-NLINK-LTD | Nlink LTD, Ryazan, Russia | ASSIGNED PA | Jul 19, 2005 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.125.0/24 | 256 | SOTCOM-ADSL-ADD2-NET | Sotcom customer ADSL net #4 | ASSIGNED PA | Mar 4, 2009 | support@ via RU-SOTCOM-20050124 |
| └ 80.72.126.0/23 | 512 | RINFUNET | The Regional Packet Switching company RINFOTELS | ASSIGNED PA | Feb 15, 2005 | support@ via RU-SOTCOM-20050124 |
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
4,096 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 3,840 | 94% | 3 | |
| Business | 256 | 6.3% | 2 |
Network & registry
Origin network
AS34467
RU
- Name
- JSC Telephone Company 'Sotcom'
- Type
- Internet provider
- Registered
- Jan 26, 2005
- Domain
- sotcom.ru
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- May 2005 · 22 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS34467 | RIPE | Sotcom Block | MNT-SOTCOM | Jan 26, 2005 |
Whois
Registration for this announcement
- Range
- 80.
72. 112. 0/ 20 - Netname
- RU-SOTCOM-20050124
- Registrant
- JSC Telephone Company "Sotcom"
- Registrant country
- RU
- Organization
- JSC Telephone Company "Sotcom" (ORG-JTC5-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jan 24, 2005
- Updated
- Nov 30, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jan 24, 2005
- Status
- assigned
Report abuse
Abuse contact
- support@
sotcom. ru - Name
- SOTCOM ISP
- Handle
- SI590-RIPE