Browse articles

Object storage

# "quota check temporarily unavailable" on a new bucket

A new bucket needs up to about 2 minutes until the quota scanner is ready. While it shows preparing, uploads are temporarily rejected with this message.

2 min readUpdated: October 23, 2026[Baca dalam Bahasa Indonesia](/help/kuota-belum-siap)

The message `quota check temporarily unavailable` appears when you upload to a bucket that was just created.

## Why it happens

This message only appears on buckets that have a quota limit (hard quota); buckets without a limit are ready immediately. After a bucket with a quota is created, the usage scanner needs up to about 2 minutes before the quota can be read. During that time the system cannot yet confirm that the upload stays under the quota, so uploads are temporarily rejected.

## What to do

1.  Open the bucket page in the dashboard. During this process the bucket status reads **preparing** and the page refreshes automatically.
2.  Wait until the status changes to **ready**.
3.  Retry the upload. Many S3 clients, such as the AWS CLI and rclone, retry automatically.

For automation scripts that create a bucket and upload right away, add a delay or retry logic for a few minutes after the bucket is created.

## Not a quota problem

This message does not mean that your bucket or account quota is used up, and it is unrelated to your access key. As soon as the bucket is ready, the quota you set at creation applies and uploads are accepted while they stay under it. If uploads are rejected after the status reads **ready**, see [Bucket quota full](/help/kuota-penuh).

## If it never becomes ready

If the status still reads **preparing** after more than 10 minutes, open a support ticket and include the bucket name exactly as shown in the dashboard.

## See also

-   [Creating and managing buckets](/docs/bucket)

Still need help?

Open a support ticket from the dashboard and our team will reply as soon as possible.

[Browse the docs](/en/docs)[Open a ticket](/app/support/new)