Overview
Every tenant has quotas: ceilings on how much of each resource type it can hold. They exist per tenant, so if you operate several tenants each has its own allowance. Quotas are the most common reason a create action is refused, so knowing where you stand saves time.What’s capped
Some accounts also cap how many regions a multi-region deployment may span — attempting more explains the limit and asks you to deselect regions rather than failing obscurely.
Where to watch consumption
The dashboard is the main view. Three quota cards — Compute, Storage, and Network — show each limit asused / limit with a percentage bar, and three allocation charts plot the same figures as percentages.
The bars change colour as you approach a ceiling:
What counts toward a quota
Stopped machines still consume. A stopped VM releases nothing except the compute it was actively using — its volumes, its network, and any public IP it holds all still count. This matters because “stop the machine to free up quota” is a reasonable assumption that doesn’t hold. To recover quota you have to delete the resource.When you hit a limit
The action is refused, and the platform says which limit it hit. Your options, cheapest first:1
Reclaim what you're not using
Detached volumes, old snapshots, unassigned public IPs, and stopped machines you’ve finished with. The dashboard’s Resources card gives you the counts to compare against what you believe you’re running.
2
Check you're in the right tenant
Quotas are per tenant. A tenant that looks full may simply be the wrong one to be working in.
3
Request an increase
Quotas are set by the platform, not self-service. Ask your administrator or Simnet support to raise the specific limit.
There is no self-service quota screen. Increases are granted by a platform administrator, who manages tenant quotas and quota templates from the admin console.
Dashboard
Where quota consumption is displayed.
Organization, tenants, and projects
Why quotas belong to a tenant.