Services
IaaS
Regions

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)

S2P/S3P Optimized Destinations

Sometimes local eyeball networks (opens in a new tab) 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)

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 (opens in a new tab). Please reach out to our support team for more information.

Core Regions

CodeLocationDatacenterVXCS3NS2NS2PS2C
IAD01Ashburn, VirginiaEquinix DC10
LAX02Los Angeles, CaliforniaCoreSite LA2
LAX07Los Angeles, CaliforniaWest 7 Center
SJC10San Jose, CaliforniaEquinix SV10
FMT02Fremont, CaliforniaHurricane Electric FMT2
EWR02Secaucus, New JerseyEquinix NY2
MIA02Miami, FloridaColoHouse MI
MCI01North Kansas City, Missouri1530 Swift
AMS05Amsterdam, NetherlandsEquinix AM5
LON07London, United KingdomDocklands Data Centre
BER02Berlin, GermanySpeedbone
MOW01Moscow, RussiaMMTS-9
HKG12Hong KongEquinix HK2
NRT04Tokyo, JapanEquinix TY8
SIN03SingaporeEquinix SG3
TPE01TaipeiChief LY
JNB01Johannesburg, South AfricaTeraco JB1