> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6.12-hosted-service-guide/hosted-service/support-and-maintenance/get-notifications-about-hosted-instance-availability.md).

# Get Notifications About Hosted Instance Availability

Cortex XSOAR targets a 99.9% service availability which equals unplanned downtime of up to 43.83 minutes per month or up to 8.77 hours per year. The current availability status, notifications, and scheduled maintenance can be viewed at <https://status.paloaltonetworks.com>.

{% hint style="info" %}

### Note

If the [service limits](/cortex-xsoar-6.12-hosted-service-guide/hosted-service/service-limits.md) for incident ingestion or monthly partition data are exceeded, Palo Alto Networks cannot guarantee the SLA.
{% endhint %}

The Cortex XSOAR hosted service operates under the [Palo Alto Networks business continuity policy (BCP) (PDF)](https://www.paloaltonetworks.com/content/dam/pan/en_US/assets/pdf/datasheets/support/cortex-service-level-agreement.pdf), defined as 4HR/4HR RPO/RTO.

Customers are notified prior to planned maintenance or expected outages and are updated when the maintenance is complete. You can also opt in to [Get Notifications About Hosted Instance Availability](/cortex-xsoar-6.12-hosted-service-guide/hosted-service/support-and-maintenance.md#UUID-26a17b29-3bef-8f82-d184-12f6750b72de_idfe5a979c-ecd7-48d3-8b76-7f9f7e285603) via email.

Under the Standard plan, technical support is available via the Customer Support Portal. With the Premium plan, technical support is also available by phone 24 hours per day, 7 days per week.

For server outages on the production environment, customers should open a request via a support ticket.

| Severity | Description                                                                                                                                                                                                                       | Standard   | Premium   |
| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | --------- |
| 1        | Service is down, critically affects Customer production environment. No workaround available yet.                                                                                                                                 | ≤ 2 hours  | ≤ 1 hour  |
| 2        | Service is impaired, Customer production up, but impacted. No workaround available yet.                                                                                                                                           | ≤ 4 hours  | ≤ 2 hours |
| 3        | A Service function has failed, Customer production not affected. Support is aware of the issue and a workaround is available.                                                                                                     | ≤ 12 hours | ≤ 4hours  |
| 4        | Non-critical issue. Does not impact Customer business. Server configurations, information, documentation, and how-to requests from Customer. Requests for new features and enhancements should be submitted through the Aha site. | ≤ 48 hours | ≤ 8 hours |

Critical server patches and critical operating system updates are applied when available. Non-critical server patches and operating system updates, defined as those that don’t affect production instances, are applied when software is upgraded.

Non-critical Cortex XSOAR application upgrades are installed on an on-demand basis. Customers submit support tickets to request application upgrades. Separate requests are required to upgrade the development and production environments. Customers must provide at least 24 hours advance notice prior to the upgrade date. Non-critical upgrades are performed Monday - Thursday.

Application upgrades and other support requests may require planned system downtime, coordinated with the customer.

#### Get Notifications About Hosted Instance Availability

Opt in to the notification service to get email alerts about hosted instance availability, which includes alerts about unexpected downtime and then follow-up alerts when the service is back up.

1. Log in to your Cortex XSOAR instance and go to Settings → ABOUT → **Troubleshooting**.
2. In the **Server Configuration** section click **Add Server Configuration**.
3. Enter the following key and value:

   | Key                          | Value                                                                     |
   | ---------------------------- | ------------------------------------------------------------------------- |
   | hosted.notification.contacts | A comma-separated list of email addresses who will receive notifications. |
4. Click **Save** and verify that the new server configuration has been added by refreshing the page.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>It may take up to an hour after adding the server configuration before you begin receiving relevant email notifications.</p></div>


---

# 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, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6.12-hosted-service-guide/hosted-service/support-and-maintenance/get-notifications-about-hosted-instance-availability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
