Skip to content
Updated 24h ago

AWS vs Google Cloud SLA

Promised uptime per service, credits, support and what the status pages showed, side by side.
Change vendors (up to four; 2 picked)

Promise vs reality

Promised in the SLAObserved on the vendor's status pagePartial historyShortfall

Best SLA by category

Support: fastest first response

  • AWS Business Support+30 minBusiness-critical system down: < 30 mins · Production system down: < 1 hour · Production system impaired: < 4 hours · System impaired: < 12 hours · General guidance: < 24 hours
  • AWS Enterprise Support15 minBusiness/mission-critical system down: < 15 mins · Production system down: < 1 hour · Production system impaired: < 4 hours · System impaired: < 12 hours · General guidance: < 24 hours
  • AWS Unified Operations5 minMission-critical system down: < 5 mins from Incident Management Engineer · Production system down: < 1 hour · Production system impaired: < 4 hours · System impaired: < 12 hours · General guidance: < 24 hours
  • AWS Developer (legacy, closed to new subscriptions)n/aNo published response targets.
  • AWS Business (legacy, closed to new subscriptions)1 hCritical issues: 1 hour
  • AWS Enterprise On-Ramp (legacy, being deprecated)30 minCritical issues: 30 minutes
  • Google Cloud Standard4 hP2: 4 hours · P3: 8 hours · P4: 8 hours
  • Google Cloud Enhanced1 hP1: 1 hour · P2: 4 hours · P3: 8 hours · P4: 8 hours
  • Google Cloud Premium15 minP1: 15 minutes · P2: 2 hours · P3: 4 hours · P4: 8 hours

Popular comparisons

Sources: each vendor's own SLA page (re-read monthly) and status page feed (read every Friday). A summary, not the contract: the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.

SLA changes by email

Fridays, only in weeks when a cloud, data or AI vendor changed an SLA.

Double opt-in. Unsubscribe any time.