What we commit to on uptime and support
In short
For eligible enterprise subscriptions, we use commercially reasonable efforts to keep the production platform available at least 99.9% of each month. If we fall short, you can claim a credit against your fees. This page also sets out how quickly we first respond when you report a problem.
This summary helps you find your way. The full text below is what applies.
Section 1. Who this agreement covers
This Service Level Agreement (“SLA”) sets out uptime and support response commitments for the production-hosted parts of the Fastclinic enterprise platform (“Production Services”), provided by Fastclinic Limited to customers who have bought an eligible subscription tier named in an applicable Order. If your Order sets different metrics or credits, the Order controls for those items only.
This SLA does not create obligations for on-premises deployments, beta or preview features, third-party integrations or professional services, unless expressly stated in writing.
Section 2. Words with a set meaning
- Downtime
- The total minutes in a calendar month during which the core Production Services are unavailable for authenticated API or web application access, not counting Excluded Minutes (defined in section 8).
- Monthly Uptime Percentage
- The total minutes in the month minus Downtime, divided by the total minutes in the month, multiplied by 100%.
- Incident
- An unplanned degradation or outage affecting the Production Services.
- Business Hours
- 09:00 to 18:00 West Africa Time (WAT), Monday to Friday, excluding Nigerian public holidays, unless your Order sets out extended coverage.
Section 3. Our uptime commitment
We will use commercially reasonable efforts to keep the Monthly Uptime Percentage for the Production Services at 99.9% or higher, measured per region or deployment instance as described in your technical appendix, if you have one.
A Monthly Uptime Percentage of 99.9% allows about forty-three (43) minutes of Downtime in a thirty-day month before a service credit may apply under section 6, subject to the exclusions.
Section 4. How uptime is measured
We measure uptime with our internal monitoring systems from several external vantage points, and with simulated health checks against documented API and application endpoints. We add the results up monthly. If you dispute a measurement, you can open a ticket within fifteen (15) days of the end of the month, with the relevant logs. We will review it in good faith and give you a written explanation.
Partial degradation (for example, slower responses, or problems in a module that is not core) may be treated as a support matter under the severity levels rather than as Downtime, unless it prevents material use of the subscribed core workflow as defined in your Order.
Section 5. How quickly we first respond
Once you open a support ticket through the designated channel and give us the diagnostic information we ask for, these are the initial response times we work to during Business Hours:
| Severity | When it applies | First response |
|---|---|---|
| Severity 1, critical | The Production Services are wholly unavailable, or data integrity is at imminent risk, for multiple users. | One (1) hour |
| Severity 2, major | Material degradation of core features affecting a substantial portion of users. | Four (4) hours |
| Severity 3, minor | Limited impact, with a workaround available. | One (1) business day |
| Severity 4, general | Questions, feature requests or cosmetic issues. | Two (2) business days |
How long a resolution takes depends on the root cause and on your cooperation. The table covers the first meaningful response only. Premium support tiers may include 24/7 coverage and shorter response times, as stated in the Order.
Section 6. Service credits when we fall short
If the Monthly Uptime Percentage falls below 99.9%, you may request a credit of part of the monthly subscription fees for the affected Production Services for that month:
| Monthly Uptime Percentage | Credit |
|---|---|
| Below 99.9% but at least 99.0% | 10% of those fees |
| Below 99.0% | 25% of those fees |
Credits are applied to future invoices, or refunded if no future invoice is due within ninety (90) days. They exclude taxes. Subject to the limitations in your master agreement, they are your sole and exclusive remedy for SLA failures. Credits are not cash equivalents, except as stated in this SLA.
To claim a credit, send a written request within thirty (30) days after the end of the month in which the Downtime happened, with your account identifier and incident ticket references. Credits cannot be combined with credits for the same period under duplicate provisions.
Section 7. Scheduled maintenance
We may carry out scheduled maintenance that temporarily affects availability. Where practicable, we schedule it during low-traffic windows (usually Sundays, 02:00 to 06:00 WAT) and give at least forty-eight (48) hours’ notice of any impact we expect you to see, except for emergency security maintenance.
Scheduled maintenance minutes that we announce in advance, and emergency security patches, are excluded from Downtime calculations.
Section 8. What does not count as Downtime
Excluded Minutes, which are not counted as Downtime, include without limitation:
- scheduled maintenance and emergency maintenance, as described in section 7
- problems caused by your networks, devices, DNS, third-party identity providers or misconfiguration
- suspension for non-payment, breach or a legal requirement
- force majeure events, including internet-wide failures, strikes or government action
- beta, preview or optional modules that your Order does not name as covered by the production SLA
- dependence on third-party cloud regions or services outside our reasonable control, except where we have committed in writing to specific redundancy
- brief errors affecting a single user session, or edge cases below the de minimis thresholds published in our status page methodology.
Section 9. If you think we have the priority wrong
If you believe an Incident has not been prioritised correctly, you can escalate it through your named customer success contact, or by emailing contact@getfastclinic.com with the subject line “SLA Escalation”, including ticket numbers and the impact on your business. We will assign a manager to review it within one (1) business day.
Section 10. Which document wins
This SLA forms part of the agreement between the parties. If your Order, data processing agreement or enterprise framework agreement conflicts with this SLA, the conflicting provision in the signed enterprise document prevails. Fastclinic Limited is incorporated in Nigeria under CAMA 2020, and contractual interpretation stays governed by the governing law clause in your Terms unless agreed otherwise.