Google Cloud Run asia-south1 stuck with "Project failed to initialize in this region due to quota exceeded" for 4 days — quota resets not helping
Been stuck on this for 4 days and nothing is working.
**The situation:**
Migrated Firebase Cloud Functions from us-central1 to asia-south1.
During deployment, hit the write quota limit (30/min in asia-south1 —
yes, it's tiny). Now ALL 41 Cloud Run services in asia-south1 show:
"Routing traffic: Failed. Project failed to initialize in this region
due to quota exceeded."
**What makes this weird:**
- Code uploaded successfully every time
- The services EXIST in Cloud Run
- Daily quota reset happens — doesn't fix it
- Even `gcloud run services update-traffic myservice --to-latest
--region asia-south1` fails with the same quota error
- `firebase deploy --only functions` says "Skipping unchanged functions"
because code hash didn't change
**What I've tried:**
- Waited for daily quota reset (midnight Pacific) — same error
- Tried gcloud update-traffic directly — same error
- Tried forcing redeploy with code change — quota error again
- Deleted unrelated service to free region slot — same error
- Filed support case — waiting
**My understanding:**
The services are stuck pointing at failed revisions. Fixing them
requires Cloud Run write operations. But those writes are being
throttled. So it's a deadlock — can't fix the quota state without
quota.
**Questions:**
Has anyone recovered from this without Google support intervening?
Is there a way to force Cloud Run to serve traffic from an existing
revision without using the write quota?
How long does the project-level throttle typically last after
repeated quota exhaustion?
Project: Firebase Functions v2 (Cloud Run), asia-south1, Node.js 22
Any help appreciated — this is blocking a production app launch.