© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Search
Star
Feedback
Setup for Free
URGENT: Project still restricted after cached egress quota reset (production app offline) - Supabase
S
Supabase
•
3w ago
•
12 replies
Moh-M_
URGENT: Project still restricted after cached egress quota reset (production app offline)
🤷
other
Hi
— we have a production outage and need help from a Supabase team member
.
Our project was restricted earlier due to
exceed_cached_egress_quota
exceed_cached_egress_quota
. We waited for the billing cycle reset and the dashboard now shows the quota is no longer exceeded
.
However the restriction is still active and all requests return
:
"Service for this project is restricted due to exceed
_cached
_egress
_quota
.
"
We already tried
:
• waiting for the billing reset
• pause
/ resume
• full project restart
• redeploying an edge function
The restriction is still there
.
Project ref
: gyiwsrjdcidpiypjkbfg
This is affecting our production delivery app
.
Could someone from the Supabase team please help clear the restriction
?
Supabase
Join
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
46,176
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Similar Threads
Was this page helpful?
Yes
No
Recent Announcements
Similar Threads
Project Still Restricted After Billing Cycle Reset (Egress Quota)
S
Supabase / help-and-questions
6d ago
Cached Egress
S
Supabase / help-and-questions
6mo ago
DB quota cleared but Supabase still restricted?
S
Supabase / help-and-questions
2mo ago
Cached Egress Question
S
Supabase / help-and-questions
3w ago