Regional Availability
Available Datacenters
We have datacenters across 9 regions. A region is a geographic area where we have one or more datacenters.
This table lists each datacenter, its region, and its slug for use with the API and doctl:
| Datacenter | Region | Slug |
|---|---|---|
| NYC1 | New York City, United States | nyc1 |
| NYC3 | New York City, United States | nyc3 |
| AMS3 | Amsterdam, the Netherlands | ams3 |
| 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 |
| SYD1 | Sydney, Australia | syd1 |
Legacy Datacenters
We additionally have several legacy datacenters, which are AMS2, NYC2, and SFO1. We have restricted resource creation in legacy datacenters because there is no remaining physical space to expand within those datacenters. Users who have existing Droplets in these datacenters can continue to create additional Droplets there, but we strongly recommend using another datacenter in the same geographical region, like AMS3, NYC3 or SFO3.
Product Availability
The tables below summarize availability for our 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 a tooltip with more information.
-
◇Hover for more information. Future availability. We intend to offer the product in this datacenter in the future, but don’t currently. Hover for a tooltip with more information.
Droplets
| Droplet Plans | NYC1 | NYC3 | AMS3 | SFO2 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 | SYD1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Basic (Regular CPU) | ◆ | ⬖ $4 plan is not available. | ◆ | ◆ | ◆ | ◆ | ⬖ $4 plan is not available. | ◆ | ⬖ $4 plan is not available. | ⬖ $4 plan is not available. | ◆ |
| Basic (Premium CPU) | ⬖ Plans with a 1:4 vCPU:RAM ratio are not yet available. | ◆ | ◆ | ◆ | ⬖ Plans with a 1:4 vCPU:RAM ratio are not yet available. | ⬖ Plans with a 1:4 vCPU:RAM ratio are not yet available. | ◆ | ◆ | ◆ | ◆ | |
| General Purpose (Regular CPU) | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose (Premium CPU) | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ||
| CPU-Optimized (Regular CPU) | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| CPU-Optimized (Premium CPU) | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ||
| Memory-Optimized (Regular CPU) | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Memory-Optimized (Premium CPU) | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ||||
| Storage-Optimized (Regular CPU) | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Storage-Optimized (Premium CPU) | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
Droplet Backups
| Droplet Backups | NYC1 | NYC3 | AMS3 | SFO2 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 | SYD1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Weekly | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Daily | ⬖ Early Availability | ⬖ Early Availability | ⬖ Early Availability | ⬖ Early Availability | ⬖ Early Availability | ⬖ Early Availability | ⬖ Early Availability | ⬖ Early Availability |
Managed Databases
| Database Engine | NYC1 | NYC3 | AMS3 | SFO2 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 | SYD1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| PostgreSQL | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| MySQL | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Redis | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| MongoDB | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
Managed Database Machine Types
| MySQL Machine Type | NYC1 | NYC3 | AMS3 | SFO2 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 | SYD1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Shared CPU | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Storage-Optimized | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Memory-Optimized |
| PostgreSQL Machine Type | NYC1 | NYC3 | AMS3 | SFO2 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 | SYD1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Shared CPU | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Storage-Optimized | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Memory-Optimized |
| Redis Machine Type | NYC1 | NYC3 | AMS3 | SFO2 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 | SYD1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Shared CPU | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | |||||||||||
| Storage-Optimized | |||||||||||
| Memory-Optimized | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| MongoDB Machine Type | NYC1 | NYC3 | AMS3 | SFO2 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 | SYD1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Shared CPU | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Storage-Optimized | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Memory-Optimized |
| Kafka Machine Type | NYC1 | NYC3 | AMS3 | SFO2 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 | SYD1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Shared CPU | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| General Purpose | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Storage-Optimized | |||||||||||
| Memory-Optimized |
App Platform
Availability on App Platform is by region, 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 | SYD |
|---|---|---|---|---|---|---|---|---|---|
| Dynamic | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Static Site | ◆ | ◆ | ◆ | ⬖ Cloudflare CDN only | ⬖ Cloudflare CDN only | ◆ | ⬖ Cloudflare CDN only | ⬖ Cloudflare CDN only | ◆ |
Other Products
| Product | NYC1 | NYC3 | AMS3 | SFO2 | SFO3 | SGP1 | LON1 | FRA1 | TOR1 | BLR1 | SYD1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Volumes | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Spaces | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | |||
| Load Balancers | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
| Container Registry | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ||||
| Functions | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ | ◆ |
Datacenter Compatibility for Droplet-Specific Resources
Many of our products and features are designed to work with Droplets, and are available in the same datacenters that Droplets are. These Droplet-specific resources can have different levels of compatibility:
-
All datacenters. Datacenter-specific. Works with Droplets in all datacenters.
-
Same datacenter only. Datacenter-specific. Works with Droplets in the same datacenter.
-
Datacenter agnostic. Not datacenter 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 datacenter compatibility. The following table summarizes:
| Droplets in All Datacenters | Droplets in the Same Datacenter Only | Datacenter Agnostic |
|---|---|---|
| 1-Click Applications | Backups (to create Droplets) | DNS |
| Snapshots | Reserved IPs | Cloud Firewalls |
| Custom Images | Load Balancers | Tags |
| IPv6 | VPC | |
| Monitoring |
Paperspace
Paperspace currently has three datacenter regions:
| Region Name | Country | Location |
|---|---|---|
| NY2 | United States | Near New York City |
| CA1 | United States | Near Santa Clara |
| AMS1 | The Netherlands | Near Amsterdam |
We are in the process of expanding our global coverage. Follow the Paperspace Changelog for updates. View the status of our regions on the Paperspace status page.
Paperspace products are available in the following regions:
| Product | Regions |
|---|---|
| Machines | NY2, CA1, AMS1 |
| Notebooks | NY2 |
| Deployments | NY2 |
| Workflows | NY2 |
You can test latency to Paperspace datacenters with conventional tools, like ping and traceroute.