tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
Product Strengths
Use Cases
Storage Engine
Product Series
Product Versions
Specifications and Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
Pricing Center
Instance Purchasing
Renewal (Yearly/Monthly Subscription)
Refund (Yearly/Monthly Subscription)
Overdue Payments
Switching from Pay-as-You-Go to Yearly/Monthly Subscription
Getting Started
Quickly Creating an Instance
Connecting to Redis Instance
Operation Guide
Operation Overview
Connecting to a Database Instance
Managing Instances
Upgrade Instance
Management Node (Redis/ValKey Edition)
Multi-AZ Deployment Management
Backup and Restoration
Managing Accounts
Parameter Configuration
Slow Query
Access Management
Network and Security
Monitoring and Alarms
Event Management (Redis/ValKey Edition)
Data Migration
Global Replication for Redis Edition
Database Audit
Performance Optimization
Sentinel Mode
Development Guidelines
Naming Rules
Basic Usage Guidelines
Design Principles of Key and Value
Command Usage Guidelines
Design Principles of Client Programs
Connection Pool Configuration
Command Reference
Command Reference Overview
Redis Edition and Valkey Edition Command Compatibility
Version Command Usage Differences
Differences Between the Proxy Architecture and Direct Connection Mode
More Command Operations (Redis/Valkey Edition)
Memcached Edition Command Compatibility
Practical Tutorial
Building TencentDB for Redis® Client Monitoring Based on Spring Boot
Redis Client Connection Configuration Policy and Practice
Global SCAN Guide for Cluster Architecture
Eliminating Instances Securely
Hot Key and Big Key
AZ Migration Scheme
Troubleshooting
Connection Exception
Exception Analysis and Solution of Redisson Client Timeout Reconnection
Performance Troubleshooting and Fine-Tuning
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
FAQs
General
Connection and Login
Purchase
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Overdue Payments

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-17 16:36:36
When cloud database resources in yearly/monthly subscription mode expire or the available balance of your cloud service account in pay-as-you-go billing mode is less than the billing amount (account in arrears), cloud database instance resources will be gradually shut down and finally released and terminated. To avoid service suspension, top up your account promptly for renewal to ensure continuous and stable operation.

Yearly/Monthly Subscription

When instances are purchased in yearly/monthly subscription billing mode, you need to prepay for an entire month or a whole year. Instances will be released and terminated after expiration if they are not renewed in time. For the handling mechanism upon resource expiration, see the following figure and table.

Stage
Duration
Status and Handling Mechanism
Validity period
Within 7 days before expiration
Cloud resources with auto-renewal disabled: Tencent Cloud will send a notification about resource expiration every other day until a successful renewal is made, regardless of whether the account balance is sufficient.
Cloud resources with auto-renewal enabled: When the account balance is insufficient, Tencent Cloud will send a notification every other day reminding the user to recharge the account for auto-renewal, until the renewal is successfully completed.
Note:
If no renewal is made on the day before cloud database resource expiration or the day of expiration, Tencent Cloud will notify the user of the service expiration time and resource release time via voice call (the actual receiving method is subject to the subscription configuration in Message Center). In this way, the user can take timely measures.
Grace period
Within 7 days after expiration
Cloud database resources can still be accessed normally, and the service is not suspended.
Cloud resources with auto-renewal disabled: Tencent Cloud will send a notification about resource suspension every other day until a successful renewal is made.
Cloud resources with auto-renewal enabled: The system will retry auto-renewal every day. If the account balance is insufficient, the user will be notified of the auto-renewal failure until the service is suspended. After the service is suspended, no more auto-renewal attempts will be made.
If no successful automatic or manual renewal is made before the end of the 7th day after resource expiration, cloud database resources will be suspended and retained in the recycle bin.
Note:
If cloud database resources are renewed within the grace period, the billing start time will be the end time of the original billing cycle.
Upon resource suspension, Tencent Cloud will notify the user of the resource release time via voice call (the actual receiving method is subject to the subscription configuration in Message Center). In this way, the user can take timely measures.
Retention period
Within 7 days after shutdown
Cloud database resources become unavailable after shutdown. The instances are isolated in the recycle bin.
Restorable: Instances can be restored from the recycle bin. For detailed operations, see Restoring Isolated Instances.
At the end of the 7th day after shutdown, they will be cleared from the recycle bin and can no longer be manually restored.
Note:
If cloud database resources are renewed within the retention period, the billing start time will be the end time of the original billing cycle.
On the 7th day after shutdown, Tencent Cloud will notify the user of the resource release time via voice call (the actual receiving method is subject to the subscription configuration in Message Center). On the 8th day after shutdown, the user will be notified of resource release.
From the 8th day to the 15th day after shutdown
Cloud resource instances will be cleared from the recycle bin 7 days after shutdown, and the instance backups will be stored in the backend for 8 days. To restore instances, contact Tencent Cloud engineers.
At the end of the 15th day after shutdown, all backup data will be deleted and cannot be restored.
Invalidity period
15 days after shutdown
Cloud database resources are completely terminated, and all data is deleted and cannot be restored.

Pay-as-You-Go

If instances are purchased in pay-as-you-go billing mode, the billing system performs settlement every hour on the hour. If the available balance of your account is insufficient (less than 0) at the time of settlement, the fees of the previous hour cannot be deducted. In this case, your account is considered in arrears. For the specific handling mechanism, see the following figure and table.
Note:
The system will notify the Tencent Cloud account creator, global resource collaborator, and financial collaborator via email and SMS message (the actual receiving method is subject to the subscription configuration of Message Center).

Stage
Duration
Status and Handling Mechanism
Grace period
Within 24 hours after the account enters arrears
Cloud database resources can still be accessed normally, and the service is not suspended.
Normal billing: Cloud database resources can still be accessed normally within 24 hours after the account balance is less than 0, and billing continues.
At the end of the 24th hour after the account enters arrears, if the balance has not been successfully topped up to zero or above, cloud database resources will be suspended and retained in the recycle bin.
Note:
When the Tencent Cloud account enters arrears, an overdue payment notification will be sent, which contains the overdue payment amount, the expected service suspension time for all pay-as-you-go resources under the account, and the final termination time.
Retention period
Within 7 days after shutdown
Cloud database resources become unavailable after shutdown. The instances are isolated in the recycle bin.
Restorable: If the balance has not been successfully topped up to zero or above, instances can be restored from the recycle bin. For detailed operations, see Restoring Isolated Instances.
At the end of the 7th day after shutdown, they will be cleared from the recycle bin and can no longer be manually restored.
Note:
When the Tencent Cloud account enters arrears, a service suspension notification will be sent, which contains the overdue payment amount, all the suspended services under the account, and the final termination time.
From the 8th day to the 15th day after shutdown
Cloud resource instances will be cleared from the recycle bin 7 days after shutdown, and the instance backups will be stored in the backend for 8 days. To restore instances, contact Tencent Cloud engineers.
At the end of the 15th day after shutdown, all backup data will be deleted and cannot be restored.
Invalidity period
15 days after shutdown
All backups of the cloud database resources are completely terminated and cannot be restored.
Note:
When the resources are terminated, a notification will be sent, which contains the overdue payment amount and all the terminated services under the account.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백