
Egress fees are charges for data that leaves a storage provider's network, usually priced per gigabyte downloaded. On AIOZ Storage the documented rate is 0.005 USD per GB downloaded, and the billing docs list no bandwidth charge for uploads. Here you will see what triggers egress, how to estimate it, and what the docs leave out.
TL;DR:
Egress is outbound traffic: bytes that move from the provider's servers to a user, an application, or another cloud. An egress fee is the price a provider puts on those bytes, usually a rate per GB that is summed over a month.
Many providers treat inbound traffic differently, and Amazon's S3 pricing page lists data transferred in from the internet as free. It also gives the first 100 GB per month out to the internet as free, aggregated across AWS services and regions, and you pay by the GB past that.
Two reasons come up in provider and vendor material, and the first is cost recovery: outbound traffic uses network capacity that the provider pays for. The second is retention: free uploads and paid downloads make it expensive to move a large dataset elsewhere. A CDN vendor, Edge Network, calls egress a switching cost for exactly that reason.
Treat the second point as a competitor's view, since it describes an incentive and the providers in question do not state it as their pricing logic.
Any read that sends bytes out of the provider's network can count. The Edge Network guide lists several cases, and the same patterns apply to any object store:
The Edge Network guide sums this up as egress being driven by your users' behaviour. That makes it harder to predict than storage, because you control how much you store, but your users control how often they read it.
The AIOZ Storage billing docs describe two charges for regular object storage. Bandwidth is charged when you download data, and storage is charged on an hourly basis for the space you use, at the prices on the live billing page:
| Charge | Price |
|---|---|
| Storage | 0.017 USD per GB per month, charged hourly |
| Bandwidth | 0.005 USD per GB downloaded |
A few more rules from the docs matter for planning:
Because the model is pre-paid, a balance that falls too low locks the account. How AIOZ Storage Pricing Works covers the minimum balance and the 3-day deadline in detail.
Multiply the GB you expect to download in a month by the bandwidth rate, then add storage. Using the documented rates and treating 1 TB as 1,000 GB (the docs do not define the unit):
| GB downloaded in a month | Bandwidth charge |
|---|---|
| 1,000 (1 TB) | 5 USD |
| 10,000 (10 TB) | 50 USD |
| 100,000 (100 TB) | 500 USD |
The ratio between reads and stored data decides which bill dominates, because storage costs 0.017 USD per GB-month and bandwidth costs 0.005 USD per GB. The two are equal when you download 0.017 / 0.005 = 3.4 times your stored data each month. Below that ratio storage is the larger charge, and above it bandwidth is.

Here is a small estimator you can adapt, which uses only the two rates above and prints the example in the chart:
STORAGE_USD_PER_GB_MONTH = 0.017 # AIOZ billing docs, charged hourly
BANDWIDTH_USD_PER_GB = 0.005 # AIOZ billing docs, per GB downloaded
def monthly_estimate(stored_gb, downloaded_gb):
storage = stored_gb * STORAGE_USD_PER_GB_MONTH
bandwidth = downloaded_gb * BANDWIDTH_USD_PER_GB
return storage, bandwidth, storage + bandwidth
storage, bandwidth, total = monthly_estimate(stored_gb=10_000, downloaded_gb=30_000)
print(f"storage {storage:.2f} USD, bandwidth {bandwidth:.2f} USD, total {total:.2f} USD")
# storage 170.00 USD, bandwidth 150.00 USD, total 320.00 USDStorage is charged on the space occupied each hour, so a bucket that grows during the month costs less than its final size suggests. Treat the estimator as a ceiling for a bucket that stays full all month.
These are general practices, not AIOZ features, and they apply to any provider that bills for downloads:
I read the billing, overview and penalty pages and found these gaps, which you should treat as unknown until AIOZ states them:
If a number matters for a budget, ask AIOZ support to confirm it before you commit.
What are egress fees in cloud object storage, and why do providers charge them?
Egress fees are charges for data that leaves the provider's network, such as a download, a restore, or a transfer to another cloud, and they are normally priced per GB.
Does AIOZ Storage charge egress fees for downloads from a bucket?
Yes, because the billing docs list bandwidth as a charge incurred when you download data, at 0.005 USD per GB downloaded.
Is uploading data to AIOZ Storage charged as bandwidth in the same way?
The billing docs describe bandwidth charges for downloads only, and they list no upload bandwidth charge for regular object storage.
Does AIOZ Storage bill per request when you list, read or write objects?
The billing docs list no per-request charge for regular object storage, although a separate rate limit of 100 requests per second applies, and the vector database does charge per query.
How much does it cost to download 10 TB from AIOZ Storage?
About 50 USD at the documented rate, if 1 TB is 1,000 GB. The docs do not define the unit, so the exact figure may differ slightly.
Are egress fees the same thing as CDN fees when you serve files to users?
Not always, since a CDN usually bills its own delivery separately. AIOZ's Overview page says its built-in CDN delivers data from the nearest node without extra fees for a separate CDN service, but the bandwidth charge still applies to downloads.

Distributed storage keeps data on many independent nodes that act as one system. See how it works, replication vs erasure coding, its types and trade-offs.

Egress fees are charges for data leaving a storage provider's network. See what triggers them, how to estimate them, and what AIOZ Storage's docs say.

An object storage vector database keeps vectors in the storage layer, not a cluster. See how it differs, when to pick it, and where AIOZ Storage fits in.

AIOZ Storage vector database pricing line by line: upload, storage, queries, data searched and data returned, with a worked monthly example you can reuse.

Create a bucket and upload a file on AIOZ Storage in five steps: sign up, set a passphrase, add credits, and upload. Plus what the passphrase cannot recover.

The AIOZ Storage rate limit is 100 requests per second. See what the docs do and don't say, and how to stay under it with boto3 retries and a limiter.