cancel
Showing results for 
Search instead for 
Did you mean: 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

Premium account suspended 6+ days over a $0.51 invoice we can't pay — billing unresponsive

Khikmatullaev
New Contributor

Hi all — hoping a Databricks employee or admin can help escalate.

Our Premium account has been fully suspended for 6+ days because of a $0.51 past-due invoice. We cannot pay it: we have no NetSuite Customer Payment Portal login, and the payment link will not let us sign in. As a result, all compute — classic clusters and serverless SQL/notebooks — fails with RESOURCE_EXHAUSTED in every region and workspace.

We have emailed billing@databricks.com and cust-success@databricks.com several times (support/billing cases are open) and submitted in-product feedback, but have only received automated acknowledgments — no human contact and no resolution. This has already caused us to miss a production deadline, all over 51 cents we are actively trying to pay.

Could a Databricks staff member please help escalate so we can either be charged on the card already on file or sent a working payment link, and have compute re-enabled? I can share account ID and case numbers privately via DM. Thank you.

1 ACCEPTED SOLUTION

Accepted Solutions

Ashwin_DSA
Databricks Employee
Databricks Employee

Hi @Khikmatullaev,

I’m sorry you’ve been blocked for this long, especially over such a small past-due amount.

Please send me a private DM with your Databricks account ID, affected workspace ID(s), invoice number (if you have it), and the open billing/support case numbers. Please do not post any of that publicly here.

I’ll help route this internally for urgent review so the team can look into two things in parallel:

  1. Getting you a working payment path for the outstanding invoice, and
  2. Reviewing restoration of compute access once billing can validate the account state.

In the meantime, it may also be worth checking whether your account is billed through AWS, Azure, or GCP Marketplace rather than directly through Databricks, since that could change the payment path. If you are a direct customer and can access your Databricks account console billing settings, it may also be worth checking whether you can update the payment method there.

Thank you for spelling out the impact clearly, and I’m sorry again that this has affected your production timeline.

Look forward to your message.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.

Regards,
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***

View solution in original post

1 REPLY 1

Ashwin_DSA
Databricks Employee
Databricks Employee

Hi @Khikmatullaev,

I’m sorry you’ve been blocked for this long, especially over such a small past-due amount.

Please send me a private DM with your Databricks account ID, affected workspace ID(s), invoice number (if you have it), and the open billing/support case numbers. Please do not post any of that publicly here.

I’ll help route this internally for urgent review so the team can look into two things in parallel:

  1. Getting you a working payment path for the outstanding invoice, and
  2. Reviewing restoration of compute access once billing can validate the account state.

In the meantime, it may also be worth checking whether your account is billed through AWS, Azure, or GCP Marketplace rather than directly through Databricks, since that could change the payment path. If you are a direct customer and can access your Databricks account console billing settings, it may also be worth checking whether you can update the payment method there.

Thank you for spelling out the impact clearly, and I’m sorry again that this has affected your production timeline.

Look forward to your message.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.

Regards,
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***