Resumen

  • La identidad pública de EcoHosting encaja limpiamente. Su sitio web y los términos de servicio de 2026 mencionan a EcoHosting Internet Limitada, RUT76.764.736-0, en Providencia 1650 oficina 303; LACNIC registra el AS266855 activo con el mismo nombre legal y dirección.
  • La evidencia de red es sustancial pero acotada. RIPEstat observó a AS266855 anunciando seis rutas IPv4/24y una IPv6/32durante el 1 al 15 de julio de 2026. Cuatro de esas rutas IPv4 y la asignación IPv6 están registradas directamente a EcoHosting, mientras que dos rutas IPv4 están dentro del espacio de direcciones registrado a Pluschile Internet Limitada.
  • EcoHosting publica superficies de producto utilizables para hosting compartido y VPS, incluyendo cPanel, controles de energía remotos, monitoreo y funciones de respaldo. Sus términos también dicen que los recursos ilimitados siguen sujetos a límites de uso razonable y que las herramientas de respaldo no son una garantía absoluta de recuperación completa o exitosa.
  • El sitio comercial anuncia soporte por tickets las 24 horas y una referencia de disponibilidad del 99.9%, pero los términos principales no convierten esos titulares en promesas de respuesta, resolución o compensación por sí mismos. Los compradores necesitan un cronograma de servicio que defina medición, recuperación, localidad, escalamiento, evidencia y salida.

La empresa legal y el registro de red apuntan al mismo lugar

Un proveedor de hosting regional debería ser fácil de identificar antes de que un cliente le confíe un dominio, buzón o aplicación. EcoHosting supera ese primer obstáculo con evidencia pública inusualmente directa. Supágina de empresanombra a EcoHosting Internet Limitada, publica el RUT76.764.736-0, da una dirección comercial en Providencia 1650 oficina 303 en Santiago y lista un número telefónico central. Lostérminos de servicioactuales repiten el nombre legal, número fiscal y dirección.

Elregistro de LACNIC para AS266855nombra de forma independiente a ECOHOSTING INTERNET LIMITADA como titular. Marca el sistema autónomo como activo, registra su inscripción el 17 de julio de 2018 y da la misma dirección de Providencia. El teléfono adjunto al titular es el número publicado en el sitio comercial. Esa es una unión de identidad útil: la parte que vende el servicio y la parte registrada como responsable de la red no están meramente conectadas por una marca similar.

Elperfil del directorio de BTWproporciona el ancla de comisionamiento. Sitúa a la empresa en Chile, la rastrea hasta un registro de miembro de LACNIC y la asocia con actividad de red gestionada, nube, centro de datos, colocación y hosting. Esas etiquetas enmarcan las preguntas; no certifican cada servicio ni establecen qué activos físicos posee EcoHosting.

La distinción importa porque el sitio web de la empresa hace afirmaciones amplias sobre operar desde 2011, atender a más de 10,000 clientes y gestionar más de 30,000 sitios web y buzones. Esas cifras son proporcionadas por el proveedor y no fueron corroboradas por una lista de clientes, informe auditado o conjunto de datos de servicio público. Un comprador puede confiar más en la unión legal y de registro que en el titular de escala. La conclusión resultante es limitada pero valiosa: EcoHosting es una contraparte chilena rastreable con una identidad de red rastreable.

AS266855 es evidencia de red real, no un certificado de tiempo de actividad

EcoHosting no pide a los clientes que acepten la frase "infraestructura local" completamente por fe. LACNIC registra el bloque IPv4 activo45.239.108.0/22a la empresa. Un/22contiene 1,024 direcciones IPv4. LACNIC también registra la asignación IPv6 activa2803:12a0::/32a EcoHosting. Ambos registros datan de julio de 2018 y nombran el mismo contacto administrativo, técnico y de abuso que el registro del sistema autónomo.

Las observaciones de enrutamiento muestran que estos recursos no son etiquetas inactivas. El registro de prefijos anunciados de RIPEstat paraAS266855observó siete rutas continuamente durante su ventana del 1 al 15 de julio de 2026: cuatro rutas/24cubriendo el45.239.108.0/22de EcoHosting, dos rutas/24en192.140.58.0y192.140.59.0, y la ruta IPv62803:12a0::/32. Cada/24IPv4 contiene 256 direcciones.

La lista de rutas también revela un límite operativo que un cliente no debería simplificar. LACNIC registra la asignación más grande192.140.56.0/22que contiene esos dos/24visibles a Pluschile Internet Limitada, no a EcoHosting. Las dos empresas comparten el mismo contacto de red nombrado en los registros, pero los documentos públicos revisados aquí no definen su relación corporativa o de servicio. EcoHosting puede tener un uso delegado legítimo o un acuerdo operativo; la evidencia no explica quién controla los registros de asignación, cambios de ruta, manejo de abuso o atención al cliente para esa porción del espacio de direcciones.

Hay una señal positiva de seguridad de ruta. La validación RPKI de RIPEstatdevolvióvalidpara AS266855 y el/22de EcoHosting, con una longitud máxima de ruta de/24. Esto permite que las redes que usan validación de origen de ruta verifiquen que AS266855 está autorizado para originar las cuatro rutas más específicas. La misma verificación devolvióunknownpara el IPv6/32, lo que significa que la captura no encontró una autorización de origen de ruta de validación para ese prefijo.

Estos registros establecen responsabilidad de recursos numéricos, enrutamiento visible y un control de autorización. No dicen nada sobre pérdida de paquetes, latencia, diversidad de tránsito, capacidad DDoS, gobernanza de cambios de ruta, ocupación de servidores o disponibilidad de aplicaciones. Un proveedor puede anunciar todos los prefijos esperados mientras un arreglo de discos, hipervisor, servicio DNS o cola de soporte está fallando.

La respuesta de adquisición correcta es solicitar una ruta específica del cliente: direcciones asignadas, ASN de origen, upstreams, instalación, capas de conmutación y cortafuegos, punto de monitoreo, diseño de conmutación por error y el equipo autorizado para cambiar cada capa.

La superficie del producto reemplaza tareas, pero también divide la responsabilidad

EcoHosting's current hosting catalogue is concrete enough to show what a small-business customer is buying. Plans combine website storage, corporate mailboxes, SSL, cPanel, MySQL, application installation and a site builder. The page names LiteSpeed Enterprise, BitNinja and JetBackup, and it distinguishes entry, small-business and higher-capacity plans by storage, mailboxes, sites and compute resources.

That bundle removes several pieces of manual work. A small company can register a domain, publish WordPress, create mailboxes, manage a database, obtain a certificate and request restoration without assembling separate suppliers. The automation is economically meaningful precisely because the customer does not need to operate every underlying component.

The VPS offer exposes a different control boundary. EcoHosting describes immediate provisioning, remote restart, shutdown and power-on through a web panel, SSD storage, optional cPanel, two full-server images per week, external backups and node monitoring through PRTG with email and SMS alerts. These are actions and mechanisms a buyer can test. They are more informative than a generic cloud label.

The control plane still leaves important questions unanswered. The public pages do not define role separation, multifactor authentication, API access, audit-log export, emergency-access controls, snapshot consistency, backup encryption, restore time or how a customer's action is reconciled with an operator action. Nor do they show whether the hosting and VPS layers share DNS, storage, authentication, network or support dependencies.

EcoHosting's own terms supply the necessary caution. "Unlimited" storage, sites, mailboxes, databases or transfer remain subject to normal and reasonable use. The provider may apply limits to CPU, memory, processes, storage, inodes, transfer, mail, connections, snapshots, restorations, ports and other parameters. A buyer should therefore treat the plan name as a commercial tier, not as a capacity model. Expected traffic, mailbox volume, database work, concurrent processes, storage growth and burst behaviour should be written into the accepted order with a warning and migration path before limits become service interruptions.

A 99.9% headline becomes useful only after its denominator is known

EcoHosting's commercial pages refer to 99.9% uptime and ticket support available 24/7. Both can be meaningful. Neither is self-defining.

The master terms say that an SLA, credit, compensation, commercial guarantee or availability commitment exists only when a current policy expressly applies it to the contracted service. They also say that a 24/7 support reference means general availability through the channels EcoHosting defines for that service; on its own, it does not establish a maximum response or resolution time. In the absence of a more specific policy, the terms do not promise an exact response or resolution time.

For a 30-day measurement period, 99.9% availability would permit about 43 minutes of counted unavailability. But that arithmetic is useful only after the contract identifies the measured component and clock. Is the commitment for network reachability, a physical server, the hosting control panel, DNS, mail, the customer's web application or the whole service? Is measurement taken from EcoHosting's monitor or from outside AS266855? Are maintenance, attacks, software faults, customer configuration and third-party failures excluded? Does the clock stop at workaround, partial restoration or complete recovery?

A service schedule should answer those questions and specify evidence. Monthly uptime reports, incident timestamps, alert history, route observations and ticket records should reconcile. If compensation is offered, the schedule should state the claim window, calculation and remedy. Without those definitions, 99.9% remains a useful signal of intent but an unreliable basis for valuing downtime risk.

Chilean operation does not locate every copy of customer data

EcoHosting consistently presents itself as a Chilean operator. The legal entidad, office, ASN, IPv4 allocation and IPv6 allocation all support that description. The hosting pages also say the infrastructure and support are in Chile. That is relevant to contracting, local contact and network latency.

It does not establish the location of every data class. Shared-hosting files, virtual-machine disks, snapshots, external backups, mail queues, DNS data, monitoring records, support attachments, account credentials and billing records may follow different paths. The public pages reviewed for this article do not name the production facility, backup site, subprocessor list, inter-site distance or storage operator for each product.

The master terms are explicit about the remaining customer responsibility. JetBackup, snapshots, restorations and similar mechanisms are described as an available tool or operational layer rather than an absolute guarantee of retention, integrity or successful recovery. EcoHosting says it does not guarantee in every case that copies remain available, cover all data or restore completely, and it requires customers to keep their own backups when continuity demands it. Expiration, non-payment or cancellation may also lead to lost access, content deletion or an inability to recover data.

This makes restoration and exit part of the buying test, not paperwork for the end of the relationship. The customer should map each data class to a primary location, backup location, operator, retention period, encryption key owner and deletion process. It should restore a representative site, mailbox, database and virtual-machine image into an isolated environment, then record recovery point, recovery time and missing dependencies. It should also export data and configuration in usable formats before testing cancellation or migration.

"Data in Chile" is valuable only when the contract identifies which data, in which Chilean location, under whose control and with what recovery evidence.

Local support has to connect the ticket to someone who can act

For a small business, EcoHosting's local support proposition may matter as much as its ASN. The site publishes a Chilean telephone number and sales address, while the client portal exposes tickets, a knowledge base and a network-status route. The commercial catalogue advertises continuous ticket support. Those are visible entry points, and the terms commit EcoHosting to maintaining official channels appropriate to the service.

The gap is authority. A ticket handler may be able to reset an account but not change a route, inspect a hypervisor, restore a backup or enter a facility. The public material does not publish severity definitions, on-call roles, escalation contacts, acknowledgement targets, update cadence or restoration distributions. It also does not explain when Pluschile, a software vendor, a facility operator or another supplier must act.

Buyers should test the support chain before placing a critical workload. Submit a low-risk incident through the prescribed channel, verify the timestamp and severity, ask for escalation and observe who can diagnose each layer. A tabletop exercise should cover a blocked address, failed website, lost mailbox, corrupted database, unreachable VPS and suspected route incident. The response record should identify the owner, evidence used, decision authority, handoff and next update time.

That exercise measures the labour behind the interface. Locality can shorten the commercial conversation, but it does not automatically shorten restoration. What matters is whether the person receiving the ticket can reach the person controlling the failed component, especially outside ordinary office hours.

Procurement should begin with a measured service map

EcoHosting has already supplied more public proof than a name alone. The legal identity is consistent, AS266855 is active, directly registered IPv4 and IPv6 resources are visible, expected prefixes are routed, one key IPv4 origin is RPKI-valid, and the product pages expose real hosting and VPS controls. Those facts justify serious evaluation.

They also show how to run it. First, bind the order to EcoHosting Internet Limitada, the exact plan, assigned resources, facility, origin ASN, any Pluschile dependency and every third party that can interrupt delivery. Second, test provisioning, role access, remote power actions, monitoring, backup and restoration with timestamps. Third, fail a permitted dependency and measure detection, escalation, workaround, recovery and communication. Finally, export the workload, mail, DNS, logs and account data, stop billing and verify deletion.

The acceptance record should become part of the service schedule. It should define capacity thresholds, availability measurement, recovery objectives, data locations, support clocks, evidence rights, remedies and exit assistance. That is the point at which network presence becomes operating assurance.

EcoHosting can credibly say that there is a Chilean company and network behind the storefront. The public record does not prove the outcome of the next disk failure, route change, restore request or overnight ticket. A buyer should credit the traceable footprint, then make the service earn the rest through a measured workload and a contract that names who acts when the automation stops.