- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Service Management
- Creating API
- API Creation Overview
- Creating APIs Connecting to the Public URL/IP Backend
- Creating APIs Connecting to the VPC Resource Backend
- Creating APIs Connecting to the SCF Backend
- Creating API for Interconnecting Backend with COS
- Creating APIs Connecting to the Mock Backend
- Creating APIs Connecting to the TSF Backend
- Importing APIs
- API Management
- Calling API
- Release and Access
- Custom Domain Name and Certificate
- Usage Plan
- Backend Upstream
- Verification and Security
- Log Statistics
- Access Monitoring
- API Doc Generator
- Application Management
- Permission Management
- Precautions
- Private IP Ranges and Public VIPs of API Gateway Regions
- Plugin Usage
- Best Practices
- Making Serverless Service Available quickly through API Gateway
- Integrating WAF to API Gateway for Security Protection
- Accessing Resources in IDC via API Gateway Dedicated Instance
- Quick Access to TEM Application via API Gateway
- Integrating ECDN to API Gateway for Acceleration
- API Gateway Providing the Access Capability for TKE
- Migrating from Region A to Region B
- Development Guide
- API Documentation
- Legacy Features
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Service Management
- Creating API
- API Creation Overview
- Creating APIs Connecting to the Public URL/IP Backend
- Creating APIs Connecting to the VPC Resource Backend
- Creating APIs Connecting to the SCF Backend
- Creating API for Interconnecting Backend with COS
- Creating APIs Connecting to the Mock Backend
- Creating APIs Connecting to the TSF Backend
- Importing APIs
- API Management
- Calling API
- Release and Access
- Custom Domain Name and Certificate
- Usage Plan
- Backend Upstream
- Verification and Security
- Log Statistics
- Access Monitoring
- API Doc Generator
- Application Management
- Permission Management
- Precautions
- Private IP Ranges and Public VIPs of API Gateway Regions
- Plugin Usage
- Best Practices
- Making Serverless Service Available quickly through API Gateway
- Integrating WAF to API Gateway for Security Protection
- Accessing Resources in IDC via API Gateway Dedicated Instance
- Quick Access to TEM Application via API Gateway
- Integrating ECDN to API Gateway for Acceleration
- API Gateway Providing the Access Capability for TKE
- Migrating from Region A to Region B
- Development Guide
- API Documentation
- Legacy Features
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
Private IP Ranges and Public VIPs of API Gateway Regions
Last updated: 2023-12-26 14:35:54
Warning:
Tencent Cloud platform is planning to upgrade shared services in different regions in the following time periods:
1. Before the official upgrade, the platform will uniformly send various notifications such as SMS and Message Center.
2. During the upgrade process, your service access will not be affected.
3. After the completion of the upgrade, the public network VIPs of the shared services will change.
For services created under shared instances in the API Gateway, you may refer to the following information to check the private network gateway and the public network IP.
The private network ranges can be used for interconnection, while the public network VIPs can be used to differentiate the outbound traffic for ultimately generating the billing statement.
Note:
Shared instances are multi-user, and the public network VIPs often change.
If a user creates a service using a shared instance and sets a security group due to business needs, they should promptly check this page for synchronous updates in the security group.
If a user wants a fixed VIP while using the service, it is recommended to purchase a dedicated instance.
The private network IP ranges and public network VIPs in different regions are as follows:
Regions | Private IP Network Ranges (consistent across all regions) | Public Network VIPs | Scheduled Upgrade Time | Post-upgrade Public Network VIPs |
Guangzhou | 9.0.0.0/8,10.0.0.0/8,100.64.0.0/10,11.0.0.0/8,30.0.0.0/8 | 125.94.61.15,125.94.61.16,125.94.61.17,125.94.61.18,125.94.61.19,125.94.61.20,125.94.61.21,125.94.61.22,116.31.69.26,116.31.69.27,116.31.69.28,116.31.69.29,116.31.69.30,116.31.69.36,116.31.69.37,116.31.69.38,116.31.69.39,116.31.69.40 | February 2024 | Announced 5 days before the official upgrade |
Beijing | 9.0.0.0/8,10.0.0.0/8,100.64.0.0/10,11.0.0.0/8,30.0.0.0/8 | 123.206.35.235,123.206.35.236,123.206.35.237,123.206.35.238,123.206.35.239,123.206.35.240,123.206.35.241,123.206.35.242,123.206.35.243,123.206.35.244,123.206.35.245,123.206.35.246,123.206.35.247,123.206.35.248,123.206.35.249 | January 9, 2024 | Announced 5 days before the official upgrade |
Shanghai | 9.0.0.0/8,10.0.0.0/8,100.64.0.0/10,11.0.0.0/8,30.0.0.0/8 | 211.159.135.21,211.159.135.22,211.159.135.23,211.159.135.24,211.159.135.25,211.159.135.26,211.159.135.27,211.159.135.28,211.159.135.29,211.159.135.30 | January 23, 2024 | Announced 5 days before the official upgrade |
Hong Kong (China) | 9.0.0.0/8,10.0.0.0/8,100.64.0.0/10,11.0.0.0/8,30.0.0.0/8 | 123.206.35.245,123.206.35.246,123.206.35.247,123.206.35.248,123.206.35.249 | December 25, 2023 | 43.132.28.160, 43.132.29.187 43.132.31.114, 43.132.28.122 43.132.29.164, 43.132.31.45 |
Singapore | 9.0.0.0/8,10.0.0.0/8,100.64.0.0/10,11.0.0.0/8,30.0.0.0/8 | 119.28.123.219,119.28.123.220,119.28.123.221,119.28.123.222 | December 25, 2023 | 43.132.33.86, 43.132.34.18 43.132.32.215, 43.128.66.147 43.134.99.237, 150.109.16.225 |
Yes
No
Was this page helpful?