Under maintenance Provisioning host patching
Frankfurt
2026-09-22 02:00 UTC → 04:00 UTC (2 h window)
Rolling host kernel/driver updates. New deploys in the region may queue for a few minutes; running instances are unaffected.
Service status · all times UTC
All systems operational
Updated 12:10:27 · 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,937GPUs 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.ai and powergpu.ai
99.98%
Operational REST API/v1 — offers, instances, balance
100.00%
Operational Provisioningdeploys, start/stop, image cache
100.00%
Operational Network edgeinstance hostnames, TLS, port maps
99.98%
Operational Storage fabricinstance NVMe and network volumes
99.88%
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.4 s now · avg 26.9
min 24.0 · max 29.9 s
GPUs online fleet-wide
1,937 now · avg 1,936
min 1,907 · max 1,964
Regions
Per-region state, GPUs accepting deploys, API latency from the region's edge, and the last 30 days.
North America 10 regions
| Region | Status | GPUs | Latency | 30 days |
|---|---|---|---|---|
 Ashburn, VAus-east-1 |
Operational | 116 | 43 ms | 100.00% |
| New York, NYus-east-2 |
Operational | 62 | 39 ms | 100.00% |
| Chicago, ILus-central-1 |
Operational | 97 | 36 ms | 99.91% |
| Dallas, TXus-central-2 |
Operational | 79 | 34 ms | 100.00% |
| Los Angeles, CAus-west-1 |
Operational | 72 | 37 ms | 100.00% |
| Seattle, WAus-west-2 |
Operational | 64 | 34 ms | 100.00% |
| Miami, FLus-south-1 |
Operational | 40 | 42 ms | 100.00% |
 Montréalca-east-1 |
Operational | 93 | 35 ms | 100.00% |
| Vancouverca-west-1 |
Operational | 22 | 41 ms | 100.00% |
 Querétaromx-central-1 |
Operational | 57 | 44 ms | 100.00% |
Europe 10 regions
| Region | Status | GPUs | Latency | 30 days |
|---|---|---|---|---|
 Amsterdameu-west-1 |
Operational | 52 | 46 ms | 100.00% |
 Londoneu-west-2 |
Operational | 82 | 42 ms | 100.00% |
 Pariseu-west-3 |
Operational | 38 | 44 ms | 100.00% |
| Frankfurteu-central-1 |
Operational | 85 | 43 ms | 100.00% |
 Warsaweu-central-2 |
Operational | 72 | 45 ms | 100.00% |
 Stockholmeu-north-1 |
Operational | 99 | 39 ms | 100.00% |
 Helsinkieu-north-2 |
Operational | 24 | 38 ms | 100.00% |
 Milaneu-south-1 |
Operational | 36 | 44 ms | 100.00% |
 Madrideu-south-2 |
Operational | 57 | 44 ms | 99.95% |
 Bucharesteu-east-1 |
Operational | 32 | 40 ms | 100.00% |
Asia-Pacific 7 regions
| Region | Status | GPUs | Latency | 30 days |
|---|---|---|---|---|
 Tokyoap-northeast-1 |
Operational | 76 | 68 ms | 99.95% |
 Seoulap-northeast-2 |
Operational | 55 | 67 ms | 100.00% |
| Osakaap-northeast-3 |
Operational | 45 | 65 ms | 100.00% |
 Singaporeap-southeast-1 |
Operational | 87 | 68 ms | 100.00% |
 Sydneyap-southeast-2 |
Operational | 46 | 67 ms | 100.00% |
 Jakartaap-southeast-3 |
Operational | 39 | 65 ms | 100.00% |
 Mumbaiap-south-1 |
Operational | 102 | 58 ms | 100.00% |
South America 2 regions
| Region | Status | GPUs | Latency | 30 days |
|---|---|---|---|---|
 São Paulosa-east-1 |
Operational | 48 | 77 ms | 100.00% |
 Santiagosa-west-1 |
Operational | 26 | 88 ms | 100.00% |
Middle East & Africa 3 regions
| Region | Status | GPUs | Latency | 30 days |
|---|---|---|---|---|
 Dubaime-central-1 |
Operational | 49 | 77 ms | 100.00% |
 Johannesburgaf-south-1 |
Operational | 51 | 69 ms | 100.00% |
 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 Provisioning host patching
London
2026-09-24 02:00 UTC → 04:00 UTC (2 h window)
Rolling host kernel/driver updates. New deploys in the region may queue for a few minutes; running instances are unaffected.
Incident history — last 90 days
Every incident with customer impact, newest first, with its full timeline. Transparency beats a wall of green.
September 2026 3
Degraded
Degraded volume throughput in Chicago, IL
Storage fabric
Chicago, IL
- 05:44Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 05:19Monitoring — A fix has been applied and we are monitoring the results.
- 04:53Identified — Root cause identified and a fix is being applied.
- 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
- 21:47Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 21:22Monitoring — A fix has been applied and we are monitoring the results.
- 20:27Identified — Root cause identified and a fix is being applied.
- 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
Chicago, IL
- 05:44Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 05:19Monitoring — A fix has been applied and we are monitoring the results.
- 04:53Identified — Root cause identified and a fix is being applied.
- 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
- 04:32Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 04:07Monitoring — A fix has been applied and we are monitoring the results.
- 03:57Identified — Root cause identified and a fix is being applied.
- 03:53Investigating — We are investigating packet loss on the Vancouver edge. Running instances are not affected.
Degraded
Slow instance deploys in Madrid
Provisioning
Madrid
- 04:48Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 04:23Monitoring — A fix has been applied and we are monitoring the results.
- 04:06Identified — Root cause identified: image-cache pressure on a subset of hosts. Deploys are being rebalanced.
- 03:58Investigating — We are investigating slow instance deploys in Madrid. Running instances are not affected.
Degraded
Packet loss on the Tokyo edge
Network edge
Tokyo
- 21:06Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 20:41Monitoring — A fix has been applied and we are monitoring the results.
- 20:11Identified — Root cause identified and a fix is being applied.
- 19:55Investigating — We are investigating packet loss on the Tokyo edge. Running instances are not affected.
Degraded Slow console page loads Console & website
- 12:47Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 12:22Monitoring — A fix has been applied and we are monitoring the results.
- 11:52Identified — Root cause identified and a fix is being applied.
- 11:37Investigating — We are investigating slow console page loads. Running instances are not affected.
Degraded
Packet loss on the Tokyo edge
Network edge
Tokyo
- 21:06Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 20:41Monitoring — A fix has been applied and we are monitoring the results.
- 20:11Identified — Root cause identified and a fix is being applied.
- 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
- 05:28Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 05:03Monitoring — A fix has been applied and we are monitoring the results.
- 04:33Identified — Root cause identified and a fix is being applied.
- 04:17Investigating — We are investigating delayed transactional email delivery. Running instances are not affected.
Outage Elevated NVMe latency in São Paulo Storage fabric
- 21:47Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 21:22Monitoring — A fix has been applied and we are monitoring the results.
- 20:27Identified — Root cause identified and a fix is being applied.
- 19:58Investigating — We are investigating elevated NVMe latency in São Paulo. Running instances are not affected.
June 2026 2
Degraded
Slow instance deploys in Warsaw
Provisioning
Warsaw
- 15:57Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 15:32Monitoring — A fix has been applied and we are monitoring the results.
- 15:17Identified — Root cause identified: image-cache pressure on a subset of hosts. Deploys are being rebalanced.
- 15:10Investigating — We are investigating slow instance deploys in Warsaw. Running instances are not affected.
Degraded Delayed on-chain confirmation tracking Payments
- 06:50Resolved — This incident has been resolved. Affected on-demand instances are covered by the SLA credit policy.
- 06:25Monitoring — A fix has been applied and we are monitoring the results.
- 05:55Identified — Root cause identified: upstream network confirmation delays. Credits apply automatically once transactions confirm.
- 05:40Investigating — We are investigating delayed on-chain confirmation tracking. Running instances are not affected.