General steps, last reviewed Oct 14, 2026. Not legal or financial advice.
What should I do first?
Stop the bleeding. Turn on the provider's pause/cap if one exists (see the table), e.g. Vercel's Pause Production Deployments or an OpenAI hard spend limit. On Google Cloud, disabling billing stops services but Google warns resources might be irretrievably deleted.
Rotate or delete leaked keys. AWS and Google Cloud both document deleting unneeded/compromised keys and creating new ones. Restrict API keys (Google Cloud best practice).
Find the source. Check usage pages by project, key and SKU before deleting anything you may need as evidence.
Contact support quickly through the official billing support channel (e.g. open an AWS Support case). Explain the timeline and what you did. Refunds or credits are at the provider's discretion; nothing here promises one.