Service availability and operations policy

This page explains how HostMyCode approaches service availability, maintenance, and incident handling for standard hosting services. It should be read together with the Terms of Service, Refund Policy, Acceptable Use Policy, and any product-specific terms that apply to your order.

Unless a separate written agreement expressly states otherwise, HostMyCode services are provided on a commercially reasonable, best-effort basis. This page does not create a guaranteed uptime commitment, service credit right, or response-time SLA for standard retail accounts.

HostMyCode works to operate stable hosting infrastructure, maintain healthy network connectivity, and respond to service-impacting incidents using commercially reasonable efforts.

Operational activity may include monitoring, repairs, reboots, upstream coordination, hardware replacement, platform tuning, emergency actions, and security-related interventions based on the nature of the affected service.

Routine and emergency maintenance may be required to preserve platform stability, security, and performance. This can include kernel updates, hardware servicing, control panel maintenance, storage work, network changes, and datacenter-level maintenance.

When practical, HostMyCode will try to schedule planned work during lower-impact periods and provide reasonable notice for maintenance likely to affect service access. Some maintenance events may need to be performed immediately without advance notice.

Availability may be affected by events inside or outside HostMyCode control, including customer configuration errors, software faults, abuse events, DDoS attacks, upstream network issues, registrar delays, routing anomalies, datacenter incidents, hardware faults, or third-party service failures.

Standard service interruptions, degraded performance, or temporary inaccessibility do not create an automatic right to credits, refunds, or damages unless a separate written agreement expressly grants that remedy.

Customers remain responsible for their applications, website code, software stack, backups, monitoring, and operational readiness above the infrastructure layer. You should maintain current backups and reasonable recovery procedures for your services.

If you believe there is a service-impacting issue, you should open a support ticket with enough detail for investigation, including the affected service, timing, symptoms, and any troubleshooting already performed.

If HostMyCode enters into a separate written agreement with a customer that expressly defines uptime targets, credit terms, response windows, or custom support commitments, that written agreement will control for the covered services.

If no such written agreement exists, the standard best-effort service model described on this page and in the Terms of Service applies.