Regions

Overview

Instance Types

S2N

Standard NVMe (Gen2)

• Shared Latest Generations Intel CPU or AMD EPYC Rome (2nd Gen) CPU
• RAID1 / RAID10 NVMe Storage
• Network Throughput Limit 10Gbps

S3N

Standard NVMe (Gen3, EPYC)

• Shared AMD EPYC Milan (3rd Gen) CPU
• RAID1 / RAID10 NVMe Storage
• Network Throughput Limit 10Gbps

S2P

Standard NVMe (Gen2, WAN Latency Optimized)

• Shared Latest Generations Intel CPU or AMD EPYC Rome (2nd Gen) CPU
• RAID1 / RAID10 NVMe Storage
• Network Throughput Limit 10Gbps (1Gbps to optimized destinations)

S3P

Standard NVMe (Gen3, WAN Latency Optimized)

• Shared AMD EPYC Milan (3rd Gen) CPU
• RAID1 / RAID10 NVMe Storage
• Network Throughput Limit 10Gbps (1Gbps to optimized destinations)

S2C

Standard NVMe w/ CN2 (Gen2)

• Shared Latest Generations Intel CPU or AMD EPYC Rome (2nd Gen) CPU
• RAID1 / RAID10 NVMe Storage
• Network Throughput Limit 10Gbps (600Mbps to the listed networks below)

S4P

Standard NVMe (Gen4, WAN Latency Optimized)

• Shared AMD EPYC Genoa (4th Gen) CPU
• RAID1 / RAID10 NVMe Storage
• Network Throughput Limit 10Gbps (1Gbps to optimized destinations)

S4H

Standard NVMe (Gen4, High Frequency)

• Shared AMD Ryzen Gen-4 High Frequency CPU (Can be Ryzen 7900, EPYC 4464P,4465P)
• RAID1 / RAID10 NVMe Storage
• Network Throughput Limit 10Gbps

Routing Profiles

See Routing Profiles for the full routing profile matrix.

S2C/S3C Optimized Destinations

The following networks are optimized for S2C instances:

• AS4134 China Telecom
• AS4837 China Unicom
• AS9808 China Mobile

Note: Only egress traffic to the above networks is optimized. Ingress traffic from the above networks may still go through the normal IP transit blend

Difference between S2C/S3C and S2P/S3P

You may see that we provide both S2C/S3C and S2P/S3P offerings at the same location.

The difference is that S2C/S3C will always use CN2 (China Telecom) for optimized destinations no matter if how bad the performance is, while S2P/S3P will use alternative routes if the performance is suboptimal.

Core Regions

Code	Location	Datacenter	VXC	S3N	S2N	S2P	S2C
IAD01	Ashburn, Virginia	Equinix DC10	✅	❌	✅	❌	❌
LAX02	Los Angeles, California	CoreSite LA2	❌	✅	❌	❌	❌
LAX07	Los Angeles, California	West 7 Center	❌	✅	❌	❌	❌
SJC10	San Jose, California	Equinix SV10	❌	❌	✅	❌	❌
FMT02	Fremont, California	Hurricane Electric FMT2	❌	❌	✅	❌	❌
EWR02	Secaucus, New Jersey	Equinix NY2	❌	❌	✅	❌	❌
MIA02	Miami, Florida	ColoHouse MI	❌	❌	✅	❌	❌
MCI01	North Kansas City, Missouri	1530 Swift	❌	❌	✅	❌	❌
AMS05	Amsterdam, Netherlands	Equinix AM5	❌	❌	✅	❌	❌
LON07	London, United Kingdom	Docklands Data Centre	❌	❌	✅	❌	❌
BER02	Berlin, Germany	Speedbone	❌	❌	✅	❌	✅
MOW01	Moscow, Russia	MMTS-9	❌	❌	✅	❌	✅
HKG12	Hong Kong	Equinix HK2	✅	✅	❌	❌	❌
NRT04	Tokyo, Japan	Equinix TY8	❌	✅	❌	❌	❌
SIN03	Singapore	Equinix SG3	✅	✅	❌	❌	❌
TPE01	Taipei	Chief LY	❌	✅	❌	❌	❌
JNB01	Johannesburg, South Africa	Teraco JB1	✅	❌	✅	❌	✅