Data as of Nov 17, 2026

77.220.128.0/19

58 residential-proxy exits · 30 days

JSC Comcor

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

Residential-proxy exits

Proxy exits
58
0.71% of its addresses · 30 days
Always-on exits
6
10% of its exits
Spread
14 of 32
/24s with at least one exit
Providers
82
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

15K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • APROXY
  • Ake.net
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYFALL
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • 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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.220.128.0/198,192RU-COMCOR-20070323JSC Comcor (ORG-CA35-RIPE) · RUALLOCATED PAFeb 27, 2015netadm@comcor.ru
└ 77.220.128.0/212,048AKADO-B2CJSC "Akado-B2C"ASSIGNED PAApr 18, 2007netadm@comcor.ru
via RU-COMCOR-20070323
└ 77.220.136.0/221,024MIG-TELECOMJSC "AKADO-Stolitsa", MigTelecom, MoscowASSIGNED PANov 8, 2007netadm@comcor.ru
via RU-COMCOR-20070323
└ 77.220.140.0/221,024MIG-TELECOMJSC "AKADO-Stolitsa" - MigTelecom, MoscowASSIGNED PAApr 16, 2009netadm@comcor.ru
via RU-COMCOR-20070323
└ 77.220.144.0/23512MIG-TELECOMJSC "AKADO-Stolitsa", MigTelecom, MoscowASSIGNED PAJun 8, 2007netadm@comcor.ru
via RU-COMCOR-20070323
└ 77.220.148.0/221,024MIG-TELECOMJSC "AKADO-Stolitsa" - MigTelecom, MoscowASSIGNED PAMay 4, 2009netadm@comcor.ru
via RU-COMCOR-20070323
└ 77.220.152.0/23512MIG-TELECOMJSC "AKADO-Stolitsa", MigTelecom, MoscowASSIGNED PAFeb 6, 2008netadm@comcor.ru
via RU-COMCOR-20070323
└ 77.220.156.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 this prefix

Summary

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