Rank, 14 days: 6 on the Vercel sheet
10 people reported
All time, since Sep 8.
Hobby build rate limit stuck
“I am experiencing a deployment block on my Vercel Hobby team.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/vercel/issues/9015/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Hobby deployments blocked by build rate limit below usage limits. GitHub status reports upgradeToPro=build-rate-limit and the block persists "beyond the expected 24-hour period" with no reset timestamp shown.
Is this your bug?
File my report- Where
- GitHub deployments
- Error text
upgradeToPro=build-rate-limit- How bad
- Some reports say it blocks them completely.
Not quite your bug?
- Hobby team stays paused7 people
Original reports10, newest first
- Deployment rate limited — retry in 24 hours, still blocked after 48+ hours#51828
- About Rate limit failed to fetch#51624
- Deployment limit stuck for 48+ hours#50219
- Hobby deployment blocked by build-rate-limit despite being well below usage limits#50194
- Being rate limited on Hobby for deployment limits but I'm well under 100#49793
- API returns HTTP 402 despite team being within usage limits#49642
- Unable to accesos muy Vercel projecto from the dashboard#49495
- Account Blocked#49475
- Hobby Deployment Rate Limit Still Active Beyond 24 Hours: Request for Quota Audit#49382
- Hobby Deployment Rate Limit Still Active After 24+ Hours — Request for Quota Audit#48959