Project stopped creating deployments entirely - push, Redeploy, and Deploy Hooks all silently no-op

Project “tourrated” (prj_YfkM15T0Jybt6uqpaPHTBnSMngAS) on the Hobby plan has stopped creating new deployments entirely, for over 24 hours now. I’ve tried every mechanism I know of and none of them produce a deployment.

**What I’ve tried, in order:**

1. Pushed a commit to the connected GitHub repo on branch `main`. No deployment was ever created for it - not Ready, Building, Queued, Initializing, Error, or Canceled (checked with all statuses included in the filter). It simply never appears in the Deployments list.

2. To rule out a GitHub webhook issue, I created a Deploy Hook (branch “main”) and triggered it directly via POST to the hook URL. The API responded with a 200 and a job body like `{“job”:{“id”:“…”,“state”:“PENDING”,…}}`, confirming Vercel accepted the request. No deployment was ever created from this either - the project’s own Activity Log shows “You created deploy hook…” but no matching “deployed” entry afterward, even though every other deploy hook/push in the log has one.

3. Used the “Redeploy” button on an existing deployment from the dashboard - this worked, but it just rebuilds that specific old commit, not the current branch HEAD, so it doesn’t help get new commits live.

4. Pushed a brand new empty trigger commit - same result as #1, nothing happens.

5. Disconnected and reconnected the GitHub integration entirely (Project Settings > Git > Disconnect, then reconnect to the same repo), then pushed again - still nothing.

**Other things I checked:**

- vercel-status.com shows all systems operational, no incidents.

- Team billing looks normal, nothing flagged.

- One thing that stood out: the project’s Usage page shows “Build Minutes: 0s / 0s” (zero-out-of-zero), unlike every other metric which shows real usage against a real limit. Not sure if this is a legacy/unused metric on this plan or an actual sign of something blocking builds.

Since even a direct Deploy Hook API call (which bypasses GitHub entirely) fails to produce a deployment, this doesn’t seem like a GitHub integration problem - it looks like something on Vercel’s side is silently blocking new deployments for this specific project.

I don’t have access to ticketed support on Hobby for this category, so posting here. Has anyone seen this before, or does anyone know what could cause deployments to just silently never start? Happy to share more diagnostics if helpful.