Multi-year project-creation quota block, tied to a project I don't own inside another org - quota increase requests auto-denied twice

Hi all,

I’ve been unable to create any Google Cloud project on my personal account for a long time (I believe multiple years, though I can’t pin the exact start date). I recently dug into it myself and found some concrete but confusing details, and I’m hoping someone with visibility into the internal quota/resource-manager systems can help.

Symptom: Clicking “Create Project” always redirects to “Increase Project Limit” with “You’ve reached your project limit.”

What I found: The only project visible under my account is “titanium-case-hbhkf”, a project I never created and don’t manage. I have zero IAM permissions on it (Console: “You need additional access”, missing resourcemanager.projects.getIamPolicy), and the Delete/Shut down action is disabled for me on the Resource Manager page. Under Billing then Your projects, this project is linked to a billing account belonging to a completely different organization (“TI Cloud” > AI and IndustrySolns > Retail), not my own billing account (which is healthy, zero spend, no holds). The project’s Settings page also shows a real Organization and folder path under “Location”, so this project genuinely sits inside someone else’s Cloud org, not a random orphan.

I also found I was a member of a Google Group (a closed test group for a third-party app) that had been granted access to this same project, and I’ve since left that group. But my quota problem seems to predate joining that group by a long time, so I don’t think that’s the (whole) explanation, and I still don’t know why this specific unrelated project is the one counted against my personal project-creation quota.

I’ve submitted the official Project Quota Increase form twice, with a detailed explanation the second time. Both times I got the exact same boilerplate denial about “previous usage/history” and “abuse penalties,” which reads like an automated decision rather than a human reviewing the details.

Has anyone seen a case where a project you don’t own, create, or administer ends up permanently consuming your personal project-creation quota like this? Is there a way to get Google to actually investigate why this account-to-project association exists and disconnect it, rather than just re-requesting a quota increase? Any pointers to the right internal team or escalation path would be hugely appreciated.

Thanks!

1 Like