Guide
auth/too-many-requests
How this guide was made: Written with AI assistance and checked against the sources linked on this page.
Updated
Short answer: auth/too-many-requests means Firebase blocked requests because a limit was reached. The limit can be a device block, an SMS send limit, a per-IP limit or a request rate. Our suggestion: stop any retry loop, wait, then find which limit applies before you try again. For phone sign-in, use fictional test numbers while you test.
What does auth/too-many-requests mean?
The code is the same in the Web SDK and the Admin SDK, but the message text differs. In the Web SDK, the message is: "We have blocked all requests from this device due to unusual activity. Try again later." In the Admin SDK, the message is: "The number of requests exceeds the maximum allowed." (Firebase JS SDK: errors.ts, Firebase: Admin SDK errors)
Firebase's limits page lists the per-IP, per-project and SMS limits that can cause this. It also says: "Abuse protections may be enabled without warning on accounts that demonstrate suspicious traffic patterns." (Firebase: Authentication limits) The pages we read do not say how long a block lasts.
Which cause is it?
| What you see | Cause | Fix |
|---|---|---|
| An Admin script or server job fails after many calls in a short time | The request rate is too high for the limit | Cause 1 |
| Web sign-in says the device is blocked for unusual activity | This device is blocked | Cause 2 |
| Phone sign-in stops sending codes | The SMS limit, or the per-phone-number limit, was reached | Cause 3 |
| Sign-ups from one IP address fail | The per-IP limit was reached | Cause 4 |
| No limit explains the block | Abuse protection was enabled | Cause 5 |
1. Your code sends requests too fast
The Admin SDK page lists this code with the message "The number of requests exceeds the maximum allowed." It does not give a fix. The limits page lists per-project rates, such as "Account configuration updates: 10 requests/second" and "Batch account deletion: 1 request/second." (Firebase: Authentication limits)
- Find the job or loop that calls Firebase Auth. Look for retries that run with no wait.
- Compare the call rate with the limits on the limits page.
- Our suggestion: add a delay before each retry, and make the delay longer after each failed try. Stop after a set number of tries.
- Run the job with a small batch first, then increase the batch size.
2. This device is blocked after unusual activity
The Web SDK message for this code is: "We have blocked all requests from this device due to unusual activity. Try again later." (Firebase JS SDK: errors.ts)
- Stop sending sign-in attempts from this device. Do not keep pressing the sign-in button.
- Wait, then try again later, as the message says.
- Our suggestion: if you must test now, try from another device on another network. The pages we read do not say whether this clears a device block.
3. Phone sign-in hits an SMS limit
The limits page lists these verification SMS limits: "900 sent/minute, 3,000 sent/day" for the project, and "50 sent/minute, 500 sent/hour" per IP address. It also says there is a limit on how many verification SMS a project can send to one phone number within a set time. (Firebase: Authentication limits)
- Check whether your tests send codes to real phone numbers.
- Use fictional test numbers. The limits page says: "You can test with fictional numbers or across multiple devices to ensure a project does not exceed these limits."
- Turn on Activity Logging to track verification codes sent per phone number. The limits page says you can track them "if you've enabled Activity Logging on your project."
- For higher SMS limits, the page says: "Upgrade to Google Cloud Identity Platform for higher SMS limits."
4. One IP address hits a per-IP limit
The limits page lists "New account creation: 100 accounts/hour for each IP address" and "createAuthURI calls per IP address: 120 requests/hour." (Firebase: Authentication limits)
- Check whether many sign-ups or sign-ins come from one IP address, such as an office network, a school network or a test rig.
- Spread test traffic across networks, or wait until the hourly window passes.
- If you expect a launch or a burst of sign-ups, the page says: "You can schedule a temporary increase to the account creation limit in the Firebase console."
5. Abuse protection was enabled
The limits page says abuse protections "may be enabled without warning on accounts that demonstrate suspicious traffic patterns." (Firebase: Authentication limits)
- Stop any script or bot that sends traffic to your sign-in pages.
- If the traffic is real and you expect growth, the page says to "contact Firebase support at least two weeks in advance to discuss your quota adjustment needs."
- Our suggestion: after you stop the traffic, wait before you test again, then test with one account.
How do I check it's fixed?
- Our suggestion: after the cause is fixed, sign in once from a private window on your live app.
- Confirm sign-in completes and the next screen loads, with no auth/too-many-requests error.
- For phone sign-in, send one code to a fictional test number, then one to a real number you own.
- If the error returns on the same code path, the loop, the rate or the limit is still there. Go back to the cause that matches what you see.
FAQ
Does auth/too-many-requests mean my account is banned?
The pages we read do not describe a ban. They describe limits and abuse protections that "may be enabled without warning" for suspicious traffic. Our suggestion: stop the traffic that triggers the limit and contact Firebase support if the block stays.
How long does the block last?
The pages we read do not give a reset time. Wait, then try again with fewer requests.
Can I raise the limit?
For some limits, yes. The limits page says to contact Firebase support at least two weeks in advance for a quota adjustment. For account creation, you can schedule a temporary increase in the Firebase console. For SMS, the page points to Google Cloud Identity Platform.
Can VibeFix fix it for me?
Yes, for apps built in Lovable or any app whose code is on GitHub. The free check confirms the problem on your live app first. If you want it fixed, our AI agent finds the cause, fixes it in your code for $79 and tests your live app again. See pricing.
Related guides
- Firebase auth: unauthorized domain
- Firebase Google sign-in not working: enable the provider
- Lovable login loop: why you keep returning to sign-in
Sources
- Firebase: Authentication limits
- Firebase: Admin SDK errors
- Firebase JS SDK: errors.ts
- Firebase JS SDK reference: auth.md (auth/too-many-requests code value)
Last checked: 17 November 2026.
VibeFix is independent. Firebase is a trademark of its owner.
More guides · Shopify store accessibility · About · Your privacy choices