Service Level Agreement (SLA)
ამ დოკუმენტის ქართული ვერსია ჯერ არ გამოქვეყნებულა. ქვემოთ ინგლისური ვერსიაა მოცემული.
Last updated: 10.11.2026 · Provider: JEZA CLOUD LLC (TIN 1606154731)
Scope: cloud.jezahost.com: cloud servers (VPS / IaaS), email hosting, static IP address
This document sets out the measurable commitments of the service. Payment, cancellation and use conditions are in the "Terms of Service"; in case of conflict this document prevails on service level matters only. Definitions are in Terms of Service §1.
1. Scope
Included:
- operation of the virtual server (VM), availability of the hypervisor and the storage system
- availability of the network connection
- availability of the management panel (
cloud.jezahost.com) - the backup service, where selected (its coverage is in §6)
- in email hosting: access to mailboxes (IMAP/SMTP/webmail) and acceptance of incoming mail
Not included:
- the operating system, software, configuration and data inside the VM
- the customer's own error (wrong firewall rule, full disk, wrong restore, lost password, exhausted resources)
- the customer's external services (domain, DNS provider, third-party APIs)
- planned technical works (see §4)
- force majeure: natural disaster, failure of a power or transit supplier, a decision of a state authority, large-scale DDoS attack
- a service suspended under Terms of Service §8 or for non-payment
The following are NOT SLA commitments (deliberately):
| What | Why |
|---|---|
| Actual network port throughput | The port is "up to 1 Gbit/s" (Terms §6.3). The uplink is shared; the SLA measures the AVAILABILITY of the connection, not its speed. |
| DDoS protection | Not included in the service. Temporary blocking of an address's traffic during an attack does not count as downtime (Terms §6.3). |
| Archive disk (SAS) throughput | The archive tier is a shared and deliberately slower resource. The figures shown on the portal are indicative. |
| Backup of the archive disk | The archive disk is not backed up (§6.1, Terms §6.4). |
| Traffic volume | Not metered and not automatically capped. |
| Delivery of mail to third-party servers | The receiving party's filters, blocklists and reputation systems are outside our control. |
| Correctness of the customer's DNS records | MX/SPF/DKIM/DMARC on the domain side are the customer's responsibility (Terms §7.2). |
| Support response time | A target time, not tied to compensation (§5). |
2. Availability commitment
Monthly availability: 99.9%
This means a maximum of about 43 minutes of unplanned downtime in a calendar month (for a 30-day month; about 45 min in a 31-day month, about 40 min in February).
Measurement rules:
- the unit of measurement is each service separately (downtime of one VM is not attributed to another; email hosting counts as a separate service)
- downtime is determined from the records of our monitoring system; the customer may submit their own measurements and, where these differ, the records are reviewed together
- interruptions shorter than 5 minutes are not accumulated
- cases listed in §1 as "not included" or "not an SLA commitment" are not added to downtime
3. Compensation
Where the commitment is breached, compensation is credited to the account balance. The customer is not entitled to demand payment of compensation in cash or its return to a bank account (Terms of Service §5.3).
| Actual monthly availability | Compensation (of that service's monthly amount) |
|---|---|
| 99.0% – 99.89% | 5% |
| 95.0% – 98.99% | 15% |
| below 95.0% | 30% |
Rules:
- compensation is not granted automatically; the customer must open a support ticket within 15 days of the incident
- the basis for compensation is the service's monthly amount. Where payment was annual, the basis is the annual amount divided by 12, that is, the amount attributable to one month; no percentage is calculated on the annual amount itself
- for a service under a campaign, the basis is the monthly amount actually paid (after the discount)
- the calculation is made once per month, on that service's actual monthly availability; compensation is not granted twice for the same month
- the maximum compensation for one month is 30% of that basis
- compensation is credited to the account balance and is used to pay invoices as described in the Terms of Service §3
- no compensation is granted for a service that is overdue or suspended
- the included static IP is free of charge, so there is no compensation basis for it (Terms §6.2)
4. Planned technical works
- planned works are as a rule carried out at the weekend
- notice is given at least 72 hours in advance by email and/or a panel notification
- the duration of planned works is not counted towards availability
4.1 Shortened notice
The 72-hour period may be shortened and, where necessary, notice may be given during or after the work, in the following cases:
- security: critical vulnerability, active attack, urgent patch
- hardware/infrastructure risk: risk of failure of a disk, memory, power or cooling unit; prevention of data loss
- upstream supplier: works notified at short notice by the data centre, a transit/carrier provider or a hardware manufacturer; in such cases we do not learn of them in advance either
- force majeure as listed in §1
In these cases the customer is notified at the earliest practically possible time, and the reason for the work is explained afterwards.
5. Support
- channel: support tickets inside the portal and email [email protected]
- support hours: every day, weekends included, 08:00–24:00 (Baku time)
- response time: within 2 hours for a request received during support hours; for a request received outside support hours, within 2 hours after 08:00 the next day
- monitoring runs continuously; if a node fails, VMs are started automatically on another node without human intervention
The response time is a target time: it is not tied to the compensation in §3, and exceeding it is not a ground for compensation.
Information about critical incidents (mass outage) is published in the panel and by email without waiting for a customer to ask.
6. Backups and restore
Backup is a paid add-on (Terms of Service §6.5). This section applies to services for which it has been selected.
| Parameter | Value |
|---|---|
| Backup frequency | at least once per day (automatic) |
| Available for restore in the panel | backups from the last 7 days |
| Restore | performed by the customer from the panel |
| Daily restore limit | 3 per service |
| Effect of a restore | disk contents return to the state of the backup |
6.1 WHAT the backup COVERS
| Covered | NOT covered |
|---|---|
| system disk | archive disk (SAS) |
| additional NVMe disks | - |
Backing up data on the archive disk is entirely the customer's responsibility. This is part of the pricing model: the archive tier is cheap precisely because it is not backed up.
The volume backed up is not selected by the customer; it is derived from the sum of the system disk and the additional NVMe disks.
6.2 Important conditions
- All data after the backup date is lost and cannot be recovered.
- If a restore reduces disk size to that of the backup, the paid capacity is returned automatically; no further charge is made. Expanding the file system is the customer's responsibility.
- The backup service does not replace the customer's own backups. For critical data the customer must keep an independent copy.
- Backups are for disaster recovery only; extraction of individual files is not covered by any commitment.
- In practice backups may be taken more often; this document states the minimum commitment.
- Because of technical rotation, older backups may be kept somewhat longer than 7 days; they are not offered for restore and are deleted no later than 35 days (Privacy Policy §8).
6.3 Mailboxes
Mailbox contents are stored on our own infrastructure. A mailbox deleted while the service is active is retained for 30 days for restoration (Terms §7.5). This is a separate mechanism from VM backups and gives no commitment to restore an individual message.
6.4 Disaster-recovery copies (data-centre loss)
We additionally keep copies of the system and NVMe disks of all virtual servers at a secure storage location that is geographically separate from the primary data centre ("disaster-recovery copies"). They exist solely to restore the service if the primary data centre is lost entirely or for a prolonged period (a disaster).
| Parameter | Value |
|---|---|
| Purpose | recovery after a data-centre disaster only |
| Data-loss target (RPO) | up to 12 hours |
| Recovery time (RTO) | not guaranteed |
| Who restores | the provider only |
- Disaster-recovery copies are separate from the paid backup service in §6: they are not shown in the panel, cannot be selected by the customer for a restore, and the customer is not entitled to request an individual restore from them.
- They also cover servers of customers who have not purchased the backup service; this does not give those customers the rights described in §6.
- The RPO is a target, not a guarantee. In a disaster, data from up to the last 12 hours (or a longer period if creating or transferring a copy has failed) may be lost. Missing the RPO does not give rise to compensation under §3.
- The archive disk (SAS) is not included in disaster-recovery copies either (§6.1).
- After a disaster, recovery may take place on different hardware and with different IP addresses.
- Disaster-recovery copies do not replace the customer's own backups.
- Where this SLA or the Terms of Service require backups to be deleted (including immediate deletion), disaster-recovery copies are deleted automatically no later than 35 days after that event and are not used for any purpose in the meantime.
7. Resources and changes
- Upgrades (CPU, RAM, disk, additional disk, mail seat) are possible at any time and take effect after payment.
- Disks are not shrunk. This is a technical limitation: there is a risk of file system corruption.
- Removal of an additional disk takes effect at the end of the current billing period; the customer uses the period paid for to its end.
- The archive disk cannot be converted to an NVMe disk; a separate NVMe disk is added instead. Archive and NVMe capacity limits are counted separately.
- A reduction in mail seats takes effect immediately within 48 hours of purchase, and thereafter from the next period (Terms §7.4).
- A change of billing period (monthly ↔ annual) takes effect from the next invoice; a period already paid for is not affected.
- Static IP addresses and port forwarding rules are managed through the panel; the standard limit is 50 rules per server. Need more? Contact support. We will review your needs and raise the limit.
- We may change a static address (where technically necessary) with at least 14 days' notice (Terms §6.2); this does not create a compensation basis.
8. Payment, suspension and cancellation
The periods are set out in Terms of Service §5; this is a short summary.
| Event | Cloud server, static IP | Email hosting |
|---|---|---|
| Invoice issued | the 1st of the month | the same |
| Payment term | 7 days from the invoice date | the same |
| Suspension for non-payment | after the payment term ends | access is blocked, receiving continues |
| Full freeze for non-payment | - | 30 days after the start of the period |
| Termination for non-payment | 14 days after the payment term ends | 60 days after the start of the period |
- Data of a suspended service is retained until termination.
- The customer may cancel at any time: cancel at end of period (no money movement) or cancel immediately, only within 48 hours of ordering (the hours used are retained, a started hour counts as whole, the remainder is credited to the account balance). After 48 hours the customer may cancel only at the end of the period and is not entitled to demand a refund for the paid period. If the current period has not been paid, immediate cancellation cancels the invoice and no debt is charged. The rule is the same for monthly and annual periods and for email hosting (Terms §5.1).
- After cancellation the server is kept powered off for 7 days: no charge is made during that time and restoration is possible. Then the VM, its disks and its backups are deleted (no later than 35 days). When the email service is cancelled, the mailboxes are deleted (Terms §5.2).
- When the last cloud server on the account is cancelled, the included static IP is reclaimed immediately (Terms §6.2).
- The customer may request the return of the balance to a bank account only on the first purchase, within 48 hours of the first payment; after that the balance is spent on services; the conditions are in Terms §5.3 (minimum 5 AZN, 10 business days). If the provider cancels a service on its own initiative (without a breach by the customer), the remainder of that service is returned to the bank account; on cancellation for a breach by the customer, the customer is not entitled to demand a refund.
- An open invoice is not paid from the balance automatically: the customer pays it; on the last day of the payment period, if a renewal invoice is open and the balance covers it in full, the amount is deducted automatically (Terms §3).
- Important: Where a bank refund is requested, the retention periods do not apply: the server, all backups and the mailboxes are deleted immediately and irreversibly (Terms §5.3.1).
9. Customer obligations
- making payments on time
- security of the system inside the VM: updates, passwords, firewall
- an independent copy of their own critical data: especially on the archive disk (§6.1)
- correct configuration of the mail domain's DNS records (MX, SPF, DKIM, DMARC)
- not using the service for unlawful purposes or purposes harmful to the network (details are in the "Terms of Service" §8)
- keeping contact details current: planned works and critical notifications are sent to that address
10. Limitation of liability
The provider's liability is limited to the balance compensation set out in this document and does not exceed the cap in Terms of Service §13 (the amount paid for that service in the last 3 months). Indirect loss (lost revenue, business interruption, third-party claims, loss arising from data loss) is not covered.
11. Changes to this document
This document may be updated. Changes that reduce commitments are notified by email at least 30 days in advance; if the customer does not agree, they may cancel the service at the end of the period within that time. When the document is updated, the "Last updated" date changes.
12. Contact
- Support: the ticket system inside the portal, [email protected]
- Payments and invoices: [email protected]
- Abuse complaints: [email protected]
- Provider: JEZA CLOUD LLC · TIN 1606154731
- Registered address: Bakı şəh., Nizami ray., Q.Qarayev pr. ev.84, AZ1096