OSS is deployed across multiple regions worldwide. Each region provides public, internal, and dual-stack endpoints. The tables below list the endpoints and VIP CIDR blocks for each region. For details on when and how to use each endpoint type, see Access OSS using bucket domain names.
When you access HTML files, images, or other content via OSS-provided domain names, browsers trigger a download rather than rendering them inline. To enable inline preview, Access OSS through a custom domain name.
Public cloud
Supports most workloads across multiple global regions.
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 | VIP CIDR block |
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 regions
Region | Region ID | Public endpoint | Internal endpoint | Dual-stack endpoint | VIP CIDR block |
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 | VIP CIDR block |
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 | VIP CIDR block |
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 choose a region?
Consider these factors when selecting a region:
Proximity: Choose the region closest to your primary users or applications to minimize latency and improve performance.
Run in the same region: When other Alibaba Cloud products and your OSS bucket are in the same region, they communicate over the internal network, which eliminates internet traffic charges.
Cost: Pricing and promotions vary by region. For details, see Object Storage Service pricing.
Compliance: Data residency and compliance requirements vary by region and industry. Choose a region that meets your regulatory obligations.
Feature availability: New features typically launch in select regions first. To use the latest features, create your bucket in a supported region. For details, see Release notes for OSS features.
To measure latency between your network and OSS endpoints across regions, run the following curl command. Lower time_connect and time_starttransfer values indicate better network performance.
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 overseas region names appear differently across pages?
Some overseas region names may differ between the OSS pricing page and the resource plan purchase page, but both refer to the same region. For example, the US (Silicon Valley) region may appear as "US West 1" or "US West" depending on the page. For more information, see Object Storage Service pricing or purchase a resource plan.
What should I do if cross-border OSS access is slow or unstable?
Long-distance cross-border transfers travel over extended public internet paths through multiple network hops. Physical distance, routing complexity, and public network congestion can all cause high latency or unstable connections.
Deploy close to your data
Same-region deployment (preferred): Place your applications (such as ECS instances or container services) in the same region as your OSS bucket. Traffic within the same region flows over Alibaba Cloud's high-speed internal network, bypassing public internet and cross-border links entirely.
Avoid unnecessary cross-border access: For core production workloads, avoid long-distance cross-border reads and writes over the public internet. Migrating your application stack to the region where your data resides is the most effective way to eliminate network instability.
Use Transfer Acceleration
If cross-border access is unavoidable for your use case — such as global content distribution or cross-region disaster recovery — enable OSS Transfer Acceleration. For details, see Access OSS using transfer acceleration.