> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/admins/pricing/platform-sla.md).

# Platform SLA

## SLA

| Production Availability | <p>99.95%</p><p>= 43s of allowed downtime/unavailability daily</p> |
| ----------------------- | ------------------------------------------------------------------ |

Morpheus Platform status is availalble at <https://status.msquared.io/>.

Note - this SLA excludes cloud streaming services (e.g. Nvidia Geforce Now).

## Service Credits

| Monthly Uptime Percentage                                                                                  | 99.00% to < 99.95% | 95.00% to < 99.00% | < 95.00% |
| ---------------------------------------------------------------------------------------------------------- | ------------------ | ------------------ | -------- |
| Percentage of monthly bill that does not meet SLA that will be credited to Customer’s future monthly bills | 10%                | 25%                | 50%      |

Note: In order to receive the Financial Credits described above, Customer must notify Morpheus Platform support within 30 days from the time Customer becomes eligible to receive a Financial Credit. Customer must also provide MSquared with log files showing Downtime Periods and the date and time they occurred.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.otherside.xyz/platform-documentation/admins/pricing/platform-sla.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.