Object Storage Service (OSS) is deployed across multiple regions worldwide. Each region offers different types of endpoints, such as public, internal, and dual-stack endpoints. The following tables list the endpoints and internal virtual IP address (VIP) CIDR blocks for each region for your reference. For more information about the scenarios and usage of each endpoint type, see Access OSS through endpoints and bucket domain names.
When you use an OSS endpoint to access files such as HTML files and images, the files are downloaded instead of being previewed online in your browser. To preview files online, access OSS using a custom domain name.
Public cloud
Suitable for most business scenarios and available in multiple regions worldwide.
Due to a policy change to improve compliance and security, starting March 20, 2025, new OSS users must use a custom domain name (CNAME) to perform data API operations on OSS buckets located in Chinese mainland regions. Default public endpoints are restricted for these operations. Refer to the official announcement for a complete list of the affected operations. If you access your data via HTTPS, you must bind a valid SSL Certificate to your custom domain. This is mandatory for OSS Console access, as the console enforces HTTPS.
Asia-Pacific - China
Region | Region ID | Public endpoint | Internal endpoint | Dual-stack endpoint | Internal VIP CIDR blocks |
China (Hangzhou) | cn-hangzhou | oss-cn-hangzhou.aliyuncs.com | oss-cn-hangzhou-internal.aliyuncs.com | cn-hangzhou.oss.aliyuncs.com | 100.118.28.0/24 100.114.102.0/24 100.98.170.0/24 100.118.31.0/24 |
China (Shanghai) | cn-shanghai | oss-cn-shanghai.aliyuncs.com | oss-cn-shanghai-internal.aliyuncs.com | cn-shanghai.oss.aliyuncs.com | 100.98.35.0/24 100.98.110.0/24 100.98.169.0/24 100.118.102.0/24 |
China (Nanjing - Local Region) Closing Down | cn-nanjing | oss-cn-nanjing.aliyuncs.com | oss-cn-nanjing-internal.aliyuncs.com | 100.114.142.0/24 | |
China (Qingdao) | cn-qingdao | oss-cn-qingdao.aliyuncs.com | oss-cn-qingdao-internal.aliyuncs.com | cn-qingdao.oss.aliyuncs.com | 100.115.173.0/24 100.99.113.0/24 100.99.114.0/24 100.99.115.0/24 |
China (Beijing) | cn-beijing | oss-cn-beijing.aliyuncs.com | oss-cn-beijing-internal.aliyuncs.com | cn-beijing.oss.aliyuncs.com | 100.118.58.0/24 100.118.167.0/24 100.118.170.0/24 100.118.171.0/24 100.118.172.0/24 100.118.173.0/24 |
China (Zhangjiakou) | cn-zhangjiakou | oss-cn-zhangjiakou.aliyuncs.com | oss-cn-zhangjiakou-internal.aliyuncs.com | cn-zhangjiakou.oss.aliyuncs.com | 100.118.90.0/24 100.98.159.0/24 100.114.0.0/24 100.114.1.0/24 |
China (Hohhot) | cn-huhehaote | oss-cn-huhehaote.aliyuncs.com | oss-cn-huhehaote-internal.aliyuncs.com | cn-huhehaote.oss.aliyuncs.com | 100.118.195.0/24 100.99.110.0/24 100.99.111.0/24 100.99.112.0/24 |
China (Ulanqab) | cn-wulanchabu | oss-cn-wulanchabu.aliyuncs.com | oss-cn-wulanchabu-internal.aliyuncs.com | cn-wulanchabu.oss.aliyuncs.com | 100.114.11.0/24 100.114.12.0/24 100.114.100.0/24 100.118.214.0/24 |
China (Shenzhen) | cn-shenzhen | oss-cn-shenzhen.aliyuncs.com | oss-cn-shenzhen-internal.aliyuncs.com | cn-shenzhen.oss.aliyuncs.com | 100.118.78.0/24 100.118.203.0/24 100.118.204.0/24 100.118.217.0/24 |
China (Heyuan) | cn-heyuan | oss-cn-heyuan.aliyuncs.com | oss-cn-heyuan-internal.aliyuncs.com | cn-heyuan.oss.aliyuncs.com | 100.98.83.0/24 100.118.174.0/24 |
China (Guangzhou) | cn-guangzhou | oss-cn-guangzhou.aliyuncs.com | oss-cn-guangzhou-internal.aliyuncs.com | cn-guangzhou.oss.aliyuncs.com | 100.115.33.0/24 100.114.101.0/24 |
China (Chengdu) | cn-chengdu | oss-cn-chengdu.aliyuncs.com | oss-cn-chengdu-internal.aliyuncs.com | cn-chengdu.oss.aliyuncs.com | 100.115.155.0/24 100.99.107.0/24 100.99.108.0/24 100.99.109.0/24 |
China (Hong Kong) | cn-hongkong | oss-cn-hongkong.aliyuncs.com | oss-cn-hongkong-internal.aliyuncs.com | cn-hongkong.oss.aliyuncs.com | 100.115.61.0/24 100.99.103.0/24 100.99.104.0/24 100.99.106.0/24 |
Asia-Pacific - Other
Region | Region ID | Public endpoint | Internal endpoint | Dual-stack endpoint | Internal VIP CIDR blocks |
Japan (Tokyo) | ap-northeast-1 | oss-ap-northeast-1.aliyuncs.com | oss-ap-northeast-1-internal.aliyuncs.com | 100.114.211.0/24 100.114.114.0/25 | |
South Korea (Seoul) | ap-northeast-2 | oss-ap-northeast-2.aliyuncs.com | oss-ap-northeast-2-internal.aliyuncs.com | 100.99.119.0/24 | |
Singapore | ap-southeast-1 | oss-ap-southeast-1.aliyuncs.com | oss-ap-southeast-1-internal.aliyuncs.com | 100.118.219.0/24 100.99.213.0/24 100.99.116.0/24 100.99.117.0/24 | |
Malaysia (Kuala Lumpur) | ap-southeast-3 | oss-ap-southeast-3.aliyuncs.com | oss-ap-southeast-3-internal.aliyuncs.com | 100.118.165.0/24 100.99.125.0/24 100.99.130.0/24 100.99.131.0/24 | |
Indonesia (Jakarta) | ap-southeast-5 | oss-ap-southeast-5.aliyuncs.com | oss-ap-southeast-5-internal.aliyuncs.com | 100.114.98.0/24 | |
Philippines (Manila) | ap-southeast-6 | oss-ap-southeast-6.aliyuncs.com | oss-ap-southeast-6-internal.aliyuncs.com | 100.115.16.0/24 | |
Thailand (Bangkok) | ap-southeast-7 | oss-ap-southeast-7.aliyuncs.com | oss-ap-southeast-7-internal.aliyuncs.com | 100.98.249.0/24 |
Europe and Americas
Region | Region ID | Public endpoint | Internal endpoint | Dual-stack endpoint | Internal VIP CIDR blocks |
Germany (Frankfurt) | eu-central-1 | oss-eu-central-1.aliyuncs.com | oss-eu-central-1-internal.aliyuncs.com | eu-central-1.oss.aliyuncs.com | 100.115.154.0/24 |
UK (London) | eu-west-1 | oss-eu-west-1.aliyuncs.com | oss-eu-west-1-internal.aliyuncs.com | 100.114.114.128/25 | |
US (Silicon Valley) | us-west-1 | oss-us-west-1.aliyuncs.com | oss-us-west-1-internal.aliyuncs.com | 100.115.107.0/24 | |
US (Virginia) | us-east-1 | oss-us-east-1.aliyuncs.com | oss-us-east-1-internal.aliyuncs.com | 100.115.60.0/24 100.99.100.0/24 100.99.101.0/24 100.99.102.0/24 | |
Mexico | na-south-1 | oss-na-south-1.aliyuncs.com | oss-na-south-1-internal.aliyuncs.com | 100.115.112.0/27 |
Middle East
Region | Region ID | Public endpoint | Internal endpoint | Dual-stack endpoint | Internal VIP CIDR blocks |
UAE (Dubai) | me-east-1 | oss-me-east-1.aliyuncs.com | oss-me-east-1-internal.aliyuncs.com | 100.99.235.0/24 | |
SAU (Riyadh - Partner Region) | me-central-1 | oss-me-central-1.aliyuncs.com | oss-me-central-1-internal.aliyuncs.com | 100.99.121.0/24 |
FAQ
How do I select a region?
Consider the following factors when selecting a region:
Geographic proximity: To reduce network latency and improve the access experience, choose the region closest to your primary users or applications.
Connectivity with other Alibaba Cloud services: When your other Alibaba Cloud services and OSS are in the same region, they can communicate over the internal network. This eliminates public network traffic fees.
Cost considerations: Product prices and discount policies vary by region. For more information, see OSS Pricing.
Compliance requirements: Different regions and industries have different data compliance requirements. Select a region that meets the compliance requirements of your business.
Product features: New features are often released for public preview in specific regions. To use the latest features, create a bucket in a supported region. For more information, see Release notes.
You can use the curl command to test the access latency from your on-premises network to OSS endpoints in different regions. This helps you select a region. Lower values for time_connect and time_starttransfer usually indicate better network quality.
curl -o /dev/null -s -w "Connect: %{time_connect}s\nStart Transfer: %{time_starttransfer}s\nTotal: %{time_total}s\n" "https://oss-<region-id>.aliyuncs.com"Why do the names of regions outside the Chinese mainland appear inconsistent on different pages?
The names of some regions outside the Chinese mainland may differ between the OSS pricing page and the resource plan purchase page. However, these different names refer to the same physical location. For example, the US (Silicon Valley) region may be displayed as US West 1 or US West. For more information, see Object Storage Service pricing or Purchase a resource plan.
What should I do if I experience high latency or unstable connections when I access OSS across borders?
Cross-border long-distance data transfer, such as accessing nodes in Hong Kong (China) or Singapore from the Chinese mainland, involves long-distance public Internet links and multiple ISP interconnection nodes. Access may experience high latency or unstable connections due to objective factors such as physical distance, routing complexity, and public network congestion.
Core suggestion: Follow the "deploy nearby" principle
Deploy in the same region (recommended): Plan your business applications, such as ECS instances and container services, in the same region as your OSS buckets. Within the same region, traffic is transmitted over the high-speed internal network of Alibaba Cloud and is not affected by public network or cross-border links.
Avoid unnecessary direct cross-border connections: For core production services, avoid direct read and write operations over long distances across the public Internet. Migrating your entire business to the region where your data is stored is the most effective way to eliminate network fluctuations at the architectural level.
Solution: Use transfer acceleration
If you have a small number of unavoidable long-distance cross-border access requests for scenarios such as global business distribution or disaster recovery and backup, we recommend that you use the OSS transfer acceleration feature. For more information, see Access OSS using transfer acceleration.