Service level agreement (SLA)

Last updated:

Our commitment to the availability of the services (SLA): how it is measured, what is not considered downtime, and what credit you receive if we do not meet it.

This English version is provided for convenience only. The Hebrew version is the binding version.

Important to know: no online service can operate entirely without interruptions. If your business cannot tolerate downtime, use a redundancy solution, for example an additional server in another location. In any case, always keep backups of your own.

The commitment at a glance

Availability in the service year

Cumulative downtime in a 365-day service year

Credit

99% or more

Up to 87.6 hours (3.65 days)

No credit, the commitment was met

Less than 99%

More than 87.6 hours

100% of the monthly price, and the right to stop the service

The service year starts on the day the service is activated (section 2.2). The credit is given on request (chapter 6) and is offset against the next charges on the account.

1. What the Agreement applies to

In brief: The Agreement is part of the Terms of Service, and applies only to the services and components listed in it. It does not apply to what is inside a VPS or a dedicated server, or to your own equipment. Only the customer who pays us for the service is entitled to a credit.

1.1 This service level agreement (the "Agreement") is part of the Terms of Service, and sets out the availability commitment in chapter 8 of the Terms of Service. Terms that are not defined in the Agreement have the meaning given to them in the Terms of Service.

1.2 The Agreement applies to the following services, and in each of them only to the components listed next to it:
(a) web hosting (shared hosting), reseller hosting, and business email: the server on which the account runs is accessible from the internet, and the server services used in it for websites, mail, and databases, to the extent they are part of the service, are working;
(b) virtual private servers (VPS) and cloud office: the virtual server is running and connected to the network;
(c) dedicated servers that we rent out: the server receives power, is connected to the network, and its hardware is in working order;
(d) cloud backup: the backup storage is accessible from the internet;
(e) equipment colocation in the data center: the equipment receives power and is connected to the network.

On a VPS and on a dedicated server, the commitment does not include the operating system and the software inside the server, even when you have ordered a management service or a server on which we installed an application (section 3.5 of the Terms of Service). In equipment colocation, the commitment does not include the equipment itself.

1.3 The Agreement does not apply to other services, including server management, email marketing servers, internet radio servers, website and server monitoring, security services and software licenses, domain registration, website and app development, SSL certificates, and Cloudflare services. Nor does the Agreement apply to backups included in the plans of other services (section 6.3 of the Terms of Service), to a service provided free of charge or for a trial period, or to a service, feature, or version that we have marked as experimental (Beta) or as a preview.

1.4 Credits are given only to the customer who contracts with us and pays us for the service. When the service is used by a Reseller (section 3.11 of the Terms of Service), the Reseller is the one entitled to the credit, and Reseller Customers are not entitled to it (section 3.12 of the Terms of Service).

1.5 The Agreement prevails over general provisions of the Terms of Service only in the matters it governs: the services covered by the commitment, the method of measurement, the cases that are not downtime, the credits, the right to stop a service, and changes to the Agreement. In any other matter, the Terms of Service apply. Section 1.9 of the Terms of Service also applies to the Agreement. A service for which a separate service level agreement has been signed is subject to section 8.3 of the Terms of Service.

1.6 The table at the top of the page, the headings, and the "In brief" summaries are for orientation only and are not binding, and the sections prevail.

2. The availability commitment

In brief: We commit to at least 99% availability in each service year, meaning cumulative downtime of no more than 87.6 hours a year. Downtime is time during which the service is not working because of a fault in infrastructure under our responsibility, and only an interruption of at least 15 consecutive minutes is counted.

2.1 For each service in section 1.2, we commit to at least 99% availability on an annual average, starting from the first day of the service. This means that the cumulative downtime of the service in each service year will not exceed 1% of the hours in it: 87.6 hours (3.65 days) in a 365-day year, and 87.84 hours in a 366-day year.

2.2 "Service year" is a period of 12 months. The first service year starts on the day the service is activated, and each service year starts at the end of the previous one. Downtime that continued past the end of a service year is counted in each year according to the hours that fell in it. If the service ended before the end of the service year, availability is calculated according to the hours during which the service was active in that year.

2.3 "Downtime" is time during which a component of the service, as listed next to it in section 1.2, is not working or is not accessible from the internet, because of a fault in infrastructure under our responsibility: the network and the internet connection, power and cooling, hardware and virtualization, and, in the services in section 1.2(a), also the server services listed there. Only an interruption that lasted at least 15 consecutive minutes is counted, and a shorter interruption is not downtime.

2.4 Availability is checked for each service separately, and downtime of one service does not entitle you to a credit for another service on the account. A single event is counted only once for each service, even if several components were affected by it.

2.5 No online service can operate entirely without interruptions. If your business cannot tolerate downtime, use a redundancy solution, for example an additional server in another location. In any case, always keep backups of your own (section 6.1 of the Terms of Service).

3. How availability is measured

In brief: Availability is calculated according to our monitoring systems, and we also take into account data you provide. Downtime is counted from the time we detected it or the time you reported it, whichever is earlier.

3.1 Availability is calculated according to the data of our monitoring systems.

3.2 Downtime starts at the time our monitoring systems detected it or you reported it in the support center (HelpDesk), whichever is earlier, provided that the service was in fact not working at that time. It ends when the service is working again.

3.3 When reviewing a credit request, we will also take into account data you provide to us, for example from reports of an external monitoring service. If there is a difference between the data, we will explain in our response the data we relied on.

4. What is not considered downtime

In brief: Maintenance, a fault caused on your side, an attack directed at your service, suspension or blocking under the Terms of Service, a fault outside our network, and slowness are not downtime. An interruption of power, cooling, or communications and a failure at our providers are considered downtime, except in exceptional events such as war, a natural disaster, or a cyberattack on our network or infrastructure, or on the data center, that could not have been prevented by reasonable means.

4.1 The following times are not considered downtime:
(a) proactive, planned, or urgent maintenance work, carried out to a reasonable extent and in good faith, for the operation, upgrade, or security of the service, including replacing a server or changing an IP address (section 8.5 of the Terms of Service), whether or not we announced it in advance (section 8.4 of the Terms of Service). The time during which the service is not working because of a fault, until the fault is fixed, is not maintenance;
(b) a fault caused by your content, code, settings, or software, by load that exceeds the plan's resources, or by a breach of your website, account, or server, whose security is your responsibility (section 5.1 of the Terms of Service);
(c) a fault caused by your failure to act on a written notice you received from us, for example to update software, fix a vulnerability in the website, or upgrade the plan, or by outdated software whose updating is your responsibility;
(d) an action you performed, or asked us to perform, such as a restart, a restore from backup, a reinstallation, or an upgrade;
(e) suspension, restriction, or blocking of the service or of part of it under the Terms of Service, including under sections 2.16, 2.17, 5.6, 11.3, and 11.4 of the Terms of Service;
(f) an attack directed at your service, such as a denial-of-service (DDoS) attack, and the actions we take to block it;
(g) blocking or restricting access from certain countries, networks, or IP addresses, under section 5.5 of the Terms of Service;
(h) a fault outside our network and outside its connections to the internet, including at your internet providers or those of website visitors, at another DNS provider, at Cloudflare or another provider you use, or at a domain registry. A failure of an external protection or acceleration service provided at no additional charge, such as Cloudflare, is not considered downtime, even when we activated it;
(i) a force majeure event under section 12.8 of the Terms of Service, except for the cases in section 4.2.

4.2 An interruption of power, cooling, or communications, and a failure at a provider we use, such as the data center operator or an infrastructure provider, are considered downtime, even when they are a force majeure event under section 12.8 of the Terms of Service. They are not considered downtime only if they were caused by war, by hostilities, by terrorism, by a cyberattack, including a denial-of-service (DDoS) attack, on our network or infrastructure, or on the data center, that we could not have prevented by reasonable means, by a natural disaster, by an instruction of a competent authority, or by a power outage in the national grid that lasted beyond the backup capacity of the data center. This section applies for the purposes of the Agreement only, and does not change section 12.8 of the Terms of Service in any other matter.

4.3 The following are not downtime either: slowness, a fault in a feature of the service that is not one of the components in section 1.2, the listing of an IP address in a blocklist, and mail that was not delivered because of filtering or blocking at another provider. In cloud backup, availability does not include the existence or integrity of the backups (section 6.4 of the Terms of Service).

5. Credits and the right to stop the service

In brief: If the availability of a service in a service year is below 99%, you will receive, on request, a credit of 100% of the monthly price. The credit is offset against the next charges on the account, and if you have stopped all the services, its balance is refunded to you, less any debt. In this case, you may also stop the service immediately, without cancellation fees, by a request submitted within 30 days of the time the downtime exceeded 1% of the hours in the service year. If you stopped the service, the proportional part paid for the days after the stop will be given as a credit on the account, even beyond the annual credit cap.

5.1 If the availability of a service in a service year was below 99%, meaning its cumulative downtime exceeded 1% of the hours in it, you will receive, on request (chapter 6), a credit of 100% of the monthly price, as well as the right in section 5.6. Availability of 99% or more does not entitle you to a credit.

5.2 Entitlement to a credit is determined according to the availability in the entire service year, and, for a request submitted during the year, according to section 6.2. The maximum credit under section 5.1 for a service in a service year, including a credit given during the year, is 100% of the monthly price. The cap does not apply to the credit for the days after the service is stopped under section 5.6.

5.3 "Monthly price" is the price you paid for the affected service in the last service month before the request in that service year, after discounts and excluding one-time payments. For a service paid in advance for a longer period, the monthly price is the amount paid for the period, divided by the number of months in it.

5.4 Downtime that occurred while the account had a debt whose payment date had passed, or while the service was suspended or restricted because of a breach of the terms, does not entitle you to a credit. As long as the service is suspended because of such a breach, we will not approve a credit request for it.

5.5 An approved credit will be offset against the next charge on the account, for the same service or for another service, and against the charges after it until it is used up. The credit cannot be transferred, and as long as the account has an active service, it is not given in cash. An approved credit that has not been used by the time all the services on the account have ended will be refunded to you under section 11.2 of the Terms of Service, subject to set-off under section 2.16 of the Terms of Service.

5.6 If the cumulative downtime of a service in a service year exceeded 1% of the hours in it (87.6 hours in a 365-day year), you may also stop that service immediately, without cancellation fees and without the advance notice in section 11.1 of the Terms of Service. The request is submitted in the manner set out in section 11.1, within 30 days of the time the downtime exceeded 1% as stated above. The proportional part of the payment for the days after the stop, including from a period paid in advance, will be given as a credit on the account, which is not subject to the cap in section 5.2, and section 5.5 will apply to it.

6. How to request a credit

In brief: A credit request is submitted in the support center, within 30 days of the end of the service year or of the end of the service. You may also submit it during the year, once the cumulative downtime has exceeded 1% of the hours in the service year.

6.1 A credit request is submitted by opening a ticket in the support center (opens in a new tab), within 30 days of the end of the service year, or of the end of the service if it ended earlier. You may also submit it during the year, once the cumulative downtime has exceeded 1% of the hours in the service year. In the request, state the service and the times when it was not working, and if you have data, attach it. After the deadline in this section, a credit cannot be requested for that service year.

6.2 We will respond to the request in the support center, with details of the calculation. For a request submitted during the year, entitlement to a credit will be determined according to the downtime accumulated up to the date of the request, out of all the hours in the service year. A credit given during the year is the full credit for that service year, and no additional credit will be given for that year under section 5.1.

7. Remedy and changes to the Agreement

In brief: The credits and the right to stop the service are the sole remedy for downtime, to the extent the law permits. A change that reduces the commitment or the credits will apply to an active service only from its next service year, after advance notice.

7.1 The credits and the right in section 5.6 are the sole remedy for failure to meet the availability commitment, to the extent the law permits and subject to section 12.5 of the Terms of Service.

7.2 We may update the Agreement from time to time. A change in your favor applies from the day it is published. Any other change that does not reduce the commitment or the credits applies under section 13.1 of the Terms of Service.

7.3 A change that reduces the commitment or the credits will apply to an active service only from the start of its next service year, and after advance notice under section 13.2 of the Terms of Service. If you do not agree to the change, you may stop the service before the change applies to it, without cancellation fees, even if fewer than 7 days remain until the end of the service period (section 11.1 of the Terms of Service), and without a refund (section 11.2 of the Terms of Service).

Shopping cart

Your cart is emptyYou can start with one of our popular plans.

Site search

Accessibility

Text size
100%
Accessibility statement