An interruption of cloud, hosting, or digital platforms can halt sales, orders, customer support, warehouse management, and access to work data. However, a service outage does not automatically grant the right to compensation. It is necessary to understand what the provider was obligated to guarantee, how long the disruption lasted, and what economic consequences actually derived from that outage.
I will discuss the key points that help guide you if your business, including in Milan, has suffered downtime: the contract and the SLA, meaning the service level agreement; the difference between expenses incurred and lost earnings; useful evidence; and the alternatives between restoration, financial claims, and termination of the relationship. The starting point is simple: a technical problem can become a contractual breach, but its consequences must be reconstructed with precision.
When Downtime May Constitute a Breach of Contract
First and foremost, the performance promised in the contract matters. A cloud or hosting service may include infrastructure availability, access to management software, website hosting, backups, technical support, recovery times, or specific security functions. An unreachable website or an unusable program do not always have the same significance: the breakdown must be weighed against the obligations the provider has concretely assumed.
Article 1218 of the Italian Civil Code establishes the general rule of liability for failure or incorrect execution of performance: the debtor is bound to pay damages unless they prove that the breach or delay was caused by an impossibility of performance attributable to a cause not answering for it. The text of the provision is available in the reference to Article 1218 of the Italian Civil Code. The provider's technical explanation alone is not enough to exclude all liability. It must be linked to the contractual commitments, the provided exclusions, and the effective role of the provider.
Scheduled maintenance, communicated in the prescribed forms and times, does not necessarily coincide with a breakdown. Likewise, a slowdown does not always equate to total unavailability. However, a formally reachable service can be practically unusable if it prevents completing payments, issuing transport documents, or accessing data indispensable for business operations. The compromised function is often more important than the technical label of the incident.
SLAs and Contractual Conditions: Why Service Credit Is Not Always the Answer
The SLA must be read together with the main contract. The SLA, an acronym for service level agreement, generally indicates the part of the agreement that defines service availability, methods for measuring downtime, maintenance windows, support response times, and remedies provided in case of failure to meet the promised levels.
Many contracts provide for a service credit, meaning a credit on future fees calculated based on hours of unavailability. This remedy can be useful and immediate, but it does not necessarily coincide with compensation for economic prejudice. A fee credit and business shutdown damages are different items. The clause may establish that the credit is the sole remedy for certain events, provide for caps, or exclude specific categories of damage; its meaning depends on the formulation actually accepted by the parties.
It is essential to identify the applicable version of the terms. In digital services, terms and support plans can change over time; the contract, order, renewal, and communications through which any modifications entered the relationship are relevant to the dispute. It is not enough to download the page currently visible on the provider's website. One must understand which text governed the service on the date of the disruption.
The obligated party must also be identified with care. If you purchased the service from a reseller or someone managing your portal, your contracting party may be different from the cloud infrastructure operator. The fact that the breakdown originates with a third party does not automatically dictate who is liable toward your business. The answer stems from the obligations assumed in the contract you signed and the clauses regulating any external suppliers.
Actual Loss and Loss of Profits: What Can Be Claimed
Compensation can concern both actual losses and missed earnings. Article 1223 of the Italian Civil Code includes the loss sustained and the profit lost insofar as they are an immediate and direct consequence of the breach or delay; you can consult the reference to Article 1223 of the Italian Civil Code. Actual loss is a patrimonial diminution already suffered; loss of profits is the income that the enterprise failed to realize due to the outage.
Actual loss may include, if linked to the disruption and documented, the costs of a replacement service, extraordinary technical interventions, operational recovery, or urgent communications to customers. Not every expense incurred during the emergency is attributable to the provider. One must distinguish a cost necessary to cope with downtime from an ordinary expense or a choice not caused by the interruption.
Loss of profits requires a more accurate reconstruction. For an e-commerce business, initiated but uncompleted orders, interrupted payments, customer messages, traffic data, and comparison with genuinely homogeneous periods may be relevant. For a company working on orders or projects, however, unexecutable deliveries, postponed services, or penalties applied by end clients can matter. Hypothetical turnover does not automatically coincide with lost profit. From the expected revenue, costs that would not have been incurred and extraneous factors that may have impacted sales must also be considered.
If the breach does not depend on willful misconduct, the Italian Civil Code limits compensation to the damage foreseeable at the time the obligation arose, pursuant to Article 1225 of the Italian Civil Code. Predictability also depends on what the provider knew about the use of the service. An informed provider aware that the platform supports a continuous sales channel knows a different risk compared to someone providing a standard service without knowing a particular business criticality.
Proof of Disruption and the Connection to the Loss
A screenshot of the error is useful, but it is rarely sufficient. To reconstruct downtime, tickets, emails, incident notices, monitoring logs, error messages with date and hour, access logs, recovery reports, and reports received from customers may be necessary. These elements make it possible to define not only when the provider opened or closed the incident, but when the service was concretely unavailable to the business.
The next step is the causal link: it must be demonstrated that the invoked loss derives from the outage and not from other reasons. A drop in revenue must be compared with comparable data. Seasonality, promotions, inventory shortages, internal malfunctions, or reduced demand can explain all or part of the same result. Uncompleted orders, missed contractual deadlines, and accounting data close in time instead make the reconstruction more verifiable.
The party suffering the damage must also avoid, with ordinary diligence, an unnecessary increase in consequences. Article 1227 of the Italian Civil Code provides for the reduction of compensation in the event of contributory negligence by the creditor and does not recognize damages avoidable with ordinary diligence; the text can be consulted in the reference to Article 1227 of the Italian Civil Code. Activating an alternative solution does not mean waiving the dispute. Instead, it can serve to contain the shutdown, if the cost and measure adopted are reasonable relative to the emergency.
It is advisable to preserve the chronology of events without alterations: schedules, communications, sales data, activities impossible to perform, and costs incurred. The reconstruction must separate provable facts from merely imagined consequences. This helps both in dealing with the provider and in choosing a financial claim proportional to the available data.
Restoration, Formal Dispute, and Possible Contract Termination
The priority may be restoring the service, not immediately severing the relationship. When cloud or hosting is essential, the business must first prevent the outage from prolonging. A written formal notice can accompany the opening of the technical ticket, clarifying the lamented disruption, the need for restoration, and the intention to keep the claim for emerging damages reserved.
The request to the provider must also comply with the procedures set out in the contract: some SLAs impose a channel, a deadline, or specific data to request service credit. Reporting the breakdown to support and formulating a contractual dispute are different steps. The former normally serves to obtain restoration; the latter defines what is being contested and the economic consequences intended to be enforced.
In bilateral contracts, the party suffering the breach can request performance or termination, without prejudice to compensation for damages, pursuant to Article 1453 of the Italian Civil Code. Termination is not automatic for every disruption. The contract cannot be terminated if the breach is of minor importance with respect to the interest of the other party, as specified by Article 1455 of the Italian Civil Code.
An express termination clause can attribute relevance to the violation of obligations identified by the parties. Article 1456 of the Italian Civil Code requires, in this case, that the interested party declare their intention to avail themselves of the clause. Before migrating data or terminating the service, operational continuity and data export must be considered. A hasty choice may solve an immediate technical problem but create another on an organizational or contractual level.
Frequently Asked Questions
Can I claim loss of profits for sales lost during the outage?
Yes, if the missed earnings are demonstrable and linked to the downtime. Uncompleted orders, traffic data, conversion history, margins, and comparisons with homogeneous periods can help quantify it. Theoretical turnover is not enough on its own, because compensation concerns actual prejudice and not a commercial forecast lacking evidence.
Does the credit provided by the SLA close every compensation claim?
Not necessarily. Service credit is often a contractual remedy calculated on the fee, but one must read whether the contract indicates it as an exclusive remedy, what events it covers, and what limits it establishes. Its presence does not allow stating, without examining the applicable clauses, that any further claim is permitted or excluded.
Can I contest the damage if the provider attributes the breakdown to a third party?
You can contest the disruption to your contractor, verifying what obligations they assumed. The technical origin of the incident is an important fact, but it does not dictate liability on its own. The contract, SLA, and clauses on external infrastructure, non-imputable causes, and support indicate the perimeter of the promised performance.
Must I activate an alternative service to limit damages?
It is advisable to adopt reasonable measures to contain the shutdown. An alternative channel can prevent the damage from increasing and does not in itself entail waiver of the dispute. However, the cost must be documented and proportional to the situation, while the adopted solution must be truly suitable for keeping essential functions operational.
Can I immediately terminate the cloud or hosting contract?
Termination depends on the severity of the breach and the contract. A brief episode without significant consequences may not be sufficient; a serious, prolonged, or repeated outage may carry a different weight. Before severing the relationship, termination clauses, scheduled procedures, data recovery, and operational continuity must be considered.
When It Is Useful to Address the Contractual Problem Immediately
It is useful to intervene when the outage has impacted revenue, customers, or operations, and reliable data are still available. Contracts, orders, SLAs, tickets, communications, technical logs, and economic data of the period in question allow distinguishing documented disruption from a merely hypothesized loss. The decision to change providers must also be coordinated with the possibility of exporting data and keeping essential services active.
If your company operates in Milan and downtime has produced significant economic consequences, we can help you frame the contract and the claim within the limits of provable facts. The objective is to clarify whether the remedy provided by the SLA is sufficient, which damages find concrete evidence, and which initiatives are compatible with the continuity of your business.