Limits
How many resources an account can have, and how to get more.
Every organization has limits on the number of resources it can have. They protect the platform against abuse and runaway scripts. New organizations start with these limits:
| Resource | Default limit |
|---|---|
| Servers | 5 |
| Volumes | 10 |
| Volume storage, all volumes together | 2,000 GB |
| Floating IPs | 5 |
| Load balancers | 2 |
| Snapshots | 10 |
| Snapshot storage, all snapshots together | 1,000 GB |
| Projects | 10 |
| API tokens | 50 |
| Private networks | 10 |
| Firewalls | 20 |
| Placement groups | 10 |
| SSH keys | 50 |
Limits count everything in the organization, across all its projects. The console shows your current limits and use under Billing.
When a limit is reached, creating another resource of that kind fails with 403 limit_exceeded. The error details say
which limit (resource, e.g. servers) and its value (limit):
{
"error": {
"code": "limit_exceeded",
"message": "Your account can have up to 5 servers. Open a support ticket to raise the limit.",
"details": { "resource": "servers", "limit": 5, "used": 5, "requested": 1 }
}
}The storage limits (volumes_gb, snapshots_gb) count gigabytes: creating or growing a volume needs its new size to
fit, and taking a snapshot reserves the server's disk size until the snapshot's real size is known. For them, used
and requested are in GB.
To raise a limit, open a support ticket in the console with the category Limit increase and tell us what you need and what for.
Other limits that apply to single resources:
| What | Limit |
|---|---|
| Labels per resource | 64 |
| Rules per firewall | 50 |
| Firewalls per server at creation | 5 |
| Volume size | 10 GB to 10,240 GB |
| Private network size | /16 to /28 |
| Snapshots in progress per organization | 2 |
| Cloud-init user data | 32 KiB |
| Services and targets per load balancer | Set by the load balancer type |