Availability SLA (verson 2024.6)
- Introduction
- This Schedule sets out the Provider’s availability commitments relating to the Hosted Services.
- In this Schedule, “uptime” means the percentage of time during a given period when the Hosted Services are available at the gateway between public internet and the network of the hosting services provider for the Hosted Services.
- Definitions of all terms come from the EULA
- Availability
- The Provider shall use reasonable endeavours to ensure that the uptime for the Hosted Services is at least 99% during each calendar month.
- The Provider shall be responsible for measuring uptime, and shall do so using any reasonable methodology.
- The Provider shall report uptime measurements to the Customer on its status website, in respect of each calendar month.
- Service credits
- In respect of each calendar month during which the Hosted Services uptime is less than the commitment specified in Paragraph 2.1, the Customer shall be entitled to earn service credits in accordance with the provisions of this Part 3.
- The service credits earned by the Customer shall be as follows: 5% credit of user subscription charges for each day the uptime level falls below the commitment specified in Paragraph 2.1.
- Upon request by the Customer, the Provider shall deduct an amount equal to the service credits due to the Customer under this Part 3 from amounts invoiced in respect of the Charges for the Hosted Services. All remaining service credits shall be deducted from each invoice issued following the reporting of the relevant failure to meet the uptime commitment, until such time as the service credits are exhausted.
- Service credits shall be the sole remedy of the Customer in relation to any failure by the Provider to meet the uptime guarantee in Paragraph 2.1, except where the failure amounts to a material breach of the Agreement.
- Upon the termination of the Agreement, the Customer’s entitlement to service credits shall immediately cease, save that service credits earned by the Customer shall be offset against any amounts invoiced by the Provider in respect of Hosted Services following such termination.
- Exceptions
- Downtime caused directly or indirectly by any of the following shall not be considered when calculating whether the Provider has met the uptime guarantee given in Paragraph 2.1:
- a Force Majeure Event;
- a fault or failure of the internet or any public telecommunications network; or
- a fault or failure of the Provider’s hosting infrastructure services providers, unless such fault or failure constitutes an actionable breach of the contract between the Provider and that company; or
- a fault or failure of the Customer’s computer systems or networks; or
- any breach by the Customer of the Agreement; or
- scheduled maintenance carried out in accordance with the Agreement; or
- a misconfiguration made by the Customer which results in service failure.
- Downtime caused directly or indirectly by any of the following shall not be considered when calculating whether the Provider has met the uptime guarantee given in Paragraph 2.1:
Maintenance SLA (version 2024.6)
- Introduction
- This Schedule sets out the service levels applicable to the Maintenance Services.
- Definitions of all terms come from the EULA
- Scheduled Maintenance Services
- The Provider shall where practicable give to the Customer at least 10 Business Days’ prior written notice on our Status Page of scheduled Maintenance Services that are likely to affect the availability of the Hosted Services or are likely to have a material negative impact upon the Hosted Services, without prejudice to the Provider’s other notice obligations under this Schedule.
- The Provider shall provide all scheduled Maintenance Services between 22:00 and 05:00 Monday to Friday.
- The Provider shall apply security updates as soon as practically possible without interruption to service. In the event of a critical security update being required which may result in interruption to service, this may require less than the standard notice period to maintain the integrity and security of the platform.
- The Provider shall apply Updates to the Platform as follows:
- third party security Updates shall be applied to the Platform promptly following release by the relevant third party, providing that the Provider may acting reasonably decide not to apply any particular third party security Update;
- the Provider’s security Updates shall be applied to the Platform promptly following the identification of the relevant security risk and the completion of the testing of the relevant Update; and
- other Updates shall be applied to the Platform in accordance with any timetable notified by the Provider to the Customer or agreed by the parties from time to time.
Support SLA (version 2024.6)
- Introduction
- This Schedule sets out the service levels applicable to the Support Services;
- Definitions of all terms come from the EULA unless with the exception of
- Support Hours means from 05:00 UTC to 22:00 UTC Monday to Friday excluding any day which is a public holiday in the Republic of South Africa.
- Helpdesk
- The Provider shall make available to the Customer a helpdesk in accordance with the provisions of this Schedule.
- The Customer may use the helpdesk for the purposes of requesting and, where applicable, receiving the Support Services; and the Customer must not use the helpdesk for any other purpose.
- The Provider shall ensure that the helpdesk is accessible by telephone, email and using the Provider’s web-based ticketing system.
- The Provider shall ensure that the helpdesk is operational and adequately staffed during Support Hours during the Term.
- The Customer shall ensure that all requests for Support Services that it may make from time to time shall be made through the helpdesk.
- The Customer may raise critical issues outside of the Support Hours by contacting The Provider by the published support telephone number and explaining to the operator that it is a Critical issue. The Customer understands that they must not raise non-critical issues outside of the Support Hours through this method.
- Response and resolution
- Issues raised through the Support Services shall be categorised as provided in Figure (1)
- The Provider shall determine, acting reasonably, into which severity category an issue falls.
- The Provider shall use all reasonable endeavours to respond to requests for Support Services promptly, and in any case in accordance with the targets provided in Figure (1)
- The Provider shall ensure that its response to a request for Support Services shall include the following information (to the extent such information is relevant to the request): an acknowledgement of receipt of the request, where practicable an initial diagnosis in relation to any reported error, and an anticipated timetable for action in relation to the request.
- The Provider will respond to Critical issues 24 hours per day, 7 days per week.
- The Provider shall use all reasonable endeavours to resolve issues raised through the Support Services promptly, and in any case in accordance with the time periods provided in Figure (1)
- The Provider will escalate issues internally as per Figure (2).
- Provision of Support Services
- The Support Services shall be provided remotely, save to the extent that the parties agree otherwise in writing.
- Limitations on Support Services
- If the total hours spent by the personnel of the Provider performing the Support Services during any calendar month exceed 8 hours then:
- the Provider will cease to have an obligation to provide Support Services to the Customer during the remainder of that period; and
- the Provider may agree to provide Support Services to the Customer during the remainder of that period, but the provision of those Support Services will be subject to additional Charges.
- The Provider shall have no obligation to provide Support Services in respect of any issue caused by:
- the improper use of the Hosted Services by the Customer; or
- any alteration to the Hosted Services made without the prior consent of the Provider.
- Feature Requests and Configuration Requests are not covered by the SLA and are completed as time permits. The Provider shall have no obligation to accept Feature Requests.
- If the total hours spent by the personnel of the Provider performing the Support Services during any calendar month exceed 8 hours then:
Figure 1 – Severity Matrix
Severity | Description | Initial Response Target | Resolution Target |
---|---|---|---|
Critical | The Hosted Services are inoperable or a core function of the Hosted Services is unavailable. | 15 min (24×7) | 1 hour |
Serious | A core function of the Hosted Services is significantly impaired. | 30 min | 4 hours |
Moderate | A core function of the Hosted Services is impaired, where the impairment does not constitute a serious issue or a non-core function of the Hosted Services is significantly impaired. | 30 min | 4 days |
Minor | Any impairment of the Hosted Services not falling into the above categories; and any cosmetic issue affecting the Hosted Services | 30 min | 10 days |
Configuration Request | A request to reconfigure an aspect of your system on your behalf. | n/a | Not covered by SLA |
Feature Request | A request to adjust functionality or add functionality to platform that isn’t currently possible. | n/a | Not covered by SLA |
All times in Support Hours
Figure 2 – Escalation Matrix
All time periods are measured in Business Hours
Severity | Escalated to 2nd Tier | Escalated to 3rd Tier | Management Notified |
---|---|---|---|
Critical | – | Immediately | Immediately |
Serious | Immediately | 1 hour | 2 hours |
Moderate | 2 hours | 4 hours | 8 hours |
Minor | As required | As required | – |
Configuration Request | As required | As required | – |
Feature Request | – | – | – |