Title: Hobby build-rate-limit still active after 24+ hours — request for quota audit
Hello Vercel Team,
I am requesting an investigation into a deployment/build rate-limit issue affecting my Hobby account.
Project: salon-core-spike-7
Team / scope: rogeliocarrascoquiroz-9562
Plan: Hobby
GitHub repository: rogeliocarrascoquiroz-stack/salon-core-spike-7
Current error: upgradeToPro=build-rate-limit
The restriction has now persisted for more than 24 hours.
The merge to main that was blocked by this condition was:
Commit: 370e2621a7cf8d395675703a7c6308e2b1afbcbf
The Vercel/GitHub status for that commit still reports the build-rate-limit condition rather than an application build failure.
What I have already verified:
- There are no visible deployments stuck in Building or Initializing.
- The deployments visible in the Vercel dashboard are in Ready state.
- The account is on the Hobby plan.
- I reviewed Team Settings > Billing, but no deployment quota/reset timestamp is shown there.
- Vercel platform status does not indicate a general build outage.
- The rate-limit condition has remained active beyond the expected rolling 24-hour period.
Could you please audit the deployment-rate-limit state for this team and project and confirm:
- Which deployment events are currently being counted against the Hobby deployment quota.
- The timestamp of the oldest event still contributing to the limit.
- When the current restriction is expected to expire.
- Whether failed, rejected, canceled, or automatically generated Git deployments are being counted.
- Whether the quota state is functioning normally or has become stuck.
- If the state is incorrect, please reset/correct the deployment-rate-limit so normal deployments can resume.
I am not requesting a plan upgrade. I am specifically asking for a quota audit because the restriction has persisted beyond 24 hours and is blocking active development.
Thank you.