The short version
- We run every Service with care, with the redundancy described for each product, and we monitor it around the clock.
- You can check availability yourself on our public status page at https://zeeroow.com/status, sampled every minute with 90 days of history.
- We give at least 48 hours' notice of every planned maintenance, by email to affected customers and on the status page. Emergency work may happen without notice.
- Emergencies are handled 24/7. Urgent and High tickets are timed around the clock; Normal and Low tickets in general support hours, Sunday to Thursday, 09:00–18:00 Bangladesh time. Our response times are targets, not guarantees.
- This SLA has no uptime percentage and no service credits. Any goodwill credit is at our discretion.
1. About this SLA
1.1 This Service Level Agreement ("SLA") is part of our Terms of Service. It is published by Zeeroow Limited, trading as Zeeroow ("we", "us"). Words with capital letters have the meaning given in the Terms.
1.2 This SLA describes how we operate the Services, how we measure and publish availability, how we handle maintenance and incidents, and how quickly we aim to answer support requests.
1.3 This SLA does not promise any particular uptime percentage and does not give a right to service credits.
2. What we commit to
2.1 We operate the Services with reasonable skill and care, following good industry practice.
2.2 We build each product with the redundancy described for that product on its product page and order form. Where a product page does not describe redundancy, you should not assume it has any.
2.3 We monitor our platform and the Services continuously, and our staff are alerted when a check fails.
2.4 We publish the availability of our Services openly, as described in section 3, so that you can see the record for yourself.
3. How availability is measured and published
3.1 Our public status page is at https://zeeroow.com/status.
3.2 The status page lists our Services by group. Each Service is checked automatically every minute. A single brief failed check may be treated as a momentary blip rather than an outage.
3.3 For each Service, the status page shows its current state and its history for the past 90 days, together with incident reports and their timelines.
3.4 Planned maintenance is shown on the status page in advance. Time spent in announced planned maintenance is not counted as downtime.
3.5 The status page measures our Services, not your own software, data or configuration. A Service can be shown as working while your website or application on it is not, for example because of a fault in your own code.
4. Planned maintenance
4.1 We give at least 48 hours' notice of every planned maintenance that may affect your Service. We always send the notice by email to the affected Customers and publish it on the status page. We do not start non-emergency maintenance at shorter notice.
4.2 The notice says what we are doing, when, and what effect you should expect.
4.3 We try to schedule planned maintenance at times of low use.
4.4 Emergencies are exempt. We may carry out urgent work without notice to fix a security vulnerability, prevent or stop an attack, protect data, or restore a Service that has failed. We post an update on the status page as soon as we can.
5. Incident communication
5.1 When an incident affects a Service, we post it on the status page and update it as we learn more, until it is resolved.
5.2 After a significant incident, we may publish a summary of what happened and what we are doing to prevent it from happening again.
5.3 You can follow the status page through the feeds it offers.
6. Support channels and hours
6.1 You can reach support:
- through a support ticket in the Client Area at https://zeeroow.com/clientarea;
- through live chat in the Client Area, when it is staffed; or
- by email to help@zeeroow.com.
6.2 Emergencies are handled 24 hours a day, 7 days a week. An emergency is a complete outage of a Service, a security incident, or a problem that stops a production service from working. Report an emergency by opening a ticket with Urgent priority.
6.3 General support hours are Sunday to Thursday, 09:00–18:00 Bangladesh time, excluding public holidays in Bangladesh.
7. Support response targets
7.1 We aim to meet these targets:
| Priority | First reply | Resolution |
|---|---|---|
| Urgent | 1 hour | 8 hours |
| High | 4 hours | 24 hours |
| Normal | 8 hours | 3 days |
| Low | 24 hours | 7 days |
How the clock runs. Targets for Urgent and High tickets run in calendar time: 24 hours a day, 7 days a week, including weekends and public holidays. Targets for Normal and Low tickets run only during general support hours (section 6.3).
7.2 These are targets, not guarantees. Missing a target does not give a right to a refund, a credit or compensation.
7.3 "Resolution" means we have fixed the problem, given you a workaround, or explained that the cause is outside our control and what you can do. A problem that needs a third party (for example a registry or an upstream network) may take longer.
7.4 We may change the priority of a ticket to match its real urgency. Priorities are:
- Urgent: a production service is down or a security incident is under way.
- High: a Service is badly degraded, or an important function does not work.
- Normal: a problem with a workaround, a configuration question, or a billing question.
- Low: general questions, information requests and feature suggestions.
7.5 A ticket that is waiting for your reply may be closed if you do not reply within 7 days. You can reopen it or open a new one.
8. Provisioning
8.1 VPS: set up automatically within minutes of your payment clearing.
8.2 Dedicated servers and colocation: set up by arrangement. We agree the date with you after your order.
8.3 Other Services are usually set up automatically once payment clears.
8.4 Set-up may be delayed where we need to check your identity or your order, as the Terms allow. If an order cannot be set up, the Refund & Cancellation Policy applies.
9. Backups
9.1 What we back up depends on the product. We store backups in our data centre in Dhaka:
| Product | Backups by us | Kept |
|---|---|---|
| Hosting | As stated on your plan | As stated on your plan |
| VPS | As stated on your plan | As stated on your plan |
| Dedicated servers | None | Not applicable |
| Colocation | None (your own equipment) | Not applicable |
9.2 Our backups are a safety measure, not a replacement for your own. You are responsible for keeping your own copies of your data, and for all backups on dedicated servers and colocated equipment.
9.3 When a Service is terminated or ends after cancellation, the Service is deleted immediately, with no recovery window. Our backups of it are not restored and age out in their normal cycle, as the Terms explain.
10. Exclusions
This SLA does not cover problems caused by:
- your own software, content, configuration or actions, or those of your users;
- a suspension under the Terms or the Acceptable Use Policy;
- attacks against your Service, such as denial-of-service attacks, while we act to contain them;
- third parties outside our control, including domain registries and registrars, payment providers, upstream networks and public internet routing;
- your equipment in colocation, or its power draw beyond your contract;
- announced planned maintenance and emergency work under section 4; or
- events beyond our reasonable control, as the Terms describe.
11. Goodwill credits
11.1 We do not give service credits under this SLA.
11.2 We may, at our discretion, give a goodwill credit to your wallet after an incident. A goodwill credit is a one-off gesture. It does not set a precedent and does not create a right to future credits.
12. Remedies
12.1 This SLA gives no remedy beyond those in the Terms. The limitation of liability in the Terms applies.
12.2 Nothing in this SLA limits any right you have under Bangladeshi consumer law.
13. Changes to this SLA
We may change this SLA. We give at least 30 days' notice of a material change by email and in the Client Area.