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)

S2P/S3P Optimized Destinations

Sometimes local eyeball networks charge a premium for traffic to reach their network without congestion. Since the cost of transit is a major factor in our pricing, and we can't offer it for free or at a discount, users can choose to use our S2P offerings for a better network experience at a higher cost.

We may move networks from the S2P list to the S2N list when the cost of transit becomes more reasonable.

The following networks are optimized for S2P instances:

• AS4134 China Telecom (from HKG12, SIN03, NRT04 and SJC10)
• AS4837 China Unicom (from HKG12, SIN03, NRT04 and SJC10)
• AS9808 China Mobile (from HKG12, SIN03, NRT04 and SJC10)
• AS7473 Singtel (from SIN03)
• AS3320 Deutsche Telekom (from BER)

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

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.

Additional Services

VXC

Virtual Cross-Connect (VXC) is a service that allows you to connect your Misaka.io private network to third-party networks (e.g. AWS, Azure, GCP, etc.) or your own datacenter.

This service is provided through Console Connect. Please reach out to our support team for more information.

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	✅	❌	✅	❌	✅