Fusion Arc Hosting – Network & Power Service Level Agreement (SLA)

Fusion Arc Hosting – A Fusion Arc Telecom LLC Company

Effective Date: September 18, 2026
Last Updated: September 18, 2026


1. Purpose and Scope

This Network & Power Service Level Agreement (“SLA”) establishes the network-connectivity and datacenter-power availability commitment applicable to qualifying Fusion Arc Hosting Services.

This SLA specifically addresses:

  • network availability;
  • datacenter-delivered power availability;
  • Fusion Arc Hosting-owned, operated, colocated, leased, and third-party infrastructure;
  • managed-server and node monitoring;
  • Network Operations Center (“NOC”) alerting and response targets;
  • public Service Status reporting;
  • Qualifying Network Downtime;
  • Qualifying Power Downtime;
  • uptime measurement;
  • Scheduled Maintenance;
  • Emergency Maintenance;
  • hardware failures;
  • hardware replacement targets;
  • SLA exclusions;
  • Service Credit eligibility;
  • Service Credit calculations;
  • SLA claim procedures; and
  • the relationship between this SLA and other Fusion Arc Hosting policies.

This SLA does not establish a general guarantee that every server, website, application, operating system, storage device, database, control panel, backup system, hardware component, monitoring system, or software component will remain continuously operational.

This SLA forms part of the Fusion Arc Hosting Agreement and operates together with the applicable:

  • Terms of Service (“TOS”);
  • Acceptable Use Policy (“AUP”);
  • Fair Usage Policy (“FUP”);
  • Privacy Policy;
  • Refund & Payment Policy;
  • Support Scope, Fully Managed Services & Best-Effort Assistance Policy (“Support Policy”);
  • Backup, Recovery & Disaster Recovery Policy (“Backup Policy”);
  • Domain Registration & Renewal Policy;
  • product descriptions;
  • checkout terms;
  • service-specific terms;
  • order forms; and
  • other applicable written agreements.

The order-of-precedence provisions in the TOS govern any direct conflict between contractual documents.

For matters specifically concerning the Network and Power Availability commitment and associated SLA Service Credits, this SLA is the primary subject-matter policy unless an applicable written agreement expressly provides otherwise.

Nothing in this SLA limits rights that cannot lawfully be waived.


2. Standard Network and Power Availability Commitment

Unless a Service-specific written agreement provides otherwise, Fusion Arc Hosting provides a 99.9% Monthly Network and Power Availability commitment for eligible Covered Services.

The 99.9% commitment applies principally to:

  • Covered Network Infrastructure serving the applicable server, node, or Service; and
  • datacenter-delivered electrical power serving the applicable server, node, or infrastructure.

Covered infrastructure may be:

  • owned by Fusion Arc Hosting;
  • operated by Fusion Arc Hosting;
  • colocated by Fusion Arc Hosting;
  • leased by Fusion Arc Hosting;
  • rented or licensed by Fusion Arc Hosting;
  • supplied through a datacenter or infrastructure partner;
  • supplied through an upstream network provider; or
  • otherwise directly procured by Fusion Arc Hosting for delivery of the applicable Service.

Ownership of the physical datacenter is not required for infrastructure to qualify as Covered Infrastructure under this SLA.


3. What the 99.9% Commitment Does Not Mean

The 99.9% commitment does not constitute a 99.9% guarantee for:

  • individual websites;
  • server hardware;
  • hard drives;
  • SSDs;
  • NVMe devices;
  • RAID controllers;
  • server motherboards;
  • CPUs;
  • memory;
  • power-supply hardware;
  • network-interface cards;
  • operating systems;
  • control panels;
  • virtualization software;
  • web servers;
  • databases;
  • PHP;
  • email software;
  • DNS software;
  • Customer applications;
  • third-party applications;
  • backups;
  • restoration;
  • storage integrity;
  • application performance;
  • monitoring systems;
  • NOC response times; or
  • Customer-controlled software or configuration.

Those matters remain governed by the TOS, Support Policy, Backup Policy, applicable product terms, and other portions of the Agreement.


4. Fusion Arc Hosting Infrastructure Model

Fusion Arc Hosting operates a hybrid infrastructure model.

Depending upon the applicable Service and location, infrastructure may include:

  • Fusion Arc Hosting-owned servers;
  • Fusion Arc Hosting-operated servers;
  • Fusion Arc Hosting-owned network equipment;
  • Fusion Arc Hosting-operated network equipment;
  • Fusion Arc Hosting Points of Presence (“POPs”);
  • Fusion Arc Hosting-controlled infrastructure;
  • equipment colocated within third-party datacenters;
  • leased dedicated servers;
  • leased network infrastructure;
  • leased or contracted rack space;
  • contracted datacenter power;
  • contracted network connectivity;
  • cloud or virtualization infrastructure;
  • storage infrastructure;
  • dedicated infrastructure supplied by third parties; or
  • another infrastructure arrangement reasonably used to provide the Service.

Fusion Arc Hosting does not represent that it owns every:

  • datacenter;
  • building;
  • rack;
  • network;
  • fiber route;
  • power system;
  • server;
  • storage platform; or
  • facility

used to provide its Services.


5. Datacenter and Infrastructure Partners

Fusion Arc Hosting may use independent:

  • datacenter operators;
  • dedicated-server providers;
  • colocation providers;
  • network carriers;
  • transit providers;
  • infrastructure providers;
  • storage providers;
  • cloud providers;
  • hardware providers; and
  • other upstream partners.

Current or representative infrastructure partners may include providers such as:

  • InterServer;
  • GTHost / GlobalTeleHost Corp.; and
  • other current or future infrastructure providers selected by Fusion Arc Hosting.

The infrastructure provider used for a particular Service may vary by:

  • Service;
  • server;
  • location;
  • datacenter;
  • availability;
  • capacity;
  • technical requirements; or
  • operational requirements.

Fusion Arc Hosting may add, remove, replace, or change infrastructure providers as reasonably necessary.

The identification of a provider in this SLA does not mean that every Fusion Arc Hosting Service is hosted through that provider.


6. Customer Relationship Is With Fusion Arc Hosting

Unless expressly stated otherwise, the Customer’s Service agreement is with Fusion Arc Hosting.

A Customer does not automatically become a contractual customer of an underlying:

  • datacenter;
  • dedicated-server provider;
  • colocation provider;
  • network provider;
  • transit provider; or
  • other infrastructure partner

merely because that provider supplies infrastructure used by Fusion Arc Hosting.

The Customer’s SLA rights are determined by this SLA and the Fusion Arc Hosting Agreement.

The Customer does not automatically receive or inherit:

  • an upstream provider’s SLA;
  • an upstream provider’s Service Credit;
  • an upstream provider’s refund;
  • an upstream provider’s contractual rights; or
  • another provider’s remedies

unless Fusion Arc Hosting expressly agrees otherwise.


7. Covered Services

Unless expressly excluded by applicable product terms, this SLA may apply to qualifying active paid Fusion Arc Hosting Services including:

  • Shared Web Hosting;
  • WordPress Hosting;
  • CMS Hosting;
  • Semi-Dedicated Hosting;
  • Reseller Hosting;
  • Agency Hosting;
  • Enterprise Hosting;
  • VPS Services;
  • VDS Services;
  • Managed VPS/VDS Services;
  • Dedicated Servers;
  • Bare-Metal Servers;
  • Managed cPanel Services;
  • Managed DirectAdmin Services;
  • Managed Plesk Services; and
  • other infrastructure Services expressly identified as SLA-covered.

The SLA applies only to the qualifying Network and datacenter-power components associated with the applicable Covered Service.


8. Services Not Automatically Covered

This SLA does not automatically apply to:

  • domain registration;
  • domain renewal;
  • domain transfers;
  • standalone software licenses;
  • professional Services;
  • migrations;
  • consulting;
  • custom development;
  • Best-Effort Assistance;
  • third-party SaaS Services;
  • unsupported Customer applications;
  • free Services;
  • beta Services; or
  • experimental Services

unless Fusion Arc Hosting expressly states otherwise.


9. Managed Server and Node Monitoring

Fusion Arc Hosting uses automated and human-assisted monitoring for managed servers and managed infrastructure nodes.

Monitoring is designed to help Fusion Arc Hosting identify:

  • Service failures;
  • server outages;
  • network problems;
  • storage problems;
  • RAID degradation;
  • disk failures;
  • abnormal CPU conditions;
  • abnormal memory conditions;
  • abnormal disk or I/O conditions;
  • network-performance conditions;
  • software-Service failures;
  • infrastructure-health problems; and
  • other operational conditions requiring investigation.

This monitoring forms part of Fusion Arc Hosting’s operational management and incident-response process.

Monitoring does not create an additional uptime guarantee or modify the 99.9% Network and Power SLA.


10. Monitoring Frequency

Fusion Arc Hosting’s automated monitoring systems generally perform health and availability checks at intervals of approximately:

59 seconds

for monitored servers, nodes, Services, or metrics where that monitoring interval is technically supported and configured.

Different monitoring components may operate:

  • more frequently;
  • less frequently;
  • continuously;
  • event-driven; or
  • according to another technically appropriate interval.

The approximately 59-second monitoring interval is an operational monitoring target and configuration, not a contractual guarantee.

Fusion Arc Hosting does not guarantee that every problem will be detected within 59 seconds.


11. Monitored Software Services

On applicable managed servers, automated monitoring may check the operational status of common hosting and system Services including:

  • cpsrvd;
  • LiteSpeed;
  • MariaDB / mariadbd;
  • Exim;
  • Dovecot;
  • SSH / sshd;
  • cron / crond;
  • queueprocd;
  • tailwatchd;
  • Imunify360 WebShield; and
  • other supported system, hosting, security, network, or platform Services.

The monitored Service list may vary according to:

  • server role;
  • operating system;
  • control panel;
  • installed software;
  • product configuration;
  • infrastructure architecture; and
  • operational requirements.

Fusion Arc Hosting may add, remove, replace, rename, or modify monitored components without amending this SLA where the change does not materially alter the contractual Network and Power Availability commitment.


12. RAID, Disk, and Storage Health Monitoring

Applicable managed servers and infrastructure may also be monitored for storage-related conditions including:

  • RAID health;
  • degraded RAID arrays;
  • failed storage devices;
  • disk status;
  • SSD status;
  • NVMe status;
  • filesystem conditions;
  • storage capacity;
  • disk errors;
  • I/O conditions; and
  • other available storage-health indicators.

Storage monitoring is intended to identify potential or actual infrastructure problems so Fusion Arc Hosting personnel can investigate.

The existence of storage monitoring does not guarantee that:

  • a storage device cannot fail;
  • every impending failure can be predicted;
  • RAID will prevent data loss;
  • every storage error will be detected before impact; or
  • every storage failure will qualify as SLA downtime.

13. Resource and Performance Monitoring

Fusion Arc Hosting may monitor managed servers and nodes for operational metrics including:

  • CPU utilization;
  • system load;
  • RAM utilization;
  • swap utilization;
  • disk utilization;
  • disk I/O;
  • IOPS;
  • storage capacity;
  • network throughput;
  • network connectivity;
  • packet behavior;
  • interface status;
  • process activity; and
  • other infrastructure-health metrics.

Thresholds may vary between:

  • server types;
  • hardware configurations;
  • Service classes;
  • locations;
  • workloads;
  • operating systems; and
  • infrastructure architectures.

A threshold being reached does not automatically mean that an outage or SLA violation has occurred.


14. Automated Monitoring and Analysis

Fusion Arc Hosting may use automated scripts, monitoring systems, rule-based detection, statistical analysis, artificial intelligence, machine-learning systems, large language models, or other automated technologies to assist with:

  • anomaly detection;
  • alert classification;
  • incident correlation;
  • Service-health analysis;
  • log analysis;
  • alert prioritization;
  • incident summarization;
  • troubleshooting assistance; and
  • operational decision support.

Automated systems are intended to assist Fusion Arc Hosting personnel.

Fusion Arc Hosting may use human review when evaluating or responding to alerts.

Automated monitoring or AI-assisted analysis does not create a guarantee that every problem will be:

  • detected;
  • correctly classified;
  • correctly diagnosed;
  • immediately resolved; or
  • prevented.

15. Network Operations Center Alerts

When Fusion Arc Hosting monitoring identifies a condition meeting applicable alert criteria, the monitoring system may automatically generate an alert to Fusion Arc Hosting’s Network Operations Center (“NOC”) or other appropriate technical personnel.

Depending upon the condition, alerts may be delivered through:

  • internal monitoring dashboards;
  • automated notifications;
  • escalation systems;
  • messaging systems;
  • email;
  • alerting platforms;
  • incident-management systems; or
  • other operational channels.

Fusion Arc Hosting may prioritize alerts according to:

  • Service impact;
  • number of affected Customers;
  • infrastructure risk;
  • security risk;
  • severity;
  • persistence;
  • redundancy;
  • alert confidence; and
  • other operational factors.

16. NOC Investigation Target

For significant alerts involving a managed server, managed node, or material Service-impact condition, Fusion Arc Hosting generally targets initial NOC acknowledgment or investigation within approximately:

5 minutes or less

after the alert is received by the applicable operational monitoring and escalation systems.

This is an operational response target.

It is not:

  • an SLA;
  • a guaranteed response deadline;
  • a guaranteed resolution deadline;
  • a guaranteed repair time;
  • a guaranteed restoration time;
  • a guaranteed Customer response time; or
  • an automatic basis for Service Credits.

Actual NOC response may vary because of:

  • simultaneous incidents;
  • major outages;
  • security events;
  • widespread network events;
  • monitoring delays;
  • alert delivery failures;
  • infrastructure-provider coordination;
  • datacenter coordination;
  • incident severity; or
  • other operational conditions.

17. Monitoring Does Not Replace Customer Reporting

Fusion Arc Hosting’s monitoring systems provide an additional method of identifying infrastructure problems.

Customers should still report observed Service issues through:

  • Live Chat; or
  • Technical Support tickets.

A Customer may detect an issue before an automated monitoring system does.

Customer reports may assist Fusion Arc Hosting with:

  • diagnosis;
  • impact assessment;
  • geographic troubleshooting;
  • application-specific problems; and
  • conditions not directly visible through infrastructure monitoring.

18. Monitoring Is Not Infallible

No monitoring system can guarantee detection of every technical problem.

Monitoring may:

  • miss an event;
  • detect an event after it begins;
  • generate a false positive;
  • generate a false negative;
  • temporarily lose connectivity;
  • experience software failure;
  • experience provider failure;
  • receive incomplete telemetry;
  • report stale information; or
  • be unable to observe a Customer-specific condition.

Fusion Arc Hosting may use multiple monitoring sources and human investigation when evaluating Service health.


19. Public Service Status

Fusion Arc Hosting maintains a public Service Status system at:

status.fusionarchosting.com

The public Service Status system may be used to communicate information concerning:

  • confirmed outages;
  • network incidents;
  • power incidents;
  • server incidents;
  • node incidents;
  • infrastructure degradation;
  • maintenance;
  • significant software-Service issues;
  • security-related Service disruptions;
  • recovery progress; and
  • other material Service conditions.

20. Client Area Service Status

Fusion Arc Hosting may also display Service Status information within the Customer Client Area.

Depending upon the incident and system capabilities, Customers may receive information through:

  • the Client Area dashboard;
  • Service Status notices;
  • incident notices;
  • maintenance notices;
  • support communications;
  • email; or
  • other appropriate communication channels.

21. Status Publication and Automated Alerts

Automated monitoring may detect and internally alert Fusion Arc Hosting personnel before an incident is publicly posted.

Fusion Arc Hosting may reasonably investigate or validate an automated alert before publishing it as a confirmed public incident.

This helps reduce:

  • false incident reports;
  • duplicate incidents;
  • inaccurate status information;
  • monitoring false positives; and
  • premature conclusions regarding root cause.

Confirmed or material Customer-impacting incidents may be published or updated through the public Service Status system and, where applicable, the Client Area.


22. Service Status Information Is Operational

Service Status pages and incident communications are intended to provide timely operational information.

They may contain:

  • preliminary information;
  • estimated restoration times;
  • evolving incident classifications;
  • estimated causes;
  • partial impact information; or
  • information that later changes as investigation continues.

Fusion Arc Hosting may update, correct, expand, or revise Service Status information as additional technical information becomes available.

A preliminary Service Status report does not create a contractual admission concerning:

  • negligence;
  • SLA eligibility;
  • root cause;
  • damages;
  • liability;
  • Service Credit entitlement; or
  • responsibility for an incident.

23. Monitoring Vendor Confidentiality

Fusion Arc Hosting may use internally developed systems and third-party monitoring, alerting, observability, automation, AI, or infrastructure-management technologies.

Fusion Arc Hosting is not required to publicly identify every:

  • monitoring vendor;
  • software provider;
  • monitoring endpoint;
  • alerting platform;
  • API;
  • automation system;
  • AI provider;
  • threshold;
  • internal rule;
  • credential;
  • monitoring location; or
  • security configuration

used to operate its monitoring environment.

This helps protect:

  • security;
  • infrastructure architecture;
  • competitive information;
  • abuse-prevention mechanisms; and
  • operational integrity.

24. Covered Network Infrastructure

“Covered Network Infrastructure” means the network infrastructure reasonably necessary to provide connectivity to the applicable Covered Service and that is:

  • owned;
  • operated;
  • controlled;
  • leased;
  • contracted;
  • colocated; or
  • directly procured

by Fusion Arc Hosting for delivery of the applicable Service.

Covered Network Infrastructure may include applicable:

  • datacenter switching;
  • routing;
  • network connections;
  • transit connectivity;
  • provider-controlled upstream connectivity;
  • transport;
  • facility network infrastructure;
  • Fusion Arc Hosting POP infrastructure; and
  • other contracted network components serving the Covered Service.

25. Network Availability

“Network Availability” means availability of the Covered Network Infrastructure necessary for the applicable server, hosting node, or Service to communicate with the Internet through the network infrastructure provided or procured by Fusion Arc Hosting.

Network Availability does not mean that every independent network on the public Internet will always be able to reach the Service.


26. Covered Power Infrastructure

“Covered Power Infrastructure” means datacenter electrical-delivery infrastructure supplying power to the applicable physical server, node, rack, or hosting infrastructure.

Covered Power Infrastructure may be:

  • owned by Fusion Arc Hosting;
  • operated by Fusion Arc Hosting;
  • supplied through colocation;
  • supplied by a datacenter;
  • supplied by an infrastructure provider; or
  • otherwise directly procured by Fusion Arc Hosting.

27. Power Availability

“Power Availability” means availability of datacenter-delivered electrical power to the applicable physical server or hosting node.

Covered Power Infrastructure may include applicable:

  • facility utility power;
  • UPS systems;
  • power-distribution infrastructure;
  • generator-backed facility power;
  • rack-level power distribution; and
  • other datacenter-controlled electrical-delivery systems.

Power Availability concerns delivery of electricity to the applicable server infrastructure.

It does not guarantee continuous operation of the server’s own:

  • power supply unit;
  • motherboard;
  • internal power circuitry;
  • storage devices;
  • cooling components;
  • firmware; or
  • other physical hardware.

A server hardware failure occurring while datacenter power remains available does not constitute Qualifying Power Downtime.


28. Qualifying Network Downtime

“Qualifying Network Downtime” means a verified period during which the applicable Covered Service cannot communicate through Covered Network Infrastructure because of a failure within that infrastructure and no exclusion under this SLA applies.

Examples may include a qualifying failure of:

  • datacenter routing;
  • switching;
  • contracted upstream connectivity;
  • Fusion Arc Hosting network infrastructure;
  • Fusion Arc Hosting POP infrastructure; or
  • another Covered Network component.

29. Qualifying Power Downtime

“Qualifying Power Downtime” means a verified period during which datacenter-delivered electrical power is unavailable to the applicable server or hosting node because of a failure within Covered Power Infrastructure and no exclusion under this SLA applies.

A server being offline does not by itself establish Qualifying Power Downtime.


30. Upstream Network or Power Failures

A qualifying Network or Power failure may occur within infrastructure supplied by a third-party datacenter or infrastructure partner.

Where that Network or Power infrastructure is directly procured by Fusion Arc Hosting for the affected Covered Service, Fusion Arc Hosting may treat the verified interruption as Qualifying Downtime under this SLA even though Fusion Arc Hosting does not own the underlying facility.

Eligibility remains subject to all exclusions and requirements contained in this SLA.


31. Upstream Provider Evidence

When an incident involves third-party infrastructure, Fusion Arc Hosting may rely upon:

  • provider monitoring;
  • provider incident reports;
  • provider status information;
  • datacenter reports;
  • network telemetry;
  • power telemetry;
  • Fusion Arc Hosting monitoring;
  • support communications;
  • technical logs; and
  • other reasonably reliable evidence

when determining whether Qualifying Downtime occurred.


32. Monthly Network and Power Availability

Unless a Service-specific written agreement provides otherwise:

Monthly Availability =
(Eligible Minutes − Qualifying Downtime Minutes) ÷ Eligible Minutes × 100

Qualifying Downtime Minutes include verified qualifying Network or Power interruptions.

Where Network and Power interruptions occur simultaneously, the same minute is counted only once.

Eligible Minutes exclude periods excluded under this SLA.


33. Server Hardware Failures Are Not Network or Power SLA Downtime

Failure of server hardware does not automatically constitute Qualifying Network or Power Downtime.

Examples include:

  • hard-drive failure;
  • SSD failure;
  • NVMe failure;
  • RAID-controller failure;
  • motherboard failure;
  • memory failure;
  • CPU failure;
  • network-interface-card failure;
  • server power-supply-unit failure;
  • cooling-component failure;
  • firmware failure; or
  • other server hardware failure.

Hardware systems are physical components and may fail during their operating life.

No hosting provider can reasonably guarantee that physical hardware will never experience a fault or failure.

Fusion Arc Hosting maintains monitoring, repair, replacement, redundancy, backup, migration, and recovery procedures intended to reduce the impact of hardware failures.


34. Hardware Replacement Operational Target

Where Fusion Arc Hosting confirms that a physical hardware component has failed and determines that physical replacement or equivalent hardware remediation is required, Fusion Arc Hosting generally targets completion of the physical replacement or equivalent hardware remediation within approximately:

6 to 12 hours

after the failure has been reasonably diagnosed and replacement has been determined necessary.

This timeframe is an operational target.

It is not:

  • a guaranteed deadline;
  • part of the 99.9% Network and Power SLA;
  • a separate uptime guarantee;
  • a guaranteed hardware-replacement SLA;
  • a guaranteed Service-restoration time;
  • a Recovery Time Objective; or
  • an automatic basis for Service Credits.

35. Hardware Replacement Target Start Time

The Hardware Replacement Operational Target begins after Fusion Arc Hosting has reasonably:

  1. received or detected the incident;
  2. investigated the Service condition;
  3. determined that physical hardware has failed; and
  4. determined that replacement or equivalent physical remediation is required.

Time spent diagnosing whether an incident is caused by:

  • hardware;
  • software;
  • network;
  • power;
  • storage;
  • Customer configuration;
  • operating-system configuration; or
  • another condition

does not necessarily count toward the Hardware Replacement Operational Target.


36. Hardware Replacement Dependencies

Physical hardware replacement may depend upon:

  • replacement-part availability;
  • compatible hardware availability;
  • datacenter access;
  • remote-hands availability;
  • onsite technician availability;
  • infrastructure-provider personnel;
  • equipment inventory;
  • shipping;
  • customs;
  • geographic location;
  • security restrictions;
  • facility procedures;
  • severity of the failure;
  • simultaneous infrastructure incidents;
  • replacement-server availability; or
  • other technical and logistical conditions.

For infrastructure located in facilities not directly staffed or operated by Fusion Arc Hosting, replacement work may require coordination with the applicable infrastructure or datacenter partner.


37. Hardware Replacement Does Not Equal Service Restoration

Completion of physical hardware replacement does not necessarily mean that the affected Service is immediately restored.

Additional recovery time may be required for:

  • RAID rebuild;
  • filesystem repair;
  • operating-system boot;
  • operating-system reinstall;
  • control-panel restoration;
  • virtualization recovery;
  • data restoration;
  • backup restoration;
  • account restoration;
  • database recovery;
  • security verification;
  • network configuration;
  • DNS changes;
  • application verification; or
  • other technical recovery work.

Such recovery work is governed by the Support Policy, Backup Policy, and applicable Service terms.


38. Hardware Target Does Not Create Service Credits

Failure to meet the approximate 6–12 hour Hardware Replacement Operational Target does not by itself create entitlement to:

  • an SLA Service Credit;
  • cash refund;
  • prorated refund;
  • damages;
  • compensation;
  • cancellation without applicable charges; or
  • another remedy.

A separate hardware-replacement SLA applies only where expressly included in a Service-specific written agreement.


39. Storage Failures

Storage failure does not automatically constitute Qualifying Network or Power Downtime.

This includes failure or degradation involving:

  • SSDs;
  • NVMe devices;
  • hard drives;
  • RAID arrays;
  • RAID controllers;
  • filesystems;
  • storage controllers;
  • storage software;
  • data corruption; or
  • other storage components.

Backup and recovery matters remain governed by the Backup Policy.


40. Operating-System Failures

Failure of an operating system does not constitute Qualifying Network or Power Downtime merely because the Service becomes unavailable.

Examples include:

  • kernel panic;
  • boot failure;
  • filesystem errors;
  • operating-system corruption;
  • package failures;
  • update failures;
  • driver problems;
  • software incompatibility; or
  • operating-system misconfiguration.

Fully Managed Services may include troubleshooting and remediation according to the Support Policy.


41. Control-Panel and Hosting-Software Failures

Failure of hosting software does not automatically constitute Qualifying Network or Power Downtime.

Examples include failures involving:

  • cPanel;
  • WHM;
  • DirectAdmin;
  • Plesk;
  • LiteSpeed;
  • Apache;
  • PHP;
  • MariaDB;
  • MySQL;
  • Exim;
  • Dovecot;
  • DNS software;
  • CloudLinux;
  • security software;
  • backup software; or
  • other provider-managed software.

Such incidents may receive technical assistance under the Support Policy but do not automatically qualify for Network or Power SLA credits.


42. Hypervisor and Virtualization Failures

A VPS or VDS hypervisor, virtualization-layer, or parent-node software failure does not automatically constitute Qualifying Network or Power Downtime unless the underlying cause independently qualifies as a Covered Network or Covered Power failure.

Fusion Arc Hosting may use:

  • restart;
  • migration;
  • node repair;
  • host replacement;
  • recovery;
  • restoration; or
  • other technical procedures

to recover affected virtual Services.


43. Application Failures

Application failures do not constitute Qualifying Network or Power Downtime.

Examples include:

  • WordPress errors;
  • plugin failures;
  • theme failures;
  • PHP application errors;
  • Node.js application errors;
  • Python application errors;
  • database-query errors;
  • failed application updates;
  • custom-code defects;
  • CMS errors;
  • API errors;
  • application incompatibility; or
  • third-party application failures.

44. Customer Configuration

Downtime caused or materially contributed to by Customer configuration does not constitute Qualifying Downtime.

Examples include:

  • incorrect DNS;
  • incorrect firewall rules;
  • incorrect routing;
  • application configuration;
  • database changes;
  • deleted files;
  • permission changes;
  • Customer-installed software;
  • security configuration;
  • Customer-controlled operating-system changes;
  • Customer-requested shutdowns;
  • Customer-requested reboots; or
  • other Customer-controlled changes.

45. Resource Exhaustion

Service interruption caused by exhaustion of allocated resources does not constitute Qualifying Network or Power Downtime.

Examples include exhaustion of:

  • CPU;
  • RAM;
  • entry processes;
  • processes;
  • database connections;
  • disk I/O;
  • IOPS;
  • storage;
  • inodes;
  • bandwidth allocations;
  • application workers; or
  • other Service resources.

Resource usage remains governed by the Fair Usage Policy and applicable product terms.


46. Scheduled Maintenance

Scheduled Maintenance does not constitute Qualifying Downtime.

Scheduled Maintenance may include:

  • network upgrades;
  • router maintenance;
  • switch maintenance;
  • power-system maintenance;
  • UPS maintenance;
  • generator maintenance;
  • datacenter maintenance;
  • server maintenance;
  • software maintenance;
  • hardware replacement;
  • storage maintenance;
  • migrations;
  • security updates; and
  • other planned infrastructure work.

Where reasonably practical, Fusion Arc Hosting may provide notice of maintenance expected to materially affect Service availability.

Failure to provide advance notice does not automatically convert otherwise legitimate maintenance into Qualifying Downtime.


47. Emergency Maintenance

Emergency Maintenance does not ordinarily constitute Qualifying Downtime.

Emergency Maintenance may be performed without advance notice where reasonably necessary to address:

  • network instability;
  • power instability;
  • security vulnerabilities;
  • failing infrastructure;
  • hardware failures;
  • imminent equipment failure;
  • data-integrity risks;
  • active attacks;
  • critical software defects;
  • datacenter requirements;
  • vendor requirements; or
  • other urgent technical conditions.

48. DDoS and Malicious Traffic

Network interruption caused by malicious traffic does not automatically constitute Qualifying Network Downtime.

Examples include:

  • DDoS;
  • DoS;
  • packet floods;
  • SYN floods;
  • amplification attacks;
  • reflection attacks;
  • botnet traffic;
  • malicious scanning; or
  • other hostile network activity.

Fusion Arc Hosting may:

  • filter traffic;
  • rate-limit;
  • block traffic;
  • null route;
  • isolate a Service;
  • move a Service;
  • temporarily restrict connectivity; or
  • take other reasonable protective action.

Protective security action does not automatically constitute an SLA violation.


49. Security and Abuse Enforcement

Service interruption caused by reasonable enforcement of:

  • the AUP;
  • FUP;
  • No Spam Policy;
  • security requirements;
  • abuse procedures;
  • DMCA requirements;
  • legal requirements;
  • fraud controls;
  • sanctions requirements; or
  • other applicable policies

does not constitute Qualifying Downtime.


50. Non-Payment

Service interruption caused by:

  • non-payment;
  • overdue invoices;
  • billing suspension;
  • payment failure;
  • chargeback;
  • cancellation;
  • account restriction;
  • fraud review; or
  • termination

does not constitute Qualifying Downtime where the action is authorized by the Agreement.

Billing matters remain governed by the Refund & Payment Policy.


51. Public Internet and Unrelated Third-Party Networks

Fusion Arc Hosting does not control every network between the Customer and the hosting facility.

Failures involving:

  • Customer ISPs;
  • unrelated transit networks;
  • unrelated backbone networks;
  • mobile carriers;
  • enterprise networks;
  • Customer VPNs;
  • external proxies;
  • unrelated peering networks; or
  • other independent Internet infrastructure

do not constitute Qualifying Network Downtime where Covered Network Infrastructure remains available.


52. Third-Party Infrastructure Does Not Automatically Mean Excluded

The fact that Network or Power infrastructure is physically owned or operated by an independent datacenter or infrastructure partner does not by itself exclude the incident from SLA consideration.

Where Fusion Arc Hosting directly procures the affected Network or Power infrastructure as part of the Covered Service, a verified outage may qualify subject to this SLA.

This distinction allows Fusion Arc Hosting to operate Services using:

  • owned infrastructure;
  • colocation;
  • leased infrastructure;
  • contracted datacenter Services; and
  • other infrastructure partnerships

without representing that Fusion Arc Hosting owns the underlying facility.


53. Independent Third-Party Services

Failure of independent third-party Services not forming part of Covered Network or Power Infrastructure does not constitute Qualifying Downtime.

Examples include:

  • payment processors;
  • external APIs;
  • external databases;
  • SaaS providers;
  • external DNS providers;
  • content-delivery networks;
  • registrars;
  • registries;
  • external email providers;
  • Customer-selected software providers; or
  • other independent Services.

54. DNS Propagation

DNS propagation delays do not constitute Qualifying Downtime.

DNS availability may depend upon:

  • authoritative DNS;
  • external resolvers;
  • TTL values;
  • ISP caches;
  • registrars;
  • registries;
  • third-party DNS providers; and
  • Customer configuration.

55. Domain Services

Domain:

  • registration;
  • renewal;
  • expiration;
  • transfer;
  • redemption;
  • registry outage;
  • registrar outage;
  • transfer lock;
  • DNS delegation; or
  • ownership issues

do not constitute Qualifying Network or Power Downtime.

Domain matters are governed separately by the Domain Registration & Renewal Policy.


56. Email Delivery

Individual email-delivery failures do not constitute Qualifying Network or Power Downtime.

Email may be affected by:

  • recipient systems;
  • spam filtering;
  • reputation;
  • blocklists;
  • authentication;
  • DNS;
  • remote-server policy;
  • sender behavior;
  • mailbox configuration; or
  • external providers.

57. Backup and Restoration

Backup and restoration matters are governed by the Backup Policy.

The following do not automatically constitute Qualifying Network or Power Downtime:

  • failed backups;
  • missing recovery points;
  • delayed backup processing;
  • backup corruption;
  • delayed restoration;
  • unsuccessful restoration;
  • disaster-recovery processing;
  • healthy-node recovery time; or
  • unavailable historical data.

58. Support Response Times

Support-response targets are governed by the Support Policy.

The approximate:

  • 59-second Live Chat initial-response target;
  • 59-minute ticket initial-response target;
  • approximately 5-minute NOC investigation target; and
  • Best-Effort Assistance response estimates

are operational targets and are not part of the 99.9% Network and Power SLA.

Failure to meet one of these operational response targets does not automatically create an SLA Service Credit.


59. Hardware Repair and Recovery Time

Time required to:

  • diagnose hardware;
  • replace hardware;
  • repair a server;
  • rebuild storage;
  • rebuild RAID;
  • replace a motherboard;
  • replace memory;
  • replace a processor;
  • replace a power supply;
  • replace a network interface;
  • reinstall an operating system;
  • restore Customer data; or
  • otherwise repair and recover server infrastructure

does not automatically constitute Network or Power SLA downtime.

If the same incident independently includes verified Covered Network or Covered Power downtime, only the qualifying portion is ordinarily considered under this SLA.


60. Recovery and Migration

Fusion Arc Hosting may use migration or recovery procedures when hardware or software fails.

This may include:

  • restoring backups;
  • moving accounts;
  • migrating virtual servers;
  • replacing server hardware;
  • moving Services to another node;
  • assigning new IP addresses; or
  • changing infrastructure.

Recovery work itself does not create a separate Network or Power SLA obligation.


61. Force Majeure

Events outside Fusion Arc Hosting’s reasonable control may be excluded from Qualifying Downtime according to the TOS.

These may include:

  • natural disasters;
  • fires;
  • floods;
  • severe weather;
  • earthquakes;
  • war;
  • terrorism;
  • civil unrest;
  • governmental actions;
  • utility emergencies;
  • widespread Internet failures;
  • catastrophic telecommunications failures;
  • labor disruptions;
  • supply-chain failures;
  • pandemics; or
  • other force-majeure events.

62. Monitoring and SLA Measurement

Fusion Arc Hosting may use:

  • internal monitoring;
  • automated monitoring scripts;
  • network monitoring;
  • power monitoring;
  • server telemetry;
  • Service checks;
  • RAID monitoring;
  • disk monitoring;
  • resource telemetry;
  • facility reports;
  • datacenter reports;
  • infrastructure monitoring;
  • incident records;
  • upstream-provider reports;
  • system logs;
  • AI-assisted analysis;
  • Customer reports; and
  • other reasonably reliable technical evidence

when investigating an incident or determining whether Qualifying Network or Power Downtime occurred.

Fusion Arc Hosting technical records will ordinarily serve as the primary source for calculating SLA downtime.

The existence of an internal monitoring alarm does not by itself establish that an SLA-qualifying outage occurred.


63. Individual Connectivity Problems

A Customer’s inability to reach a Service does not by itself establish Qualifying Network Downtime.

Individual access problems may arise from:

  • local ISP problems;
  • Wi-Fi;
  • routers;
  • Customer firewalls;
  • VPNs;
  • Customer devices;
  • Customer DNS;
  • corporate networks;
  • browser configuration;
  • local routing; or
  • third-party security software.

64. Availability During Provisioning

The SLA generally begins only after the applicable Service has been provisioned and made available for Customer use.

Initial provisioning time does not constitute Qualifying Downtime unless an applicable written agreement expressly provides otherwise.


65. SLA Ends With the Service

The SLA ends when the applicable Service is:

  • terminated;
  • cancelled;
  • expired; or
  • otherwise no longer active.

Time after termination or cancellation is not included in the SLA calculation.


66. Service Credit Eligibility

Where Monthly Network and Power Availability falls below 99.9% because of verified Qualifying Downtime, the Customer may request a Service Credit.

Credits are calculated only against the recurring fee for the affected Covered Service.

They do not ordinarily apply to:

  • domain fees;
  • software licenses;
  • setup fees;
  • migration charges;
  • dedicated IP fees;
  • backup add-ons;
  • security add-ons;
  • taxes;
  • professional Services;
  • one-time charges; or
  • unrelated Services.

67. Standard Service Credit Schedule

Unless a Service-specific agreement provides otherwise:

Monthly Network and Power AvailabilityService Credit
99.9% or greaterNo credit
Less than 99.9% but at least 99.0%10% of affected monthly recurring Service fee
Less than 99.0% but at least 95.0%25% of affected monthly recurring Service fee
Less than 95.0%50% of affected monthly recurring Service fee

68. Multi-Month Billing Terms

Where a Covered Service is billed:

  • quarterly;
  • semi-annually;
  • annually;
  • biennially;
  • triennially; or
  • under another multi-month billing term,

the applicable monthly recurring fee may be determined by dividing the recurring Service charge by the number of months in the billing period.


69. Maximum Service Credit

Unless expressly stated otherwise, total SLA Service Credits for an affected Service for a calendar month may not exceed 50% of the affected Service’s monthly recurring fee.

Multiple qualifying events do not increase the maximum above this amount.


70. Affected Service Only

A qualifying incident involving one Service does not automatically create a credit for:

  • another hosting account;
  • another VPS;
  • another VDS;
  • another dedicated server;
  • domain Services;
  • licenses;
  • add-ons; or
  • other unaffected Services.

71. No Duplicate Compensation

The same event may not generate duplicate:

  • SLA credits;
  • refunds;
  • courtesy credits;
  • downtime credits;
  • settlement payments; or
  • other compensation

for the same underlying incident.

Fusion Arc Hosting may offset another credit already issued for the same event.


72. Service Credits Are Not Cash Refunds

SLA Service Credits are account credits intended for future eligible Fusion Arc Hosting charges.

Unless required by applicable law or expressly agreed otherwise, SLA credits:

  • are not cash refunds;
  • are not redeemable for cash;
  • are not transferable;
  • do not earn interest; and
  • do not create a negative account balance payable in cash.

Refunds are governed by the Refund & Payment Policy.


73. SLA Claim Deadline

A Customer requesting an SLA Service Credit must submit a formal claim within seven (7) calendar days after the qualifying incident ends.

Late claims may be denied unless Fusion Arc Hosting voluntarily reviews the claim or applicable law requires otherwise.


74. SLA Claim Method

Formal SLA Service Credit requests must be submitted through an authenticated Sales & Billing department ticket in the Fusion Arc Hosting Client Area.

The claim should include, where reasonably available:

  • affected Service;
  • approximate incident start time;
  • approximate incident end time;
  • time zone;
  • nature of the reported Network or Power outage;
  • applicable Technical Support ticket;
  • affected server, domain, or IP information; and
  • other reasonably relevant information.

75. Technical Incident Reporting

Active technical outages should be reported through:

  • Live Chat; or
  • Technical Support ticket.

Reporting an active outage allows Fusion Arc Hosting to investigate the technical condition.

A Technical Support ticket, monitoring alert, NOC incident, Client Area notification, or Live Chat report does not by itself constitute a formal SLA Service Credit request.

Technical Support and the NOC handle the technical incident.

Sales & Billing handles the formal SLA credit request.


76. Account Standing

The affected Service and Customer account must generally be in good standing when an SLA claim is submitted.

A Service may be ineligible for SLA credits where:

  • invoices are materially overdue;
  • the Service is suspended for non-payment;
  • the Service has been terminated;
  • unresolved fraud exists;
  • the Service was suspended for a material policy violation; or
  • another contractual condition makes the Service ineligible.

Nothing in this section limits rights that cannot legally be waived.


77. SLA Investigation

Fusion Arc Hosting may review:

  • internal monitoring;
  • automated alerts;
  • network monitoring;
  • power monitoring;
  • server logs;
  • NOC records;
  • incident reports;
  • datacenter reports;
  • upstream-provider information;
  • Technical Support records;
  • public Service Status records;
  • Customer-provided evidence; and
  • other relevant information

when determining whether an incident qualifies.


78. Partial Qualification

If only part of a reported incident constitutes Qualifying Network or Power Downtime, Fusion Arc Hosting may count only the qualifying portion.

For example, an incident may involve:

  1. a qualifying datacenter network interruption; followed by
  2. additional hardware, software, restoration, or recovery time.

Only the qualifying Network or Power portion would ordinarily count toward the Network and Power SLA.


79. Courtesy Credits

Fusion Arc Hosting may issue a courtesy credit even where an incident does not technically qualify under this SLA.

A courtesy credit does not:

  • establish an SLA violation;
  • constitute an admission of liability;
  • create a precedent;
  • modify this SLA; or
  • require the same credit in another situation.

80. Contractual SLA Remedy

To the maximum extent permitted by applicable law and subject to the TOS, the Service Credits described in this SLA are the sole and exclusive contractual remedy specifically provided for failure to satisfy the Network and Power Availability commitment.

Qualifying Downtime does not automatically create entitlement to:

  • a cash refund;
  • lost profits;
  • lost revenue;
  • business-interruption damages;
  • consequential damages;
  • indirect damages;
  • replacement-service costs; or
  • other damages.

All liability remains subject to the TOS.


81. No Admission of Liability

Issuing an SLA Service Credit does not constitute an admission that:

  • Fusion Arc Hosting was negligent;
  • another contractual obligation was breached;
  • the Customer suffered compensable damages;
  • Fusion Arc Hosting caused lost revenue; or
  • additional compensation is owed.

82. Business Losses

SLA credits are not calculated according to alleged:

  • lost sales;
  • lost revenue;
  • lost profit;
  • lost customers;
  • lost advertising;
  • business interruption;
  • opportunity loss;
  • reputational harm; or
  • consequential economic loss.

Credits are calculated solely according to this SLA and the recurring fee for the affected Service.


83. Relationship to Refund Policy

SLA credits and refunds are separate.

Qualifying Network or Power Downtime does not automatically entitle the Customer to:

  • cancellation;
  • full refund;
  • prorated cash refund; or
  • reimbursement of previously paid Service charges.

Refund eligibility is governed by the Refund & Payment Policy.


84. Relationship to Backup Policy

Backup scheduling, recovery points, retention, restoration, and disaster recovery are governed separately by the Backup Policy.

A backup or restoration incident does not automatically create a Network or Power SLA violation.


85. Relationship to Support Policy

The Support Policy governs:

  • Fully Managed support;
  • Self-Managed Services;
  • technical-support scope;
  • response-time targets;
  • escalation;
  • hardware and software troubleshooting;
  • Beyond Scope Assistance; and
  • Best-Effort Assistance.

This SLA does not convert:

  • monitoring intervals;
  • NOC response targets;
  • support-response targets;
  • hardware-replacement targets; or
  • other operational objectives

into Network or Power Availability guarantees.


86. Relationship to AUP and FUP

Fusion Arc Hosting may take actions authorized by the AUP and FUP even where those actions temporarily affect Service availability.

Such enforcement does not automatically create SLA liability.


87. Reseller Hosting

For qualifying Reseller Hosting, any applicable SLA credit is issued to the Fusion Arc Hosting reseller account holder.

Fusion Arc Hosting does not automatically owe separate SLA credits directly to the reseller’s end users.


88. Infrastructure Changes

Fusion Arc Hosting may change:

  • datacenters;
  • infrastructure partners;
  • monitoring technologies;
  • servers;
  • network providers;
  • upstream providers;
  • switches;
  • routers;
  • storage;
  • server hardware;
  • network architecture;
  • colocation arrangements; or
  • other infrastructure

as reasonably necessary to operate and improve the Services.

Such changes do not themselves constitute SLA violations.


89. Service Migration

Fusion Arc Hosting may move a Service to another:

  • server;
  • parent node;
  • network;
  • IP address;
  • rack;
  • datacenter;
  • infrastructure provider;
  • storage system; or
  • compatible infrastructure environment

when reasonably necessary.

The SLA does not guarantee that a Service will permanently remain with one physical facility, infrastructure provider, or hardware platform.


90. No Absolute Availability or Hardware Guarantee

The 99.9% Network and Power Availability commitment is an SLA commitment with the Service Credit remedy described in this Policy.

It is not a representation that:

  • monitoring will detect every condition;
  • a server can never fail;
  • hardware can never fail;
  • storage can never fail;
  • power supplies can never fail;
  • software can never fail;
  • applications can never fail;
  • Customer data can never be lost; or
  • a Service will always remain continuously accessible.

All physical hardware has the potential to experience failure during its operating life.

Fusion Arc Hosting uses reasonable monitoring, redundancy, maintenance, security, replacement, backup, migration, and recovery measures intended to reduce the effect of such failures, but does not represent that physical hardware or software is failure-proof.


91. Support and NOC Communications Do Not Modify the SLA

A statement through:

  • Live Chat;
  • Technical Support;
  • NOC communication;
  • Service Status update;
  • Client Area notice;
  • ordinary email;
  • telephone communication;
  • troubleshooting correspondence; or
  • another informal operational communication

does not amend this SLA unless expressly confirmed through an authorized written contractual process.

A technician’s or NOC representative’s statement concerning:

  • repair time;
  • network restoration;
  • power restoration;
  • hardware replacement;
  • server recovery;
  • root cause;
  • incident severity;
  • expected availability; or
  • estimated resolution

is an operational assessment or estimate and does not create an additional SLA guarantee.


92. Mistaken or Preliminary Information

An incorrect, incomplete, or preliminary statement by an individual employee, technician, NOC representative, automated monitoring system, or Service Status update does not by itself:

  • change the 99.9% commitment;
  • expand SLA coverage to server hardware;
  • expand SLA coverage to software;
  • convert monitoring intervals into guarantees;
  • convert the NOC response target into an SLA;
  • convert the Hardware Replacement Operational Target into a guarantee;
  • remove an SLA exclusion;
  • increase the credit percentage;
  • increase the maximum credit;
  • waive the claim deadline; or
  • modify the Agreement.

Fusion Arc Hosting may correct or update information when additional facts become available.

Nothing in this section limits rights that cannot lawfully be waived.


93. Service-Specific SLA Terms

A particular Service may expressly provide:

  • a different uptime percentage;
  • a guaranteed hardware-replacement commitment;
  • a different hardware target;
  • a different monitoring commitment;
  • a different credit calculation;
  • a different claim period;
  • a different network SLA;
  • a different power SLA; or
  • another availability commitment.

Such terms apply only to the Service for which they are expressly provided and according to the order-of-precedence provisions in the TOS.


94. Historical Availability Does Not Increase the SLA

Historical availability above 99.9% does not increase the contractual commitment.

For example, prior availability of:

  • 99.99%;
  • 99.999%;
  • 100%; or
  • another percentage

does not create a permanent right to that higher availability.


95. Upstream SLA Does Not Expand Fusion Arc Hosting SLA

An upstream provider may advertise or contractually provide a:

  • higher uptime percentage;
  • separate power guarantee;
  • hardware-replacement commitment;
  • different Service Credit; or
  • other SLA.

Those upstream terms do not automatically expand the SLA Fusion Arc Hosting provides to its Customers.

Likewise, a change to an upstream provider’s SLA does not automatically modify this SLA.


96. Prior Credits Do Not Create Precedent

Issuing an SLA or courtesy credit in one situation does not require Fusion Arc Hosting to issue the same credit where a later event does not qualify.

A prior credit does not create:

  • a permanent entitlement;
  • expanded SLA coverage;
  • a different calculation method;
  • a different maximum credit; or
  • a different credit schedule.

97. SLA Changes

Fusion Arc Hosting may update this SLA as:

  • network infrastructure changes;
  • monitoring systems change;
  • datacenter providers change;
  • power infrastructure changes;
  • colocation arrangements change;
  • products change;
  • technologies change;
  • upstream relationships change;
  • infrastructure partners change; or
  • operational requirements evolve.

Material changes will be handled according to the TOS and applicable law.


98. Contact Information

Fusion Arc Hosting
A Fusion Arc Telecom LLC Company

PO Box 1766
Gypsum, Colorado 81637-1766
United States

Technical Support: support@fusionarchosting.com
Sales & Billing: sales@fusionarchosting.com

Active technical incidents should be reported through:

  • Live Chat; or
  • a Technical Support ticket.

Current Service Status information may be available at:

status.fusionarchosting.com

Formal SLA Service Credit claims must be submitted through an authenticated Sales & Billing department ticket.


99. SLA Summary

Infrastructure Model

Fusion Arc Hosting may provide Services using:

  • infrastructure it owns;
  • infrastructure it operates;
  • its own POPs or network infrastructure;
  • colocated equipment;
  • leased equipment;
  • third-party datacenters;
  • contracted power and network infrastructure;
  • dedicated-server providers;
  • infrastructure providers such as InterServer or GTHost; and
  • other current or future infrastructure partners.

Physical ownership of the datacenter is not required for the Network and Power SLA to apply.

Standard Commitment

Eligible Services generally receive a 99.9% Monthly Network and Power Availability commitment.

Covered Availability

The commitment primarily concerns:

  • Covered Network Infrastructure serving the applicable Service; and
  • datacenter-delivered electrical power serving the applicable server or node.

Managed Infrastructure Monitoring

Fusion Arc Hosting generally monitors managed servers and nodes at intervals of approximately 59 seconds where technically supported.

Monitoring may include:

  • cpsrvd;
  • LiteSpeed;
  • MariaDB;
  • Exim;
  • Dovecot;
  • SSH;
  • cron;
  • queueprocd;
  • tailwatchd;
  • Imunify360 WebShield;
  • RAID health;
  • disk and storage health;
  • CPU;
  • RAM;
  • disk I/O;
  • network conditions; and
  • other infrastructure-health indicators.

Monitoring may use:

  • automated scripts;
  • internal monitoring systems;
  • third-party monitoring;
  • rule-based analysis;
  • AI-assisted or large-language-model-assisted analysis; and
  • human review.

NOC Alerts

Qualifying monitoring alarms may automatically alert Fusion Arc Hosting’s Network Operations Center.

For significant managed-infrastructure alerts, Fusion Arc Hosting generally targets initial NOC acknowledgment or investigation within approximately 5 minutes or less.

The monitoring interval and NOC response time are operational targets and are not SLA guarantees.

Service Status

Confirmed or material Customer-impacting incidents may be communicated through:

status.fusionarchosting.com

and, where applicable, through the Customer Client Area and other Service communications.

Hardware

Physical hardware failure is not automatically Network or Power SLA downtime.

Fusion Arc Hosting generally targets physical replacement or equivalent hardware remediation within approximately 6 to 12 hours after a hardware failure has been confirmed and replacement determined necessary.

The 6–12 hour timeframe is an operational target, not a guaranteed hardware SLA or Service Credit commitment.

Hardware and Software Exclusions

The standard Network and Power SLA does not automatically cover:

  • server hardware failure;
  • SSD/NVMe/HDD failure;
  • RAID failure;
  • motherboard failure;
  • CPU or RAM failure;
  • server power-supply failure;
  • operating-system failure;
  • control-panel failure;
  • hypervisor failure;
  • database failure;
  • web-server failure;
  • application failure;
  • Customer configuration;
  • resource exhaustion;
  • backup failure;
  • restoration time;
  • DNS propagation;
  • individual email delivery;
  • support-response time;
  • NOC response time; or
  • hardware-recovery time.

Standard Service Credits

  • Below 99.9% but at least 99.0%: 10%
  • Below 99.0% but at least 95.0%: 25%
  • Below 95.0%: 50%

Maximum Credit

Total SLA Service Credits are generally capped at 50% of the affected Service’s monthly recurring fee for the applicable calendar month.

Claim Deadline

SLA claims must generally be submitted within 7 calendar days after the qualifying incident ends.

Claim Method

Formal SLA claims must be submitted through an authenticated Sales & Billing department ticket.

Remedy

SLA Service Credits are account credits and are the contractual remedy specifically provided for qualifying failure of the Network and Power Availability commitment, subject to the TOS and applicable law.