Supabase Cache Egress exceeded
I feel like something is wrong on the Supabase end here, I'm being warned for https://supabase.com/docs/guides/platform/manage-your-usage/egress#cached-egress cache-egress overage. Problem is i have a tiny database, with 3-4 edge functions, and < 100 rows, infrequently updated. I am not using Storage, i am not using APIs. i have one webpage , under development that rarely calls the database. I can't seem to figure out why am i being flagged for this.
6 Replies
the docs suggest that there is a usage graph for egress
have you had a look at egress over time, maybe try debugging to see what could be causing it if anything
So there is a graph, but it is pretty much useless. All it does it point to the documentation.
i think the docs said you could run sql/log queries to determine what is cauing the error
it says nothing like that for Cached Egress:
>Cached Egress#
Cached and uncached egress have independent quotas and independent pricing. Cached egress is egress that is served from our CDN via cache hits. Cached egress is typically incurred for storage through our Smart CDN.
feels like some "mystery" value that supabase is intent on changing me for?
how does someone create an actual support ticket here to have Supabase investigate?
You create a Supabase support ticket from the dashboard or going to the support link directly https://supabase.com/dashboard/support/new