AWS EC2 Instances›Compute Optimized›c8in›c8in.96xlarge

Compared with Rackspace Spot

AWSRackspace Spot
Machinec8in.96xlarge24 × ch.vs1.2xlarge
vCPU384384
Memory768 GiB768 GiB
Local diskNoneNone
On-demand / hr$26.127$6.264
Spot / hr$9.390$0.984
Prices in US East, N. Virginia

Compute

vCPUs384
Memory768 GiB
Mem / vCPU2.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPSN/A
CoreMark / secN/A

Storage

TypeEBS only
Bandwidth120,000 Mbps
Throughput15000 MB/s
IOPS480,000
Base Bandwidth120,000 Mbps
Base Throughput15000 MB/s
Base IOPS480,000
Devices0
NVMe DriveNo
SSDNo
Swap PartitionNo

Networking

Performance600 Gigabit
Max ENIs24
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingNo
Branch Interface0
IPs / ENI64
Baseline Bandwidth300 Gbps

NUMA Architecture

Uses NUMANo
Node CountN/A
Max DistanceN/A
Cores / NodeN/A
Threads / NodeN/A
Memory / NodeN/A
L3 Cache / NodeN/A
L3 Cache SharedN/A

AWS Metadata

Instance typec8in.96xlarge
Full nameC8IN 96xlarge
FamilyCompute optimized
Variantc8in
GenerationCurrent
Bare MetalNo
EMR supportNo
DedicatedSupported
Introduced2026-04-16
Family sizes

c8in.96xlarge

AWS's c8in.96xlarge is a compute-optimized instance with 384 vCPU and 768 GiB. Rackspace Spot's largest server is 16 vCPU and 128 GiB, so matching this instance would take 24 × ch.vs1.2xlarge. That is arithmetically true and operationally absurd.

The Rackspace Spot column below prices that whole fleet, so read it as a scale reference rather than a drop-in replacement: at this size the useful question is what a shard of the workload costs, which is $0.041/hr per server.

Server comparison caveats
No single-node equivalent

The AWS c8in.96xlarge is 384 vCPU and 768 GiB. The largest comparable Rackspace Spot server is ch.vs1.2xlarge at 16 vCPU and 32 GiB, so matching it would take 24 of them. That maths works out, but 24 nodes is a redesign rather than a migration, because a single block of 768 GiB does not survive being split across a network.

If you chose c8in.96xlarge because the work genuinely needs 384 cores and 768 GiB together (an in-memory database, a large analytics engine, a single big solver), Rackspace Spot has no equivalent. What does fit is everything around it: the application servers, batch workers and CI that talk to that machine, which is usually the larger share of the bill.

Pricing by region

1 hr

Regions are Rackspace Spot locations.

RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace on-demandRackspace SpotOn-demand price savingsSpot price savings
US East, N. Virginia$26.127$9.390not offerednot offered$6.264$0.984
$19.863 (76%)
$8.406 (90%)
US Central, Chicagono AWS regionn/an/an/a$6.648$0.264n/an/a
US Central, Dallasno AWS regionn/an/an/a$6.600$3.144n/an/a
Hong Kongnot sold heren/an/an/a$6.480$0.264n/an/a
Sydney, Australia$34.111$3.639not offerednot offered$7.008$0.864
$27.103 (79%)
$2.775 (76%)
London, UKnot sold heren/an/an/a$6.216$0.984n/an/a
US West, San Josenot sold heren/an/an/a$6.240$0.048n/an/a
US Central, Dallas 2no AWS regionn/an/an/a$6.240$2.928n/an/a
US East, N. Virginia 2$26.127$9.390not offerednot offered$6.240$2.928
$19.887 (76%)
$6.462 (69%)

Prices updated 17 Nov 2026.

When to use it

Good for
  • ●Scientific modelling and simulation
  • ●Ad serving and real-time bidding
  • ●Game servers and matchmaking
  • ●Workloads that fit inside 768 GiB of RAM
  • ●Parallel work that can occupy 384 vCPU
  • ●Network-heavy services (AWS rates this size at 600 Gigabit)
Avoid if
  • ●The working set needs more than 768 GiB of RAM
  • ●You want a single-machine Rackspace Spot equivalent. At this size there is not one.
  • ●GPU or FPGA acceleration is needed
  • ●Memory-hungry applications. A memory-optimized family gives more RAM per dollar.
  • ●More than 2.00 GiB of RAM per vCPU is needed, since that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 384 vCPU would sit idle.
c8in.96xlarge is $19,073/mo on AWS on-demand. A single ch.vs1.2xlarge is $191/mo on Rackspace Spot on-demand. At this size the per-server price is the honest comparison.
  • Rackspace Spot sells spare capacity at market prices. It is the cheapest compute on the internet.
  • Prices are set by supply and demand. You pay what the market decides.
  • Compute is delivered as fully managed Kubernetes. All infrastructure is taken care of.
  • Egress costs $0.01/GB after the free allowance. AWS charges $0.09/GB.
Build your Cloudspace

Frequently asked questions

How much does c8in.96xlarge cost?

The AWS c8in.96xlarge costs $26.13/hr on-demand in US East (N. Virginia), about $19,073/mo running 24/7, or $9.39/hr at the AWS Spot price. On Rackspace Spot, 24 × ch.vs1.2xlarge is $6.26/hr on-demand, or $0.984/hr at the Spot price. Rackspace Spot also sells in Chicago and Dallas, where AWS operates no region at all, so those rows have no AWS price to compare against.

How much is c8in.96xlarge per month?

At 730 hours a month, c8in.96xlarge in US East (N. Virginia) is $19,073/mo on AWS on-demand, or $6,855/mo at the AWS Spot price. The same capacity on Rackspace Spot (24 × ch.vs1.2xlarge) is $4,573/mo on-demand, or $718/mo at the Spot price. Rackspace Spot prices move with demand, so the Spot figure is a typical rate rather than a fixed one.

Can I replace c8in.96xlarge with Rackspace Spot?

Not as a single machine. Rackspace Spot's largest VM shape is 16 vCPU and 128 GiB, so it would take 24 × ch.vs1.2xlarge to reach 384 vCPU and 768 GiB, and past roughly twenty nodes that stops being a credible substitution. Where the workload does shard (batch, web, queue consumers), a single ch.vs1.2xlarge at $0.041/hr is the number to compare against; the table's Rackspace Spot column prices the full 24-node fleet.

What is a cheaper alternative to c8in.96xlarge?

Rackspace Spot 24 × ch.vs1.2xlarge (384 vCPU, 768 GiB) is $4,573/mo on-demand or $718/mo at the Spot price, against $19,073/mo on-demand or $6,855/mo at the Spot price for c8in.96xlarge on AWS in US East (N. Virginia). The trade is real: Rackspace Spot capacity is priced by demand and can be reclaimed when demand rises, and workloads have to be containerized.