Compare

AWS vs Google Cloud

Admitted uptime

Last 30 daysTime not covered by a Sev 1 the provider posted itself. A best case.
0.00%
100.00%
Last 90 days
0.00%
100.00%
Last 12 months
35.51%
93.99%

Grades (90 days)

OverallSeverity weight × minutes, summed over the window. Fewer points, better grade.
C · 2,148 pts
D · 3,151 pts
ProductionYour users are hit: apps, APIs, databases, inference
C
D
ShippingYou can't deploy, build or manage: CI, CLI, dashboard, auth, billing
A
B

Incidents (90 days)

Total incidentsEverything posted on the status page except scheduled maintenance.
9
4
Sev 1 · Lights outProd site, API or database down, or data loss
2
0
Sev 2 · BleedingProd degraded or partly down
5
4
Sev 3 · Can't shipCan't deploy, build or manage it
1
0
Sev 4 · PapercutDocs, status page, slow dashboard
1
0
Median fixMedian time to resolve. Half of incidents were fixed faster.
2h 18m
6h 10m
LongestLongest single incident, start to resolved.
235d 6h
29h 46m
Security incidentsIncidents the provider flagged as security. They count one tier higher.
0
0

Trend and communication

Last 6 months vs 6 beforeIncident count, last 6 months against the 6 before.
Worse (9 → 17)
Worse (1 → 7)
Sev 1–2 postmortemsSev 1–2 incidents with a published write-up.
0 of 5
4 of 4

Cost

Per month2 vCPU (burstable) and 4 GB Linux VM on all month, 30 GB SSD disk, a public IPv4, 100 GB out. On-demand, cheapest US region, no commitments.
$30.58
~$43.11
Plan or model
EC2 t4g.medium, us-east-1
Compute Engine e2-medium, us-central1
Best valueNobody else here costs the same or less with the same or better grade.
Yes
No
VerdictAWS has the best 90-day record; AWS resolves incidents fastest.Running app? Watch Production. Deploying all day? Watch Shipping.

Matchups

Uptime as admitted on each status page. How grades work