Region Capacity Exhausted

region-capacity-exhausted · 503

The region's hosts can't fit what the change asks for, so the API created or grew nothing.

unit names what ran out: ram-gb, vcpu or disk-gb for services, ssd-pool-gb for buckets. totalValue is what the region has, reserved what is taken and projected what the change would need. The account and its plan are fine: the platform has no machine for it right now.

Besides the members every error carries, this type adds regionSlug, unit, totalValue, reserved and projected.

Common causes

  • A new service, or a first deploy, didn't fit.
  • A service resized to a bigger size didn't fit.
  • A new bucket, or more room for one, didn't fit the region's store.

How to fix the call

  • Choose a smaller size, or put something in the same region to sleep, then retry.
  • Or place it in another region, if the user agrees: where it runs is their decision.
  • Retrying unchanged later can work too, once room frees up in the region.

Example response

json
{
  "type": "region-capacity-exhausted",
  "title": "Region Capacity Exhausted",
  "detail": "Region 'amman-1' has 64 GB of RAM and 62 is already reserved; this change would need 66. Choose a smaller size, put something to sleep, or place this in another region.",
  "regionSlug": "amman-1",
  "unit": "ram-gb",
  "totalValue": 64,
  "reserved": 62,
  "projected": 66,
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "method": "POST",
  "instance": "POST /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "status": 503,
  "docs": "https://ghaym.me/docs/errors/region-capacity-exhausted"
}