> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/service-levels.md).

# Service levels

The core UbiQuity platform is monitored 24/7 for outages and targets 99.9% uptime, outside of scheduled maintenance windows.

UbiQuity operates in a shared tenancy environment, where resources are shared across multiple clients. A priority system ensures fair and efficient use of these resources. Incidents are prioritised as follows:

***

### SLA Targets <a href="#sla-targets" id="sla-targets"></a>

| **Priority** | **Name** | **Resolution Target** |
| ------------ | -------- | --------------------- |
| P1           | Critical | 4 business hours      |
| P2           | High     | 8 business hours      |
| P3           | Medium   | 5 business days       |
| P4           | Low      | By agreement          |

Resolution targets are measured during business hours (9am–5pm, Monday–Friday).

***

### P1 - Critical

Issues causing complete service disruption for all clients, leading to full system outages or data breaches. Immediate attention is required as the situation impacts access to, or critical functionality of, the UbiQuity platform.

*Examples: The platform is down for all users, database connection is lost, significant security threat.*

***

### P2 - High

Significant functionality is impacted, or significant performance degradation is experienced, however the platform and database are still accessible or workarounds are available. The issue affects a large portion of clients and requires quick resolution to prevent escalation.

*Examples: API calls are failing for all clients using this functionality, all scheduled emails are not rendering or sending, all external-facing forms displaying an error message.*

***

### P3 - Medium

A non-critical issue impacting individual clients or specific features, without completely halting operations. It may affect productivity but does not require immediate action.

*Examples: Slow loading times for a report function, reduced email sending rate, caching issues.*

***

### P4 - Low

Minor bugs that do not affect daily operations. These will be added to the backlog for resolution in future releases or maintenance windows.

*Examples: Cosmetic issues or improved user experience for existing functionality.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ubiquity.co.nz/service-levels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.