Object Storage Service (OSS) is available in multiple regions worldwide. Each region provides different endpoint types, such as public network, internal network, and dual-stack. The following tables list the endpoints and internal VIP CIDR blocks for each region. To learn about the use cases and access methods for each endpoint type, see Access OSS using endpoints and bucket domain names.
When you use an OSS access domain, browsers download files such as HTML and images instead of displaying them inline. To preview these files inline, access OSS using a custom domain name.
Public cloud
Ideal for most use cases and available in 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 - Chinese mainland
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 (Zhongwei) | cn-zhongwei | oss-cn-zhongwei.aliyuncs.com | oss-cn-zhongwei-internal.aliyuncs.com | 100.115.157.0/27 | |
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 regions
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 | |
Malaysia (Johor) | ap-southeast-8 | oss-ap-southeast-8.aliyuncs.com | oss-ap-southeast-8-internal.aliyuncs.com | 100.115.157.0/27 |
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 | |
France (Paris) | eu-west-2 | oss-eu-west-2.aliyuncs.com | oss-eu-west-2-internal.aliyuncs.com | 100.115.159.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 | |
Saudi Arabia (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 choose a region?
When choosing a region, consider the following factors:
Proximity: Choose the region that is geographically closest to your primary users or applications. This can reduce network latency and improve access performance.
Interconnection with other cloud products: If your other cloud products and OSS are in the same region, they can communicate over the internal network, which eliminates public traffic costs.
Cost: Pricing and discounts vary by region. For more information, see OSS Pricing.
Compliance: Data compliance requirements can vary by region and industry. Choose a region that meets your business's regulatory needs.
Feature availability: New features are often released for public preview in specific regions. To use the latest features, you may need to create a bucket in one of these regions. For details, see Release notes for new features.
You can use the curl command to test the access latency from your local network to OSS endpoints in different regions. This helps you choose the best region. Lower values for time_connect and time_starttransfer typically 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"Region name inconsistencies
The names of some regions outside the Chinese mainland may appear differently on pages such as the OSS pricing page and the resource plan purchase page. However, these names refer to the same physical location. For example, the US (Silicon Valley) region may appear as US West 1 or US West on different pages. For more information, see Object Storage Service pricing or Purchase a resource plan.
High latency or instability in cross-border access
Cross-border data transfers over long distances, such as accessing nodes in China (Hong Kong) or Singapore from the Chinese mainland, travel over the public internet. This path involves multiple carrier networks and is affected by factors such as physical distance, routing complexity, and public internet congestion. As a result, you may experience high latency or unstable connections.
Best practice: Co-locate resources
Deploy in the same region (Recommended): Deploy your applications, such as ECS instances and Container Service clusters, in the same region as your OSS buckets. Within the same region, traffic travels over Alibaba Cloud's high-speed internal network and is unaffected by the public internet or cross-border network issues.
Avoid unnecessary cross-border connections: For core production workloads, avoid direct read and write operations over the public internet across long distances whenever possible. Migrating your entire application to the region where your data is stored is the most effective way to eliminate network instability.
Solution: Use Transfer Acceleration
If your use case, such as global content distribution or off-site disaster recovery, requires unavoidable cross-border data transfers, we recommend using the OSS Transfer Acceleration feature for this portion of your traffic. For more information, see Access OSS by using Transfer Acceleration.