- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Creating Instance
- Naming with Consecutive Numeric Suffixes or Designated Pattern String
- Viewing Instance
- Upgrading Instance
- Downgrading Instance Configuration
- Terminating/Returning Instances
- Change from Pay-as-You-Go to Monthly Subscription
- Upgrading Instance Version
- Adding Routing Policy
- Public Network Bandwidth Management
- Connecting to Prometheus
- AZ Migration
- Setting Maintenance Time
- Setting Message Size
- Topic Management
- Consumer Group
- Monitoring and Alarms
- Smart Ops
- Permission Management
- Tag Management
- Querying Message
- Event Center
- Migration to Cloud
- Data Compression
- Instance Management
- CKafka Connector
- Best Practices
- Connector Best Practices
- Connecting Flink to CKafka
- Connecting Schema Registry to CKafka
- Connecting Spark Streaming to CKafka
- Connecting Flume to CKafka
- Connecting Kafka Connect to CKafka
- Connecting Storm to CKafka
- Connecting Logstash to CKafka
- Connecting Filebeat to CKafka
- Multi-AZ Deployment
- Production and Consumption
- Log Access
- Replacing Supportive Route (Old)
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- DataHub APIs
- ACL APIs
- Topic APIs
- BatchModifyGroupOffsets
- BatchModifyTopicAttributes
- CreateConsumer
- CreateDatahubTopic
- CreatePartition
- CreateTopic
- CreateTopicIpWhiteList
- DeleteTopic
- DeleteTopicIpWhiteList
- DescribeDatahubTopic
- DescribeTopic
- DescribeTopicAttributes
- DescribeTopicDetail
- DescribeTopicProduceConnection
- DescribeTopicSubscribeGroup
- FetchMessageByOffset
- FetchMessageListByOffset
- ModifyDatahubTopic
- ModifyTopicAttributes
- DescribeTopicSyncReplica
- Instance APIs
- Route APIs
- Other APIs
- Data Types
- Error Codes
- SDK Documentation
- General References
- FAQs
- Service Level Agreement (New Version)
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Creating Instance
- Naming with Consecutive Numeric Suffixes or Designated Pattern String
- Viewing Instance
- Upgrading Instance
- Downgrading Instance Configuration
- Terminating/Returning Instances
- Change from Pay-as-You-Go to Monthly Subscription
- Upgrading Instance Version
- Adding Routing Policy
- Public Network Bandwidth Management
- Connecting to Prometheus
- AZ Migration
- Setting Maintenance Time
- Setting Message Size
- Topic Management
- Consumer Group
- Monitoring and Alarms
- Smart Ops
- Permission Management
- Tag Management
- Querying Message
- Event Center
- Migration to Cloud
- Data Compression
- Instance Management
- CKafka Connector
- Best Practices
- Connector Best Practices
- Connecting Flink to CKafka
- Connecting Schema Registry to CKafka
- Connecting Spark Streaming to CKafka
- Connecting Flume to CKafka
- Connecting Kafka Connect to CKafka
- Connecting Storm to CKafka
- Connecting Logstash to CKafka
- Connecting Filebeat to CKafka
- Multi-AZ Deployment
- Production and Consumption
- Log Access
- Replacing Supportive Route (Old)
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- DataHub APIs
- ACL APIs
- Topic APIs
- BatchModifyGroupOffsets
- BatchModifyTopicAttributes
- CreateConsumer
- CreateDatahubTopic
- CreatePartition
- CreateTopic
- CreateTopicIpWhiteList
- DeleteTopic
- DeleteTopicIpWhiteList
- DescribeDatahubTopic
- DescribeTopic
- DescribeTopicAttributes
- DescribeTopicDetail
- DescribeTopicProduceConnection
- DescribeTopicSubscribeGroup
- FetchMessageByOffset
- FetchMessageListByOffset
- ModifyDatahubTopic
- ModifyTopicAttributes
- DescribeTopicSyncReplica
- Instance APIs
- Route APIs
- Other APIs
- Data Types
- Error Codes
- SDK Documentation
- General References
- FAQs
- Service Level Agreement (New Version)
- Contact Us
- Glossary
Note:
If you are the customer of a Tencent Cloud partner, your agreement with the partner will be applied to handle product resources under an account with overdue payments.
Payment Overdue for Pay-as-You-Go Instances
The CKafka instance is billed on a pay-as-you-go basis, with the fee automatically deducted from the account balance once a month. Your service usage in the previous month will be billed at the start of the next month, and any costs incurred will be deducted from your account.
If your account balance is insufficient, but the current usage is within the free tier, you can continue to use the service.
If your account balance becomes insufficient and your account isn't eligible for the non-stop feature, you can continue to use CKafka for 24 hours, and we will continue to bill you for this period. After 24 hours, the CKafka service will be stopped, you cannot send/receive messages or use the console and TencentCloud API, but resource usage fees will still be incurred.
After the service is stopped, the system will process CKafka as follows:
Time After Service Suspension | Description |
≤7 days | If your account is topped up to a positive balance, the billing will continue, and you can restart CKafka. |
| If your account balance remains negative, CKafka cannot be restarted. |
＞7 days | If your account is not topped up to a positive balance, your pay-as-you-go CKafka resources will be terminated. All data will be deleted and cannot be recovered. When your resources are terminated, your Tencent Cloud root account and subscription sub-accounts and collaborators will be notified by email and SMS. |
Payment Overdue for Monthly Subscribed Instances
Expiration alert
Seven days before your monthly subscribed CKafka instance expires, the system automatically pushes an expiration alert message to you every other day. All alert messages are sent to the Tencent Cloud account creator and all collaborators by email and SMS.
Overdue payment alert
From the day when your CKafka instance expires, an alert message of isolation due to overdue payment is sent to you every other day. All alert messages are sent to the Tencent Cloud account creator and all collaborators via email and SMS.
Repossession
Seven days before the Ckafka instance expires, you will receive a renewal reminder.
If your account balance is sufficient and auto-renewal is enabled, the device will be automatically renewed on the expiry date of the CKafka instance.
If the CKafka instance is not renewed within 7 days (inclusive) after expiration, it will be disabled at midnight on the 8th day (devices are disconnected and shut down, CKafka services are suspended, and only data and configurations are retained).
After shutdown, the CKafka instance will be forcibly unmounted from upstream and downstream components. Upon renewal, its mounting relationship cannot be restored and must be reconfigured.
You can still renew the instance in Billing Center > Renewal Management within 7–14 days after expiration. The billing cycle of the renewed instance will start from the expiry date of the previous cycle.
If the CKafka instance is not renewed within 14 days (inclusive) after expiration, its resources will be released at midnight on the 15th day, and data will be cleared and cannot be restored.
Yes
No
Was this page helpful?