Data as of Nov 11, 2026

77.220.151.0/24

6 residential-proxy exits · 30 days

JSC Comcor

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
38
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.5K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.220.128.0/198,192RU-COMCOR-20070323JSC Comcor (ORG-CA35-RIPE) · RUALLOCATED PAFeb 27, 2015netadm@comcor.ru
└ 77.220.148.0/221,024MIG-TELECOMJSC "AKADO-Stolitsa" - MigTelecom, MoscowASSIGNED PAMay 4, 2009netadm@comcor.ru
via RU-COMCOR-20070323

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

Routing timeline

Who has announced 77.220.128.0/19

77.220.128.0/19

Routing history

Pattern
Stable
First seen
Apr 2007
Current origin since
Apr 2014 · 13 yr
Origin networks
2
Last change of origin
Apr 2014
Recorded history

History

Handoffs
3