Each product’s availability is listed on its overview page. This table summarizes the availability for our major products using the following key:
◆ Full availability. All users can create this resource in this datacenter.
⬖Hover for more information. Limited availability. There may be limited capacity in this datacenter, or the product may be in an earlier phase of the product lifecycle.
◇Hover for more information. Future availablity. We intend to offer the product in this datacenter in the future. For example, we can expand availability when a product enters global availability. We’ll provide more information as we have it in the tooltips and in our release notes.
DigitalOcean’s datacenters are in the following locations:
This table lists each datacenter’s geographic location and its slug for use with the API and doctl.
| Datacenter | Geographic Location | Slug |
|---|---|---|
| NYC1 | New York City, United States | nyc1 |
| NYC2 | New York City, United States | nyc2 |
| NYC3 | New York City, United States | nyc3 |
| AMS2 | Amsterdam, the Netherlands | ams2 |
| AMS3 | Amsterdam, the Netherlands | ams3 |
| SFO1 | San Francisco, United States | sfo1 |
| SFO2 | San Francisco, United States | sfo2 |
| SFO3 | San Francisco, United States | sfo3 |
| SGP1 | Singapore | sgp1 |
| LON1 | London, United Kingdom | lon1 |
| FRA1 | Frankfurt, Germany | fra1 |
| TOR1 | Toronto, Canada | tor1 |
| BLR1 | Bangalore, India | blr1 |
Due to limited capacity in NYC2, AMS2, SFO1, and SFO2, only users who already have existing resources in those regions can create more resources there.
| Droplet Plans | NYC1 | NYC3 | AMS3 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 |
|---|---|---|---|---|---|---|---|---|---|
| Basic | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Premium Intel | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Premium AMD | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| CPU-Optimized | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Memory-Optimized | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Storage-Optimized | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Database Engine | NYC1 | NYC3 | AMS3 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 |
|---|---|---|---|---|---|---|---|---|---|
| PostgreSQL | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| MySQL | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Redis | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| MongoDB | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| MySQL Machine Type | NYC1 | NYC3 | AMS3 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 |
|---|---|---|---|---|---|---|---|---|---|
| Shared CPU | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | |||
| Storage-Optimized | ◆ | ◆ | ◆ | ⬖ "Low availability" | ◆ | ◆ | ◆ | ||
| Memory-Optimized |
| PostgreSQL Machine Type | NYC1 | NYC3 | AMS3 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 |
|---|---|---|---|---|---|---|---|---|---|
| Shared CPU | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | |||
| Storage-Optimized | ◆ | ◆ | ◆ | ⬖ "Low availability" | ◆ | ◆ | ◆ | ||
| Memory-Optimized |
| Redis Machine Type | NYC1 | NYC3 | AMS3 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 |
|---|---|---|---|---|---|---|---|---|---|
| Shared CPU | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | |||||||||
| Storage-Optimized | |||||||||
| Memory-Optimized | ◆ | ◆ | ◆ | ⬖ "Low availability" | ◆ | ◆ | ◆ |
| MongoDB Machine Type | NYC1 | NYC3 | AMS3 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 |
|---|---|---|---|---|---|---|---|---|---|
| Shared CPU | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | |||
| Storage-Optimized | ◆ | ◆ | ◆ | ⬖ "Low availability" | ◆ | ◆ | ◆ | ||
| Memory-Optimized |
Availability on App Platform is tracked at the regional level, not by datacenter.
The Cloudflare CDN caches static sites globally and only routes cache misses to the serving region.
| App Type | NYC | AMS | SFO | SGP | LON | FRA | TOR | BLR |
|---|---|---|---|---|---|---|---|---|
| Dynamic | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Static Site | ◆ | ◆ | ◆ | ⬖ Cloudflare CDN only | ⬖ Cloudflare CDN only | ◆ | ⬖ Cloudflare CDN only | ⬖ Cloudflare CDN only |
| Product | NYC1 | NYC3 | AMS3 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 |
|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Volumes | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Spaces | ◆ | ◆ | ◆ | ◆ | ◆ | ||||
| Load Balancers | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Container Registry | ◆ | ◆ | ◆ | ◆ | ◆ |
Many of our products and features are designed to work with Droplets, and are available in the same regions that Droplets are. These Droplet-specific resources can have different levels of regional compatibility:
All regions. Region specific. Works with Droplets in all datacenters.
Same region only. Region specific. Works with Droplets in the same datacenter.
Region agnostic. Not region specific, so you don’t choose a datacenter when you create or use these resources. Works with Droplets in all datacenters.
The overview page of each product and feature details its regional compatibility. The following table summarizes:
| Droplets in All Regions | Droplets in the Same Region Only | Region Agnostic |
|---|---|---|
| 1-Click Applications | Backups (to create Droplets) | DNS |
| Snapshots | Floating IPs | Cloud Firewalls |
| Backups (to enable) | Load Balancers | Tags |
| Custom Images | VPC | |
| Load Balancers | ||
| IPv6 | ||
| Monitoring |
General Purpose Droplets are now available in BLR1.
App Platform is now available in TOR1 and LON1.
Storage-Optimized Droplets are now available in SGP1.
For more information, see the full release notes.