This page lists every fixed limit on a server, with what happens when you reach it. The plan sets the rest, and the page that covers each feature explains how to work within it.
The plan you order sets these, and they stay with the server. The Size and add-ons card on the server's Billing tab shows them. Get a bigger server explains how to move to a larger plan.
What
Limit
Memory, Disk and CPU
Set by the plan.
Ports
Port slots, including the primary port. Most plans allow 5. Over it: Allocation limit reached (5). Cannot add more ports to this server.
Databases
Database slots. Over it: Database limit reached (3/3), with your count and the plan's limit.
2–48 characters, when you order and when you rename the server. Spaces in a row count as one. Over it: Server name must be at most 48 characters. The name can use letters and numbers in any language, spaces and - _ . ' ! & ( ) [ ] , : +, and needs at least one letter or number.
8 on one server and 32 across all servers, for each account. One more does not connect: its socket closes with code 4029, and the page shows Connection limit reached. Close other console sessions first.
Command length
1,000 characters. The console cuts a longer command at that length, and POST /command answers 422.
Commands per second
20 on one console. The console drops each command over that and shows Slow down.
We count these actions per account and per server. Each limit covers a rolling window.
Action
Most per window
Window
Power actions: start, stop, restart and kill
24
60 seconds
Software actions: changes, installs, addon updates, resource pack and Java settings changes, and Bedrock pack imports
8
10 minutes
Compressing and extracting archives
24
60 seconds
Downloads from a URL
24
60 seconds
Import tests and starts
12
5 minutes
New databases
24
60 seconds
Backup restores
8
5 minutes
A request over the limit fails, and the dashboard shows Too many requests for this action. Try again later. Through the API, the request answers 429:
JSON
{
"detail": {
"error": "rate_limited",
"message": "Too many requests for this action. Try again later.",
"action": "container.power",
"retry_after_seconds": 60
}
}
action is container.power, container.software, container.file_compress, container.file_pull, container.import, container.database or container.backup_restore. retry_after_seconds and the Retry-After header give the length of the window. A request refused this way does not count towards the limit.
Taking and restoring snapshots have no rate limit of their own. A server runs one snapshot or restore at a time instead.
Every API request also counts towards the limits for your account as a whole, which Rate limits describes.
No larger than the server's disk. A larger file is skipped.
Listing the remote folder
60 seconds for a test, 10 minutes for an import.
Length of an import
6 hours. After that: The import ran longer than 6 hours, so we stopped it.
Failed files
200. After that: Stopped after 200 files could not be copied. Links, special files and the free server's executable are skipped on purpose and do not count.
Skipped entries listed
200 in the import status, then one entry and N more entries.
Attempts after a connection problem
5. After that: The import stopped after 5 attempts. Last problem: ….
Imports at once
One per server. Across Coritan, a limit applies: an import that finds every place taken waits as Queued until one is free.
50, each up to 255 characters and 4,000 characters in all.
Snapshots or restores at once
One per server.
Time to finish
We mark a snapshot failed after an hour without progress, or longer on a server with a lot on disk, and 12 hours after it started at most. You can cancel one before then.
