Limits and quotas

This page lists every limit you may run into while using Arianet. Some limits are set per account, so they can differ between accounts. For those, this page gives no number; check your own account's current value on the page named instead.

Account resource quotas

Arianet Cloud

Each account has a limit in every datacenter for: servers, vCPUs, memory (GB), disk space (server disks and volumes together), volumes, floating and elastic IPs, private networks, routers, load balancers and snapshots.

• Where to see them: in the cloud panel, "Compute → Limits" shows each limit and your current usage in every datacenter (cloud panel guide). In the API: GET https://api.ariaservice.net/cloud/v1/limits (add ?datacenter= for one datacenter).
• When you exceed one: the create is refused with 422 and code quota_exceeded. The reason field names the resource that is full.
• Raising a limit: support sets limits per account. If one is too low, open a ticket.

Other products (VPS and its resources)

Resources such as firewalls, volumes, snapshots, floating IPs, private networks, load balancers and SSH keys also have count limits. These start the same for every account but can be set per account or per datacenter.

• Where to see them: account menu → "Resource quota" (Resource quota).
• When you exceed one: the create is refused with 403 and a message that explains the limit.
• Raising a limit: send a "Request quota increase" from the same page; support reviews it.

tip

Before creating many resources, check your limits on the pages above so a create does not fail halfway through.

API rate limits

API	Limit
Cloud (/cloud/v1)	60 requests a minute and 3600 an hour, for each account and each user acting in it
VPS (/api/v1)	about 120 reads a minute, about 20 writes a minute, about 5 server creates an hour per token (details)
Regional VPS, hosting, dedicated servers, SMS	per caller; the current values are in the RateLimit-* headers of every response

On top of the general limit, some heavy operations have their own per-server limit:

• Regional VPS: reinstall, resize and root password reset, at most 3 a minute and 10 an hour per server.
• Dedicated servers: OS install, at most 3 an hour per server.

Past a limit the response is 429, and the Retry-After header says how many seconds to wait. Retry rules are in API conventions.

Creating and deleting servers

• Creating in bursts: to stop servers being created and deleted again and again (for example to fish for another IP), the number of servers an account can create in 24 hours is capped, and deleted servers count too. If you reach the cap, the error message says how many minutes to wait. For a filtered IP, use IP change instead of creating a new server.
• Early deletion: an hourly server deleted less than 60 minutes after it was created is charged on a rising scale (details under billing).
• Balance needed to order: an hourly server is only accepted when the wallet covers several hours of it (details).
• Identity verification: an account that has not verified its identity can order only its first server (VPS or cloud), and only one server in that order. Later orders are refused until it verifies (in the cloud with code identity_needed).
• Cloud: at most 10 servers per create request (count 1 to 10).

IP change

Changing a server's primary IP is offered only in some datacenters, and each datacenter sets its own rules:

• A number of free changes per server and a fee for each later one. The fee is charged only after a successful change.
• A maximum number of changes per server (or no maximum). Failed changes are not counted.

The rules and the changes left for a server are shown on that server's IP change page (VPS, cloud). In the cloud API, going past the maximum is refused with 422 ip_change_limit_reached. The old IP never comes back to the server.

Cloud technical limits

These are the same for every account:

Item	Limit
User data (cloud-init)	32 KB
Labels	32 per server, network or load balancer; keys and values up to 63 characters each
Resource names	letters, digits, dots and dashes; up to 63 characters
Volume size	10 to 10240 GB; can only grow
Volumes attached at server create	16
Rules per firewall	50
JSON request body	64 KB
Pagination	per_page up to 100 (default 25)

Load balancer capacity depends on its type:

Type	Services (listeners)	Targets	Concurrent connections
lb11	5	25	10,000
lb21	15	75	20,000
lb31	30	150	40,000

Going past these is refused with 422 and a code such as too_many_labels, too_many_rules, too_many_targets or user_data_too_large. The full list of codes is in the cloud API reference.

Other limits

Item	Limit
SMS	up to 100 recipients and a text of up to 2000 characters per send request (SMS API)
Ticket attachments	up to 5 files, each up to 20 MB (zip, rar, jpg, png, pdf)
VPS pagination (/api/v1)	limit up to 100 (default 15)
SMS pagination	per_page up to 200