> 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/service-limits.md).

# Service Limits

Cortex XSOAR Hosted Service supports BoltDB and Elasticsearch. The hosted environment consists of two servers - production and development. The development server allows you to develop and test components (such as playbooks, automation scripts, screen layouts) before they are deployed to production.

{% hint style="info" %}

### Note

Elasticsearch is available for customers with a TIM license. Elasticsearch provides six node clusters, including three for master/coordinating nodes and three for data nodes. The same cluster configuration is provided for development and production environments. Elasticsearch deployments are limited to one app server.
{% endhint %}

The Cortex XSOAR hosted service production environment supports:

|                          | BoltDB (base scale)                                                                                                                                                                           | BoltDB (higher scale)                                               | Elasticsearch                                                       |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------- |
| Incidents per day        | <p>5,000</p><p>Rate limit of 100 incidents ingested per minute</p>                                                                                                                            | <p>10,000</p><p>Rate limit of 100 incidents ingested per minute</p> | <p>10,000</p><p>Rate limit of 100 incidents ingested per minute</p> |
| Total indicators stored  | 3,000,000                                                                                                                                                                                     | 3,000,000                                                           | 100,000,000                                                         |
| Partition data per month | 20 GB                                                                                                                                                                                         |                                                                     |                                                                     |
| Data retention           | 1 TB. For the average customer, 1 TB provides one year of data retention.                                                                                                                     |                                                                     |                                                                     |
| Custom rules             | Up to 100 custom rules limiting inbound traffic to the web interface/API interface to specific CIDRs. Of the 100 CIDRS, up to 80 can be dedicated for restricting access to the API interface |                                                                     |                                                                     |

The Cortex XSOAR hosted service development environment supports:

|                          | BoltDB (base scale)                                                                                                                                                                           | BoltDB (higher scale)                                              | Elasticsearch                                                      |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------ |
| Incidents per day        | <p>1,000</p><p>Rate limit of 100 incidents ingested per minute</p>                                                                                                                            | <p>2,000</p><p>Rate limit of 100 incidents ingested per minute</p> | <p>5,000</p><p>Rate limit of 100 incidents ingested per minute</p> |
| Total indicators stored  | 500,000                                                                                                                                                                                       | 500,000                                                            | 10,000,000                                                         |
| Partition data per month | 10 GB                                                                                                                                                                                         |                                                                    |                                                                    |
| Data retention           | 1 year                                                                                                                                                                                        |                                                                    |                                                                    |
| Custom rules             | Up to 100 custom rules limiting inbound traffic to the web interface/API interface to specific CIDRs. Of the 100 CIDRS, up to 80 can be dedicated for restricting access to the API interface |                                                                    |                                                                    |

{% hint style="info" %}

### Note

The development server has different technical specifications and should not be used for a production environment or stress testing.
{% endhint %}

You can view the percentage used for incoming incidents, stored indicators, and partition data, on the **Settings** → **ABOUT** → **System Diagnostics** page. If the percentage used reaches 75% for incoming incidents, stored indicators, or partition data, an email alert is sent to all site administrators and a warning message is displayed on the System Diagnostics page. In addition to the stated service limits above, any other alerts that appear on the Cortex XSOAR version 6.5 or later System Diagnostics page must also be addressed. Repeated alerts for big incidents, enrichment data, too many containers, etc. that cannot be resolved may result in a degradation of service.&#x20;


---

# 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/service-limits.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.