Google API: 429 RESOURCE_EXHAUSTED — Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute per user'
Your project or user exceeded an API rate or daily quota.
Quota exceeded for quota metric and limit429 RESOURCE_EXHAUSTED Quota exceeded for quota metricrateLimitExceeded Rate Limit Exceeded Google APIgoogleapi: Error 429: Quota exceeded for quota metric Meaning
The message names the metric and limit. Slow down with exponential backoff, batch requests, cache results, or request a quota increase in IAM & Admin → Quotas. Some quotas are per user, others per project.
Common causes
- Burst of requests above per-minute quota
- Daily quota exhausted
- Loop calling an API without backoff
- Many workers sharing one project quota
- Quota left at the low default
⚡ Quick fix
- Add exponential backoff with jitter
- Request a higher quota in the console
- Batch or cache API calls
Detailed fix by platform
gcloud
gcloud alpha services quota list --service=SERVICE.googleapis.com --consumer=projects/PROJECT
How to diagnose
- Metric — Which limit?
- Rate — Per minute or per day?
- Backoff — Implemented?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- API has not been used in project before or it is disabled Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting
- Artifact Registry: Permission artifactregistry.repositories.uploadArtifacts denied Docker push: denied: Permission "artifactregistry.repositories.uploadArtifacts" denied on resource "projects/p/locations/l/repositories/r"
- BigQuery: Quota exceeded: Your project exceeded quota for free query bytes scanned BigQuery: Quota exceeded: Your project exceeded quota for free query bytes scanned. Consider enabling billing
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- Could not load the default credentials Google Cloud: Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026