Data as of Nov 14, 2026

200.66.68.0/22

5 residential-proxy exits · 30 days

Megacable Comunicaciones de Mexico, S.A. de C.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
37
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

823 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
200.66.69.0/2402
200.66.70.0/2402
200.66.71.0/2401

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • Infatica
  • LemonBright
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsRPKI
200.66.64.0/19
since Nov 2024
AS14178Business47
1 always on
More specific

Announcements inside

PrefixOriginTypeProxy exitsRPKI
200.66.68.0/23
since Aug 2021
AS14178Business2
200.66.69.0/24
since May 2022
AS14178Business2
200.66.70.0/23
since Aug 2021
AS14178Internet provider3
200.66.70.0/24
since May 2022
AS14178Business2
200.66.71.0/24
since May 2022
AS14178Business1

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
200.66.64.0/198,192—Megacable Comunicaciones de Mexico, S.A. de C.V. (MX-MCMS-LACNIC)allocatedJul 6, 2001abuse@mcmtelecom.com.mx
└ 200.66.64.0/212,048—Megacable Comunicaciones de Mexico, S.A. de C.V. (MX-MCMS-LACNIC)reassignedJul 8, 2011ipmaster@mcmtelecom.com.mx

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jul 2017
Current origin since
Jul 2023 · 3.3 yr
Origin networks
1