dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-06 09:55:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix: clarify cached egress only for Storage (#40212)

Browse Source
This commit is contained in:
Wen Bo Xie authored and GitHub committed 2025-11-06 17:57:59 +01:00
1 parent 6a142b7752
commit 252ff08c4c
2 files changed
+2 -2
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

apps/docs/content/guides/platform/billing-faq.mdx
+1 -1
View File
@@ -68,7 +68,7 @@ Read more about [Compute usage](/docs/guides/platform/manage-your-usage/compute)
Egress refers to the total bandwidth (network traffic) quota available to each organization. This quota can be utilized for various purposes such as Storage, Realtime, Auth, Functions, Supavisor, Log Drains and Database. Each plan includes a specific egress quota, and any additional usage beyond that quota is billed accordingly.
We differentiate between cached (served via our CDN from cache hits) and uncached egress and give quotas for each type and have varying pricing (cached egress is cheaper).
We differentiate between cached (served via our CDN from cache hits) and uncached egress and give quotas for each type and have varying pricing (cached egress is cheaper). Cached egress only applies to Storage.
Read more about [Egress usage](/docs/guides/platform/manage-your-usage/egress).
apps/docs/content/troubleshooting/all-about-supabase-egress-a_Sg_e.mdx
+1 -1
View File
@@ -35,6 +35,6 @@ While pointing out the exact cause for egress may not be straightforward, there
**Cached vs uncached egress**
We differentiate between cached and uncached egress. Cached egress refers to egress that is served via our CDN and hits the cache. Uncached egress, on the other hand, refers to egress that is not served from the cache and requires a fresh request to the origin server.
We differentiate between cached and uncached egress. Cached egress, which only applies to Supabase Storage, refers to egress that is served via our CDN and hits the cache. Uncached egress, on the other hand, refers to egress that is not served from the cache and requires a fresh request to the origin server.
Your plan includes a quota for both cached and uncached egress and these are independent. Cached egress is also cheaper in case you exceed your quota.