Hello Vercel Team,

I’m requesting a technical investigation into a deployment-rate-limit issue affecting my Vercel project.

Project: "the-odd-spell" Vercel Team: "dogo-home-match" Plan: Hobby Production URL: "https://the-odd-spell.vercel.app"

The project is currently being blocked from deploying with:

"upgradeToPro=build-rate-limit"

The latest successful production deployment is commit:

"2b6c5cea586d9d2e53d0bf74be0cea33ce3e7c29"

Newer commits exist in GitHub, but Vercel has not successfully deployed them. The latest affected commit is:

"149403e365b91c50f7dbe720de4a9b88b0179d82"

I have already checked the Vercel Usage dashboard. Deployment Storage is 0 GB / 10 GB, and the other usage metrics are also well below their limits, so this does not appear to be a storage-capacity issue.

The deployment-rate-limit condition has persisted beyond the expected 24-hour period.

Could you please audit the actual deployment-rate-limit state for this team/project and clarify:

1. Which deployment events are currently being counted against the Hobby deployment quota.
2. The timestamp of the oldest event currently contributing to the limit.
3. When those events are expected to expire from the rolling limit.
4. Whether failed, canceled, rejected, or automatically generated deployment requests are being included in the calculation.
5. Whether the current rate-limit state is functioning correctly or has become stuck/incorrect.
6. If the quota state is incorrect, please correct or reset the affected deployment-rate-limit state so normal deployments can resume.

I am not requesting an upgrade to Pro. I am specifically asking for an investigation of the current Hobby deployment-rate-limit state.

This is currently blocking active development of a seasonal Halloween project, so I would appreciate an investigation as soon as possible.

Thank you.