<a id="service-quotas-overview"></a>

# Understand Service Quotas for Confluent Cloud

Organizations, environments, accounts, networks, and clusters in Confluent Cloud
can use only a maximum quantity of resources and operations. These service
quotas, or default limits, enable Confluent to
manage the availability and scalability of Confluent Cloud resources.

Service quotas are grouped by the resource scope that they apply to. Some
resource limits vary by scope.

- The default limits are usually adequate for most use cases, but if your
  requirements exceed the default limits, you can request increases for
  many of the default limits. For service quotas that have a quota code (ID)
  listed in the following tables, you can use the [Quotas API](quotas.md#cc-quotas) to get the
  current values.
- All Confluent Cloud resources enforce hard thresholds that cannot be exceeded, but many
  of the default quotas can be increased based on your changing requirements.
  To request an increase for a quota, contact
  [Confluent Support](https://support.confluent.io).
- Client quotas define throughput limits for specific [principals](../_glossary.md#term-principal)
  on Dedicated clusters. For more information about client quotas,
  see [Multi-Tenancy and Client Quotas on Confluent Cloud](../clusters/client-quotas.md#client-quotas).

## Service quota notifications

You can manage notifications for service quota events with the Confluent Cloud Console
or the REST API. For more information, see [Notifications for Confluent Cloud](../monitoring/configure-notifications.md#ccloud-notifications).

#### NOTE
The quota notification system sends a single notification when you first exceed
the thresholds of your quota limit (50%, 90%, and 100%). For example, if your
organization has a limit of 3,000 Cloud API keys, you receive one notification
after you create your 1,501st Cloud API key, another notification when you create your
2,700th Cloud API key, and a notification when you reach the quota limit.

Confluent Cloud service quota notification thresholds are as follows:

|   Usage (% quota) | Notification level   |
|-------------------|----------------------|
|                50 | Information          |
|                90 | Warning              |
|               100 | Critical             |

When notifications are enabled for a given notification level, you get
notifications for each quota that exceeds the relevant notification threshold
(50%, 90%, or 100% usage).

- Only quotas with available usage data are eligible for notifications.
- Notifications are sent only for exceeding a notification threshold, not for
  dipping beneath a threshold.
- Usage data is returned only if usage is non-zero. To see if a service
  quota generates usage data that can be used for notifications, review the
  **Usage data** column in the tables in [Service Quotas for Confluent Cloud](service-quotas.md#service-quotas).

## Related content

- [Quotas API](quotas.md#cc-quotas)
- [View Service Quotas Using Confluent CLI on Confluent Cloud](use-cli.md#list-quotas-with-cli)
- [Service Quotas for Confluent Cloud](service-quotas.md#service-quotas)