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

See the proof
Launch a GPU

Service status · all times UTC

All systems operational

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

  • 99.97%90-day uptime, all components
  • 1,936GPUs 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.powergpu.io and powergpu.io
99.97% Operational
REST API/v1 — offers, instances, balance
100.00% Operational
Provisioningdeploys, start/stop, image cache
99.94% 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.98% Operational
Email deliveryresets, receipts, ticket answers
99.98% Operational

Live metrics — last 24 hours

Fleet-wide medians, one point every 15 minutes.

API latency p50, ms

47 ms now · avg 46

min 42 · max 50 ms

Deploy time p50, seconds to running

26.3 s now · avg 27.0

min 24.0 · max 29.7 s

GPUs online fleet-wide

1,936 now · avg 1,936

min 1,909 · max 1,965

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 116 43 ms 100.00%
US New York, NYus-east-2 Operational 62 39 ms 100.00%
US Chicago, ILus-central-1 Operational 97 36 ms 100.00%
US Dallas, TXus-central-2 Operational 79 34 ms 100.00%
US Los Angeles, CAus-west-1 Operational 72 37 ms 100.00%
US Seattle, WAus-west-2 Operational 64 33 ms 100.00%
US Miami, FLus-south-1 Operational 40 42 ms 100.00%
CA Montréalca-east-1 Operational 92 36 ms 100.00%
CA Vancouverca-west-1 Operational 22 41 ms 100.00%
MX Querétaromx-central-1 Operational 57 43 ms 100.00%

Europe 10 regions

RegionStatusGPUsLatency30 days
NL Amsterdameu-west-1 Operational 52 46 ms 100.00%
GB Londoneu-west-2 Operational 82 42 ms 100.00%
FR Pariseu-west-3 Operational 38 44 ms 100.00%
DE Frankfurteu-central-1 Operational 85 43 ms 100.00%
PL Warsaweu-central-2 Operational 72 45 ms 100.00%
SE Stockholmeu-north-1 Operational 99 38 ms 100.00%
FI Helsinkieu-north-2 Operational 24 37 ms 100.00%
IT Milaneu-south-1 Operational 36 45 ms 100.00%
ES Madrideu-south-2 Operational 57 44 ms 99.95%
RO Bucharesteu-east-1 Operational 32 40 ms 100.00%

Asia-Pacific 7 regions

RegionStatusGPUsLatency30 days
JP Tokyoap-northeast-1 Operational 76 68 ms 99.95%
KR Seoulap-northeast-2 Operational 55 67 ms 100.00%
JP Osakaap-northeast-3 Operational 45 65 ms 100.00%
SG Singaporeap-southeast-1 Operational 87 69 ms 100.00%
AU Sydneyap-southeast-2 Operational 46 67 ms 100.00%
ID Jakartaap-southeast-3 Operational 39 65 ms 100.00%
IN Mumbaiap-south-1 Operational 102 57 ms 100.00%

South America 2 regions

RegionStatusGPUsLatency30 days
BR São Paulosa-east-1 Operational 48 76 ms 100.00%
CL Santiagosa-west-1 Operational 26 89 ms 100.00%

Middle East & Africa 3 regions

RegionStatusGPUsLatency30 days
AE Dubaime-central-1 Operational 49 77 ms 100.00%
ZA Johannesburgaf-south-1 Operational 51 68 ms 100.00%
IL Tel Avivil-central-1 Operational 34 74 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 Power maintenance at the facility US Seattle, WA

2026-09-14 02:00 UTC → 04:00 UTC (2 h window)

Scheduled UPS testing by the datacenter operator. Fully redundant path; no customer impact expected.

Under maintenance Power maintenance at the facility US Dallas, TX

2026-09-16 02:00 UTC → 04:00 UTC (2 h window)

Scheduled UPS testing by the datacenter operator. Fully redundant path; no customer impact expected.

Incident history — last 90 days

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

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.

July 2026 2

Degraded Delayed transactional email delivery Email delivery · 46 min · Resolved
  1. 05:28Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 05:03Monitoring — A fix has been applied and we are monitoring the results.
  3. 04:33Identified — Root cause identified and a fix is being applied.
  4. 04:17Investigating — We are investigating delayed transactional email delivery. 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.

June 2026 4

Degraded Slow instance deploys in Warsaw Provisioning PL Warsaw · 22 min · Resolved
  1. 15:57Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 15:32Monitoring — A fix has been applied and we are monitoring the results.
  3. 15:17Identified — Root cause identified: image-cache pressure on a subset of hosts. Deploys are being rebalanced.
  4. 15:10Investigating — We are investigating slow instance deploys in Warsaw. Running instances are not affected.
Degraded Delayed on-chain confirmation tracking Payments · 45 min · Resolved
  1. 06:50Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 06:25Monitoring — A fix has been applied and we are monitoring the results.
  3. 05:55Identified — Root cause identified: upstream network confirmation delays. Credits apply automatically once transactions confirm.
  4. 05:40Investigating — We are investigating delayed on-chain confirmation tracking. Running instances are not affected.
Outage Deploy queue backlog in Frankfurt Provisioning · 109 min · Resolved
  1. 22:08Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
  2. 21:43Monitoring — A fix has been applied and we are monitoring the results.
  3. 20:32Identified — Root cause identified: image-cache pressure on a subset of hosts. Deploys are being rebalanced.
  4. 19:54Investigating — We are investigating deploy queue backlog in Frankfurt. 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.

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