Unexplained GitHub Advanced Security charges, disabled everywhere, support ticket open 3+ weeks with no response

[laxmank03]

🏷️ Discussion Type

Bug

Body

Hi everyone,

We've been billed for GitHub Advanced Security (Code Security and Secret Protection) on our organization for several months now. Our most recent invoice (INV150855897, dated Aug 16, 2026) charged $257.65 for Advanced Security Usage alone, plus $18.73 for Code Quality Usage, against a base Team plan cost of $36.00 for our 9 seats. The Advanced Security and Code Quality charges alone made up close to 90 percent of that invoice.

The amount has varied by billing cycle, it was around $238 the month before, but the underlying issue is the same each time:

• Code Security and Secret Protection show as disabled on every single repository in our organization
• Our Licensing page shows 0 consumed licenses for both features
• We only have 9 total seats on our Team plan, so the billable license count previously shown (12) doesn't add up on its own
• We're on a straightforward GitHub Team plan, nothing unusual about our setup

We opened a support ticket (4616081) over three weeks ago with full details, followed up twice since, and have had no response at all. Meanwhile the charges keep recurring on every billing cycle.

Has anyone else run into GHAS billing that doesn't match what's actually visible/enabled in the dashboard? And does anyone know a faster way to get GitHub's attention on an unresponsive billing ticket?

Organization: HARA-Solutions-Limited
Ticket: 4616081

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐