Billing anomalies

Viewed 35

Billing is abnormal when I create a new container. I'm unsure if this is due to residual resources from deleted containers still consuming resources. Could you please help me clean up or reset my workspace to restore normal billing? Thank you.

ID:H9BR-smdzS
NS:
ns-z2egvc6f
ns-9140ch2c

9 Answers

I checked both of your namespaces and didn't see any resources that needed to be cleaned up. Could you please describe your problem in detail?

When I asked Gemini about the issue, it replied that it might be due to remnants from deleted containers still consuming resources.

I didn't see any abnormal billing from your screenshots.

Previously, when I created containers, a tcp port number was provided free of charge. Now, I've deleted all the containers and created a new one, and the result shows the following information:
0.PNG1.PNG

Opening public TCP ports will incur charges.
image.png

Previously, when creating a new container, there was no billing for one port. It seems the billing rules have changed. Thank you very much for your reply.