Data as of Nov 6, 2026
77.220.48.0/21
1,027 residential-proxy exits · 30 daysMTS PJSC
Residential-proxy exits
Proxy exits
1,027
50% of its addresses · 30 days
Always-on exits
194
19% of its exits
Spread
6 of 8
/24s with at least one exit
Providers
83
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
502K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 77.220.51.0/24 | 64 | 255 | |
| 77.220.53.0/24 | 47 | 256 | |
| 77.220.50.0/24 | 44 | 256 | |
| 77.220.52.0/24 | 39 | 256 | |
| 77.220.55.0/24 | 0 | 2 | |
| 77.220.48.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BestProxy
- BirdProxies
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EnigmaProxy
- Evomi
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LightningProxies
- MangoProxy
- MarsProxies
- Maskify
- NSocks
- NiuProxy
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PrivateProxy
- Proxies.fo
- Proxio
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RapidProxy
- ResiProxies
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalExclusive
- VitalProxy
- Webshare
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 77.220.50.0/23 since Oct 2021 | AS30881 | Residential | 511 108 always on | MTS PJSC | |
| 77.220.52.0/23 since Oct 2021 | AS30881 | Residential | 512 86 always on | MTS PJSC |
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.220.32.0/19 | 8,192 | RU-MTU-20070319 | MTS PJSC (ORG-ZM1-RIPE) · RU | ALLOCATED PA | Mar 19, 2007 | abuse@ |
| └ 77.220.48.0/28 | 16 | BAIT-FORCE-NETWORK | Bait-Force-Network | ASSIGNED PA | Jul 27, 2009 | abuse@ via RU-MTU-20070319 |
| └ 77.220.48.16/29 | 8 | YARRADIOZAVOD-NETWORK | YarRadioZavod-Network | ASSIGNED PA | Jul 27, 2009 | abuse@ via RU-MTU-20070319 |
| └ 77.220.48.24/29 | 8 | ZOZON-NETWORK | Zozon-Network | ASSIGNED PA | Jul 27, 2009 | abuse@ via RU-MTU-20070319 |
| └ 77.220.48.64/29 | 8 | BANKRUSSTANDART-NETWORK | BankRusStandart-NETWORK | ASSIGNED PA | Jul 8, 2008 | abuse@ via RU-MTU-20070319 |
| └ 77.220.48.72/29 | 8 | REZINATEHSNAB-NETWORK | Rezinatehsnab-NETWORK | ASSIGNED PA | Jul 8, 2008 | abuse@ via RU-MTU-20070319 |
| └ 77.220.48.80/29 | 8 | MESI-NETWORK | unknown | ASSIGNED PA | Jul 8, 2008 | abuse@ via RU-MTU-20070319 |
| └ 77.220.48.112/28 | 16 | NES-NETWORK | NES-Network | ASSIGNED PA | Apr 9, 2009 | abuse@ via RU-MTU-20070319 |
| └ 77.220.48.128/27 | 32 | BARANOV-NETWORK | Baranov-Network | ASSIGNED PA | Apr 9, 2009 | abuse@ via RU-MTU-20070319 |
| └ 77.220.48.160/29 | 8 | FSKEES-NETWORK | FSKEES-Network | ASSIGNED PA | Apr 9, 2009 | abuse@ via RU-MTU-20070319 |
| └ 77.220.48.168/29 | 8 | AVANGARDKINO-NETWORK | Avangardkino-Network | ASSIGNED PA | Apr 9, 2009 | abuse@ via RU-MTU-20070319 |
| └ 77.220.49.0/24 | 256 | TENSORTELECOM-NETWORK | PPPoE and PPTP clients | ASSIGNED PA | May 30, 2017 | abuse@ via RU-MTU-20070319 |
| └ 77. | 1,024 | UFK-Network | UFK Network Allocation | ASSIGNED PA | May 30, 2017 | abuse@ via RU-MTU-20070319 |
| └ 77.220.54.0/24 | 256 | TENSORTELECOM-NETWORK | PPPoE and PPTP clients | ASSIGNED PA | May 30, 2017 | abuse@ via RU-MTU-20070319 |
| └ 77.220.55.0/24 | 256 | TENSORTELECOM-NETWORK | Client Uplinks | ASSIGNED PA | May 30, 2017 | abuse@ via RU-MTU-20070319 |
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
Origin network
AS30881
RU
- Name
- MTS PJSC
- Type
- Internet provider
- Registered
- Jan 5, 2004
- Domain
- mts.ru
- Industry
- Computer and Information Technology
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Oct 2019
- Current origin since
- Oct 2019 · 7.0 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS30881 | RIPE | MTS Yaroslavl route object | TTEL-MNT | Jan 20, 2021 |
Whois
Registration for this announcement
- Range
- 77.
220. 32. 0/ 19 - Netname
- RU-MTU-20070319
- Registrant
- MTS PJSC
- Registrant country
- RU
- Organization
- MTS PJSC (ORG-ZM1-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Mar 19, 2007
- Updated
- May 24, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Mar 19, 2007
- Status
- assigned
Report abuse
Abuse contact
- abuse@
mtu. ru - Name
- MTU Abuse-c Bender
- Handle
- MAB8359-RIPE