You can query bucket information on the Overview page of the bucket, including basic information, storage usage, access traffic, and endpoints.
Basic information
The Basic information section shows the bucket's creation date and the status of features such as versioning and direct reads for Archive objects.
Usage
In the Usage section, you can view the bucket's storage usage, traffic and requests for the current month, number of objects, and number of parts.
The data in the Usage section is not updated in real time. A latency of 1 to 2 hours exists. All data is provided for reference only and is not used to calculate fees.

The following table describes each metric.
-
Storage Usage: Shows the total amount of data stored in the bucket. You can view the total usage (excluding ECS snapshots) or the usage for each individual storage class.
Storage usage
Description
Total (Excluding ECS Snapshots)
The storage usage of objects in different storage classes in the bucket, excluding Elastic Compute Service (ECS) snapshots.
Storage Usage of Standard LRS Objects/Storage Usage of Standard ZRS Objects
The storage used by objects in the Standard storage class. The label is Storage Usage of Standard LRS Objects for locally redundant storage or Storage Usage of Standard ZRS Objects for zone-redundant storage, depending on the bucket's redundancy type. For more information, see Storage classes.
Storage Usage of IA LRS Objects/Storage Usage of IA ZRS Objects
The storage usage of Infrequent Access (IA) objects in the bucket. Whether the IA (LRS) or IA (ZRS) storage usage is displayed depends on the storage redundancy type of the bucket.
-
Actual Storage Usage: The actual storage size of objects in the IA storage class.
-
Billed Storage Usage: The billed storage size for objects in the IA storage class. The minimum billable unit for an IA object is 64 KB. Objects smaller than 64 KB are billed as 64 KB. Therefore, the billed size may be higher than the actual size if the bucket contains many small objects. For more information, see Storage classes.
Archive(Locally Redundant Storage)/Archive (ZRS)
The storage usage of Archive objects in the bucket. Whether the Archive (LRS) or Archive (ZRS) storage usage is displayed depends on the storage redundancy type of the bucket.
-
Actual Storage Usage: The actual storage size of objects in the Archive storage class.
-
Billed Storage Usage: The billed storage size for objects in the Archive storage class. The minimum billable unit for an Archive object is 64 KB. Objects smaller than 64 KB are billed as 64 KB. Therefore, the billed size may be higher than the actual size if the bucket contains many small objects. For more information, see Storage classes.
Cold Archive
The storage usage of Cold Archive objects in the bucket.
-
Actual Storage Usage: The actual storage size of objects in the Cold Archive storage class.
-
Billed Storage Usage: The billed storage size for objects in the Cold Archive storage class. The minimum billable unit for a Cold Archive object is 64 KB. Objects smaller than 64 KB are billed as 64 KB. Therefore, the billed size may be higher than the actual size if the bucket contains many small objects. For more information, see Storage classes.
Deep Cold Archive
The storage usage of Deep Cold Archive objects in the bucket.
-
Actual Storage Usage: The actual storage size of objects in the Deep Cold Archive storage class.
-
Billed Storage Usage: The billed storage size for objects in the Deep Cold Archive storage class. The minimum billable unit for a Deep Cold Archive object is 64 KB. Objects smaller than 64 KB are billed as 64 KB. Therefore, the billed size may be higher than the actual size if the bucket contains many small objects. For more information, see Storage classes.
-
-
Traffic of Current Month: Total data transferred for the bucket this month.
-
Outbound Traffic over the Internet: Traffic generated when you browse or download data from OSS to a destination over the internet.
-
Inbound traffic over the internet: Traffic generated when you upload data from a source to OSS over the internet.
-
CDN back-to-origin traffic: Back-to-origin traffic generated when a Content Delivery Network (CDN) retrieves data from OSS.
-
-
Requests This Month: Total API requests made to the bucket this month.
-
Read requests: All Get-like requests. For more information, see Read requests.
-
Write requests: All Put-like requests. For more information, see Write requests.
-
-
Objects: The total number of objects stored in the bucket.
-
Parts: The total number of parts from incomplete multipart uploads in the bucket. Multipart and resumable uploads generate parts. To avoid unnecessary storage costs, use a lifecycle rule to delete unneeded parts. For more information, see Configure lifecycle rules.
Endpoints and domain names
This section lists the endpoint and bucket domain name for the bucket.
-
Endpoint: The service entry point for OSS in a specific region. You typically use an endpoint when you configure an SDK or a tool to access OSS. For more information, see Regions and endpoints.
-
Bucket Domain Name: The domain name that you can use to directly access the bucket. It follows the format
BucketName.Endpoint, whereBucketNameis your bucket's name andendpointis the endpoint for the bucket's region. For more information, see Access OSS over IPv6.

Endpoints and bucket domain names are categorized as follows:
Category |
Endpoint |
Bucket domain |
|
Access Over Internet |
An endpoint for accessing OSS over the internet. |
The domain name that is used to access the bucket over the Internet. |
|
Access from ECS over the Classic Network (internal network) |
An endpoint that is used to access OSS from an ECS instance over the classic network. The ECS instance and the bucket must be in the same region. This type of access incurs no data transfer fees. |
The bucket domain name that is used to access the bucket over the classic network from an ECS instance in the same region. This type of access does not incur traffic fees. |
|
Access from ECS over the VPC (internal network) |
An endpoint that is used to access OSS from an ECS instance over a VPC. The ECS instance and the bucket must be in the same region. This type of access incurs no data transfer fees. |
The bucket domain name that is used to access the bucket over a VPC from an ECS instance in the same region. This type of access does not incur traffic fees. |
|
Transfer Acceleration-based Access |
The acceleration endpoint. Before you use this acceleration endpoint, you must enable transfer acceleration for the bucket. For more information, see Access OSS using transfer acceleration. |
The OSS-accelerated domain name of the bucket. To have an OSS-accelerated domain name of the bucket, you must first enable transfer acceleration for the bucket. |
OSS-HDFS | The endpoint that is used by OSS-HDFS to access OSS. Before you can use this endpoint, you must enable OSS-HDFS. For more information, see Enable OSS-HDFS. | The OSS-HDFS domain name that is used to access a bucket. To have a bucket domain name of this type, you must first enable OSS-HDFS for the bucket. For more information, see Enable OSS-HDFS. |