Price floor Every GPU at least 30% below the market median — re-checked against the marketplace weekly.

See the proof

Language

Launch a GPU

Service status · all times UTC

All systems operational

Updated 13:21:06 · refreshes every 90 s · this page is served from the same stack it reports on — machine-readable at /status.json.

  • 99.96%90-day uptime, all components
  • 1,941GPUs online right now
  • 0active incidents
  • 2maintenance windows scheduled

Components

Current state and the last 90 days, one cell per day. Hover a cell for the date.

operational degraded outage

Console & websitecloud.lowcostgpu.com and lowcostgpu.com
99.95% Operational
REST API/v1 — offers, instances, balance
99.94% Operational
Provisioningdeploys, start/stop, image cache
99.97% Operational
Network edgeinstance hostnames, TLS, port maps
99.98% Operational
Storage fabricinstance NVMe and network volumes
99.94% Operational
Paymentscrypto top-ups and confirmation tracking
99.97% Operational

Live metrics — last 24 hours

Fleet-wide medians, one point every 15 minutes.

API latency p50, ms

46 ms now · avg 46

min 42 · max 50 ms

Deploy time p50, seconds to running

27.3 s now · avg 27.0

min 24.1 · max 30.0 s

GPUs online fleet-wide

1,941 now · avg 1,941

min 1,911 · max 1,970

Regions

Per-region state, GPUs accepting deploys, API latency from the region's edge, and the last 30 days.

North America 10 regions

RegionStatusGPUsLatency30 days
US Ashburn, VAus-east-1 Operational 111 34 ms 100.00%
US New York, NYus-east-2 Operational 61 36 ms 99.95%
US Chicago, ILus-central-1 Operational 98 39 ms 100.00%
US Dallas, TXus-central-2 Operational 82 43 ms 100.00%
US Los Angeles, CAus-west-1 Operational 73 40 ms 99.91%
US Seattle, WAus-west-2 Operational 67 42 ms 100.00%
US Miami, FLus-south-1 Operational 39 33 ms 100.00%
CA Montréalca-east-1 Operational 94 38 ms 100.00%
CA Vancouverca-west-1 Operational 21 33 ms 100.00%
MX Querétaromx-central-1 Operational 54 35 ms 100.00%

Europe 10 regions

RegionStatusGPUsLatency30 days
NL Amsterdameu-west-1 Operational 50 37 ms 100.00%
GB Londoneu-west-2 Operational 80 39 ms 100.00%
FR Pariseu-west-3 Operational 38 40 ms 100.00%
DE Frankfurteu-central-1 Operational 84 40 ms 100.00%
PL Warsaweu-central-2 Operational 69 36 ms 100.00%
SE Stockholmeu-north-1 Operational 104 41 ms 100.00%
FI Helsinkieu-north-2 Operational 25 47 ms 100.00%
IT Milaneu-south-1 Operational 35 35 ms 100.00%
ES Madrideu-south-2 Operational 54 41 ms 100.00%
RO Bucharesteu-east-1 Operational 32 43 ms 100.00%

Asia-Pacific 7 regions

RegionStatusGPUsLatency30 days
JP Tokyoap-northeast-1 Operational 77 54 ms 100.00%
KR Seoulap-northeast-2 Operational 57 62 ms 100.00%
JP Osakaap-northeast-3 Operational 47 60 ms 100.00%
SG Singaporeap-southeast-1 Operational 88 54 ms 100.00%
AU Sydneyap-southeast-2 Operational 49 63 ms 99.95%
ID Jakartaap-southeast-3 Operational 41 60 ms 100.00%
IN Mumbaiap-south-1 Operational 103 72 ms 100.00%

South America 2 regions

RegionStatusGPUsLatency30 days
BR São Paulosa-east-1 Operational 49 83 ms 100.00%
CL Santiagosa-west-1 Operational 24 71 ms 100.00%

Middle East & Africa 3 regions

RegionStatusGPUsLatency30 days
AE Dubaime-central-1 Operational 48 72 ms 100.00%
ZA Johannesburgaf-south-1 Operational 53 74 ms 100.00%
IL Tel Avivil-central-1 Operational 34 69 ms 100.00%

SLA reference: 99.9% monthly on on-demand and reserved — credit schedule.

Scheduled maintenance

Announced at least 72 hours ahead. Running instances are never restarted for maintenance.

Under maintenance Storage fabric firmware update CL Santiago

2026-10-22 02:00 UTC → 04:00 UTC (2 h window)

Live migration of volumes to updated nodes. No instance restarts expected; volume I/O may briefly slow.

Under maintenance Storage fabric firmware update IN Mumbai

2026-10-24 02:00 UTC → 04:00 UTC (2 h window)

Live migration of volumes to updated nodes. No instance restarts expected; volume I/O may briefly slow.

Incident history — last 90 days

Every incident with customer impact, newest first, with its full timeline. Transparency beats a wall of green.

October 2026 10

Degraded Packet loss on the Sydney edge Network edge AU Sydney · 13 min · Resolved
  1. 02:42Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 02:17Monitoring — A fix has been applied and we are monitoring the results.
  3. 02:08Identified — Root cause identified and a fix is being applied.
  4. 02:04Investigating — We are investigating packet loss on the Sydney edge. Running instances are not affected.
Degraded Degraded volume throughput in New York, NY Storage fabric US New York, NY · 30 min · Resolved
  1. 12:37Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 12:12Monitoring — A fix has been applied and we are monitoring the results.
  3. 11:52Identified — Root cause identified and a fix is being applied.
  4. 11:42Investigating — We are investigating degraded volume throughput in New York, NY. Running instances are not affected.
Degraded Slow instance deploys in Frankfurt Provisioning · 43 min · Resolved
  1. 21:03Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 20:38Monitoring — A fix has been applied and we are monitoring the results.
  3. 20:10Identified — Root cause identified: image-cache pressure on a subset of hosts. Deploys are being rebalanced.
  4. 19:55Investigating — We are investigating slow instance deploys in Frankfurt. Running instances are not affected.
Degraded Delayed on-chain confirmation tracking Payments · 46 min · Resolved
  1. 05:51Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 05:26Monitoring — A fix has been applied and we are monitoring the results.
  3. 04:56Identified — Root cause identified: upstream network confirmation delays. Credits apply automatically once transactions confirm.
  4. 04:40Investigating — We are investigating delayed on-chain confirmation tracking. Running instances are not affected.
Degraded Degraded volume throughput in Los Angeles, CA Storage fabric US Los Angeles, CA · 35 min · Resolved
  1. 15:34Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 15:09Monitoring — A fix has been applied and we are monitoring the results.
  3. 14:46Identified — Root cause identified and a fix is being applied.
  4. 14:34Investigating — We are investigating degraded volume throughput in Los Angeles, CA. Running instances are not affected.
Degraded Slow console page loads Console & website · 44 min · Resolved
  1. 12:45Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 12:20Monitoring — A fix has been applied and we are monitoring the results.
  3. 11:51Identified — Root cause identified and a fix is being applied.
  4. 11:36Investigating — We are investigating slow console page loads. Running instances are not affected.
Degraded Delayed on-chain confirmation tracking Payments · 46 min · Resolved
  1. 05:51Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 05:26Monitoring — A fix has been applied and we are monitoring the results.
  3. 04:56Identified — Root cause identified: upstream network confirmation delays. Credits apply automatically once transactions confirm.
  4. 04:40Investigating — We are investigating delayed on-chain confirmation tracking. Running instances are not affected.
Degraded Slow instance deploys in Frankfurt Provisioning · 43 min · Resolved
  1. 21:03Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 20:38Monitoring — A fix has been applied and we are monitoring the results.
  3. 20:10Identified — Root cause identified: image-cache pressure on a subset of hosts. Deploys are being rebalanced.
  4. 19:55Investigating — We are investigating slow instance deploys in Frankfurt. Running instances are not affected.
Degraded Degraded volume throughput in Los Angeles, CA Storage fabric US Los Angeles, CA · 35 min · Resolved
  1. 15:34Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 15:09Monitoring — A fix has been applied and we are monitoring the results.
  3. 14:46Identified — Root cause identified and a fix is being applied.
  4. 14:34Investigating — We are investigating degraded volume throughput in Los Angeles, CA. Running instances are not affected.
Degraded Slow console page loads Console & website · 44 min · Resolved
  1. 12:45Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 12:20Monitoring — A fix has been applied and we are monitoring the results.
  3. 11:51Identified — Root cause identified and a fix is being applied.
  4. 11:36Investigating — We are investigating slow console page loads. Running instances are not affected.

September 2026 4

Outage Intermittent 5xx responses on the REST API REST API · 85 min · Resolved
  1. 18:09Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 17:44Monitoring — A fix has been applied and we are monitoring the results.
  3. 16:48Identified — Root cause identified and a fix is being applied.
  4. 16:19Investigating — We are investigating intermittent 5xx responses on the REST API. Running instances are not affected.
Degraded Degraded volume throughput in Chicago, IL Storage fabric US Chicago, IL · 40 min · Resolved
  1. 05:44Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 05:19Monitoring — A fix has been applied and we are monitoring the results.
  3. 04:53Identified — Root cause identified and a fix is being applied.
  4. 04:39Investigating — We are investigating degraded volume throughput in Chicago, IL. Running instances are not affected.
Outage Elevated NVMe latency in São Paulo Storage fabric · 84 min · Resolved
  1. 21:47Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 21:22Monitoring — A fix has been applied and we are monitoring the results.
  3. 20:27Identified — Root cause identified and a fix is being applied.
  4. 19:58Investigating — We are investigating elevated NVMe latency in São Paulo. Running instances are not affected.
Degraded Degraded volume throughput in Chicago, IL Storage fabric US Chicago, IL · 40 min · Resolved
  1. 05:44Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 05:19Monitoring — A fix has been applied and we are monitoring the results.
  3. 04:53Identified — Root cause identified and a fix is being applied.
  4. 04:39Investigating — We are investigating degraded volume throughput in Chicago, IL. Running instances are not affected.

August 2026 5

Degraded Packet loss on the Vancouver edge Network edge · 14 min · Resolved
  1. 04:32Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 04:07Monitoring — A fix has been applied and we are monitoring the results.
  3. 03:57Identified — Root cause identified and a fix is being applied.
  4. 03:53Investigating — We are investigating packet loss on the Vancouver edge. Running instances are not affected.
Degraded Slow instance deploys in Madrid Provisioning ES Madrid · 25 min · Resolved
  1. 04:48Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 04:23Monitoring — A fix has been applied and we are monitoring the results.
  3. 04:06Identified — Root cause identified: image-cache pressure on a subset of hosts. Deploys are being rebalanced.
  4. 03:58Investigating — We are investigating slow instance deploys in Madrid. Running instances are not affected.
Degraded Packet loss on the Tokyo edge Network edge JP Tokyo · 46 min · Resolved
  1. 21:06Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 20:41Monitoring — A fix has been applied and we are monitoring the results.
  3. 20:11Identified — Root cause identified and a fix is being applied.
  4. 19:55Investigating — We are investigating packet loss on the Tokyo edge. Running instances are not affected.
Degraded Slow console page loads Console & website · 45 min · Resolved
  1. 12:47Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 12:22Monitoring — A fix has been applied and we are monitoring the results.
  3. 11:52Identified — Root cause identified and a fix is being applied.
  4. 11:37Investigating — We are investigating slow console page loads. Running instances are not affected.
Degraded Packet loss on the Tokyo edge Network edge JP Tokyo · 46 min · Resolved
  1. 21:06Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 20:41Monitoring — A fix has been applied and we are monitoring the results.
  3. 20:11Identified — Root cause identified and a fix is being applied.
  4. 19:55Investigating — We are investigating packet loss on the Tokyo edge. Running instances are not affected.

Deploy your first GPU in under a minute

Top up in crypto, benchmark us against your current provider. Per-second billing, fixed prices ≥ 30% below market — cancel by just stopping the instance.

Create an account See all prices