Hello Vercel Team,
I am requesting a technical investigation into a deployment-rate-limit issue affecting my Vercel project.
Project information
Vercel Project: ovs-enterprise-lms Vercel Team: SRO-webovs-enterprise-v02 Production domain: ovs-lms.flowvim.com GitHub repository: SRO-web/ovs-enterprise-lms Plan: Hobby
Issue
Our Vercel deployment is currently being blocked with the following rate-limit indication:
upgradeToPro=build-rate-limit
The important point is that the last successful production deployment occurred on:
September 7, 2026 at approximately 01:10–01:11 WAT (UTC+1).
The last successful production deployment was associated with commit:
b3921af86d69846e77489ff87094929f192d13b0
Commit message:
Make lesson narration follow current edited content
After that successful deployment, development work continued in GitHub, but the subsequent Vercel deployment checks have failed because of the deployment rate limit.
There have been no subsequent successful production deployments.
As of September 8, 2026 at approximately 06:58 WAT, the deployment restriction was still active.
This means that more than 29 hours had elapsed since the last successful deployment activity, while Vercel was still returning the deployment-rate-limit condition.
What we have verified
The Vercel deployment history shows the above deployment as the latest successful production deployment.
The subsequent GitHub commits were not successfully deployed, and the Vercel/GitHub deployment checks report the deployment-rate-limit condition rather than a normal application build failure.
Vercel documentation indicates that the Hobby deployment limit operates over a 24-hour period.
Therefore, I would appreciate an investigation into the actual rate-limit state associated with this team/project.
Request for investigation
Could the Vercel team please check:
Which deployment events are currently being counted against the Hobby deployment quota for this team/project. The timestamp of the oldest deployment event currently contributing to the rate limit. The expected expiration time of those counted events under the rolling 24-hour limit. Whether any rejected, failed, or automatically generated deployment requests are being retained in the quota calculation. Whether the current rate-limit state is functioning as intended or has become stuck/incorrect. If the quota state is incorrect, please correct or reset the affected deployment-rate-limit state so that normal deployments can resume.
I am not requesting an account-plan change. I am specifically requesting an audit of the current deployment-rate-limit state and clarification of why the restriction remains active beyond the expected 24-hour period.
I would be grateful if someone from the Vercel team could review the account/project-level deployment records and advise on the cause.
Thank you.