Branching billing shows 35 deleted branches still charging compute hours
🌲branching
Issue: Being charged for ~2,000 Branching Compute Hours ($26.81) across 35 branch instances, but
Environment:
- Plan: Pro ($25/month)
- CLI: supabase-cli latest
- Integration: GitLab CI/CD (not Vercel/GitHub)
Billing details:
- Period: Jan 11 - Feb 11, 2026
- 35 separate
- MR-6 appears 25+ times, each showing ~57 hours
- MR-6 was merged on Dec 15, 2025 — before this billing cycle even started
What I've verified:
-
- No branches visible in Dashboard → Branches
- Jan 12 alone shows 864 compute hours — would require 36 parallel DBs running
Questions:
1. Are there "orphan" branches running invisibly that don't appear in CLI/Dashboard?
2. Why does a merged MR from December appear 25+ times in January billing?
3. Is there a known issue where branch deletion doesn't fully stop billing?
4. How can I get visibility into what's actually running?
Already submitted a support ticket but hoping someone in the community has experienced similar issues with branching billing anomalies.
Thanks!
supabase branches listmainEnvironment:
- Plan: Pro ($25/month)
- CLI: supabase-cli latest
- Integration: GitLab CI/CD (not Vercel/GitHub)
Billing details:
- Period: Jan 11 - Feb 11, 2026
- 35 separate
my-project (MR-X)- MR-6 appears 25+ times, each showing ~57 hours
- MR-6 was merged on Dec 15, 2025 — before this billing cycle even started
What I've verified:
-
supabase branches listmain- No branches visible in Dashboard → Branches
- Jan 12 alone shows 864 compute hours — would require 36 parallel DBs running
Questions:
1. Are there "orphan" branches running invisibly that don't appear in CLI/Dashboard?
2. Why does a merged MR from December appear 25+ times in January billing?
3. Is there a known issue where branch deletion doesn't fully stop billing?
4. How can I get visibility into what's actually running?
Already submitted a support ticket but hoping someone in the community has experienced similar issues with branching billing anomalies.
Thanks!
