Canada: Demystifying Cloud Service Levels

Last Updated: November 17 2015
Article by Lisa R. Lifshitz

Service levels can sometimes be the "orphan children" of a cloud transaction — often neglected and not given the attention they deserve.

Some technology lawyers are reluctant to review and comment on service levels, preferring to leave their negotiation to the client's business or technical experts.  However, lawyers can play a crucial role in vetting service-level agreements as part of creating an effective cloud arrangement.  

While many cloud providers will be reluctant to negotiate customized service levels for specific customers in the absence of a large-volume public cloud deal or the acquisition of a private cloud solution, there are still ways to improve even the most vanilla of service-level agreements. The following tips are intended to help demystify service levels/service-level credits and include some suggestions for creating better service-level agreements.

Service levels are important

At their most basic, service levels are intended to compensate customers for a cloud provider's failure to deliver cloud services to their promised levels, usually by way of service credits (providing customers with rebates against further billings). As service levels are not standardized, customers sometimes find it difficult to compare the offerings of various cloud providers. Depending on the nature of the cloud service, service levels can include measuring for uptime/availability, performance and response times, incident priority/correction times, etc.  

Service levels are often made available in a stand-alone SLA separate from the cloud provider's master services agreement, which may cause its own difficulties from a contract perspective. This SLA may or may not be hyperlinked to the cloud MSA and is often available on the cloud provider's web site, allowing the vendor to amend it at will.

The onus is thus on the customer to monitor for changes. Regardless of where the SLA is to be found, in the cloud 2.0 world, almost every reputable vendor will offer basic service levels. The failure of a prospective vendor to offer even minimum service levels is a definitive "red flag" that should strongly signal that particular vendor is not right for your organization. At the same time, any cloud provider that offers a customer an overly generous service level or service credit, i.e., "10,000-per-cent service credit equivalent to 100 times the customer's fees" on the service, is not to be trusted, either.

Ensure the SLA is understandable

Some SLAs are written so poorly or technically that their plain meaning is difficult to understand. While service levels and service credits can be complex, they still have to be intelligible. Start with the basics — what is the service level actually measuring? Will the cloud provider be monitoring the service for breaches of service levels or is it the customer's responsibility to do so and to alert the vendor? Do the vendor's proposed planned-maintenance downtime windows align with the customer's requirements? What is the measurement period? If there is a formula/calculation to receive credits, does it make sense? While generally credits are calculated as a percentage of the fees (i.e.,  monthly fees) the customer has paid, where does the measurement begin? Is there a maximum credit cap? Are the exclusions clear? Focus on the key definitions, such as "availability", "downtime", "excluded downtime", etc. If the language used by the vendor is not clear, demand clarifications as it is likely that a judge wouldn't understand it either.   

SLAs or SLOs?  

When reviewing a proposed SLA, be careful to distinguish between service levels and service-level objectives. SLOs are essentially "aspirational" — often there are no repercussions if they are not met. Any aspect of the cloud service that a customer wishes to meaningfully measure must, therefore, be a service level with a definitive remedy for breach. Following any incident that affects performance, the cloud vendor should perform an analysis to identify the cause of the failure, provide the customer with a written report of the results of such analysis and the procedure for correcting the failure, and keep the customer informed of the status of the cloud vendor's remedial efforts regarding such failure. Remedies should also start immediately following the first missed service level — unlike one vendor that stated that, in the first month of missed availability, the vendor's sole commitment was to promise that "the parties would meet to discuss possible corrective actions."

Watch for those carve-outs and "gotchas"

It is standard for SLAs to contain many "carve-outs," including excluding the provision of emergency maintenance from "downtime" calculations (and often intermittent downtime does not count toward downtime calculations either). Most cloud providers will not take responsibility for factors outside their immediate control, including Internet routing, traffic issues affecting Internet links, third-party software, customer-provided software, or missed service levels due to force majeure events. However, what about jurisdictional limits? Should the cloud vendor be able to exclude meeting a service level because of system work at the request of customer, system shutdowns caused by customer customizations, or faults in the customer's network, LAN, or firewall? What about "non-fulfilment or violation of customer's duties of collaboration"? Be mindful of unreasonable exclusions and request their deletion if possible.  

Review customer responsibilities carefully

Service credits often come with "strings" attached. Many SLAs now tie the provision of credits to a customer's obligation to meet ever-increasing obligations. For example, a customer is obliged to notify the cloud provider via e-mail within a certain number of days of any claims for credits following an incident (and be obliged to provide such details as downtime information with dates and time period for each instance of downtime during the relevant period, and an explanation of the claim made under the SLA, including relevant calculations). Failure to do so within such period will result in forfeiture of any credits.  
Many cloud vendors consider the responsibilities around the use of the cloud service to be "shared" and will withhold credits if a customer fails to meet its own obligations.  These may include: misusing access rights, violating the cloud agreement or the acceptable use policy, or if customer's use of the cloud service is not in accordance with the documentation for such cloud service.  

Cloud providers have also refused to be responsible for failures to meet an SLA if the failure is caused by a customer declining to accept patches, configurations, or maintenance changes recommended by the cloud vendor. Consider, for example, whether your customer would be comfortable giving a representation that it can make the software hosted by the cloud vendor rightfully available to such vendor, or provide a representation that the customer's data is virus-free, has been collected/supplied in compliance with applicable laws (including data privacy and export compliance laws), or that it changes its passwords at regular intervals?  

Failure to comply with the above has led at least one cloud provider to deny its obligation to meet its stated service levels. It is now fairly common for many SLAs to state that the cloud vendor will not have responsibility to meet service levels if the customer is late with its payments or otherwise has monies owing to the cloud vendor.  If your organization typically does not meet its payment schedules, it will be critical to ensure that you modify the cloud agreement's standard payment terms so that your enterprise is not caught without a service-level remedy.

Negotiate termination rights  

Most SLAs state that the provision of service credits is the customer's sole remedy for breach of a service level/SLO and that failure to meet an SLO is not a material breach of the cloud agreement. This limitation can serve as an important disincentive to vendors as there will be no real penalty for continued service interruption. However, customers that continually experience ongoing intermittent outages or service-level failures will not likely wish to continue with a cloud vendor that has offered poor service, and even generous credits against future billing will be of little or no benefit if such customer now wants to switch providers following inconsistent service. A better approach is to draft in a requirement that repeated service-level failures measured over a period of months — i.e., failure to meet the same SLA within any rolling three- or six-month period — be grounds for termination.

To conclude, having robust service levels with actual credits involved for breaches of performance remains an important part of any balanced cloud-computing arrangement.  As no two cloud vendors have the same offerings, careful review of the SLA prior to the deal should be part of the due diligence and negotiation process during the acquisition of mission-critical cloud services. If service levels are important to you or your clients, be certain to escalate their negotiation to the front of the deal rather than left as an after-thought.

Once the language in the SLA has been clarified, you must also ensure that your cloud contract/cloud service is governed by the updated version of the SLA rather than boilerplate version hyperlinked on the cloud vendor's web site.

Originally published on Canadian Lawyer Online - IT Girl Column

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Lisa R. Lifshitz
In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.